Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

{kola,kolaTestIso}: workaround issue with accessDenied from dir() #124

Merged
merged 1 commit into from
Oct 17, 2022

Conversation

dustymabe
Copy link
Member

@dustymabe dustymabe commented Oct 17, 2022

When using dir() in the kola and kolaTestIso jobs the cd is happening on the controller (not in the COSA pod) so if the directory isn't under the env.WORKSPACE directory then we get a permission denied error.

Let's go back to using a cd ${cosaDir} for now to workaround this while we find better solutions. This cd ${cosaDir} will have no effect on multi-arch where we'll be operating in a remote session anyway.

Copy link
Member

@jlebon jlebon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! As discussed OOB, we will circle back on this and rework things to make it cleaner.

When using dir() in the kola and kolaTestIso jobs the cd is happening on the controller (not in the COSA pod).

To clarify, that was my first theory but in testing, the fact that it does work if it's a subdir of the workspace seems to indicate it's more subtle than that.

When using `dir()` in the kola and kolaTestIso jobs we are getting a
permission denied error if the directory is isn't under the env.WORKSPACE
directory.

Let's go back to using a `cd ${cosaDir}` for now to workaround this while
we find better solutions. This `cd ${cosaDir}` will have no effect on
multi-arch where we'll be operating in a remote session anyway.
@dustymabe
Copy link
Member Author

To clarify, that was my first theory but in testing, the fact that it does work if it's a subdir of the workspace seems to indicate it's more subtle than that.

updated the commit message to drop that possibly inaccurate detail.

@dustymabe dustymabe merged commit b2bbc1b into coreos:main Oct 17, 2022
jlebon added a commit to jlebon/coreos-ci-lib that referenced this pull request Oct 17, 2022
Support for the cosa directory being different from the working
directory makes implementation details messier.

Drop support for it.

Callers can still have their cosa directories be different from the
Jenkins workspace by first wrapping calls to the cosa APIs here in a
call to `dir(cosaDir)`:

```
dir(cosaDir) {
        cosaBuild(skipKola: true)
        kola()
        kolaTestIso(skipMetal4k: true)
}
```

The cosa directory currently needs to be a subdirectory of the workspace
(see coreos#124).
@jlebon
Copy link
Member

jlebon commented Oct 17, 2022

LGTM! As discussed OOB, we will circle back on this and rework things to make it cleaner.

Draft in #125.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants