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

[rhcos-4.12] backports for 9p issue and concurrency for extensions container #3187

Merged
merged 4 commits into from
Nov 11, 2022

Conversation

dustymabe
Copy link
Member

No description provided.

We're investigating an error in this command and we need more context.

(cherry picked from commit ee0ac59)
This is necessary so that the `tmp_builddir`s allocated are distinct per
artifact run. Otherwise, running the two commands in parallel will stomp
on each other as they try to use the same dir.

`buildextend-metal` already does this, so we're missing
`buildextend-extensions-container` and `buildextend-legacy-oscontainer`.

I believe this is the reason why `buildextend-extensions-container` has
been failing in the RHCOS pipeline.

I avoided a larger cleanup here around enforcing `IMAGE_TYPE` (probably
should be renamed to e.g. `ARTIFACT`) getting set in `prepare_build`.
That requires more work because we should also make sure to consistently
clean up the dir at the end. Right now, we're relying on the fact that
the same dir gets cleaned and reused each time. We'll also need to
backport this so I wanted to keep the changes minimal.

(cherry picked from commit db1c001)
We should be able to get rid of the two codes `disable=` bits there if
we just tell ShellCheck where to find `cmdlib.sh` as we do elsewhere.

(cherry picked from commit f2cfb18)
9p being 9p, we're hitting ENOMEM when trying to read `platforms.json`
in `install_grub_cfg()`. Yet, it works fine at the top of the file when
we initially parse the kargs and GRUB cmds. So somehow initial reads do
go through. Let's try to leverage this by doing an early copy of the
file into the supermin filesystem and then do any further introspections
from there. That way, we only access it over 9p once.

Maybe fixes coreos#3180.

(cherry picked from commit e867666)
@dustymabe dustymabe enabled auto-merge (rebase) November 10, 2022 22:03
Copy link
Member

@jmarrero jmarrero left a comment

Choose a reason for hiding this comment

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

lgtm

auto-merge was automatically disabled November 10, 2022 22:35

Rebase failed

@mike-nguyen
Copy link
Member

@dustymabe This looks like it is targeting main but is titled rhcos-4.12. Is this what you intended?

@dustymabe dustymabe changed the base branch from main to rhcos-4.12 November 10, 2022 23:46
@dustymabe
Copy link
Member Author

@dustymabe This looks like it is targeting main but is titled rhcos-4.12. Is this what you intended?

good catch. Fixed!

Copy link
Member

@mike-nguyen mike-nguyen left a comment

Choose a reason for hiding this comment

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

lgtm

@dustymabe dustymabe merged commit 09cc641 into coreos:rhcos-4.12 Nov 11, 2022
@dustymabe dustymabe deleted the dusty-4.12-backports branch November 11, 2022 15:40
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.

None yet

4 participants