-
Notifications
You must be signed in to change notification settings - Fork 305
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
bootloader/zipl: Run in target deployment as container if needed #3104
Conversation
Prep for using this for zipl.
Skipping CI for Draft Pull Request. |
a652bf7
to
7f01c54
Compare
OK with this I get:
Which...hmm, looks like it's saying no BLS entries were found? |
Prep for use with zipl.
7f01c54
to
3b6d9c0
Compare
OK, we now correctly bind |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thx for this!
{ | ||
g_debug ("executing zipl in deployment root"); | ||
g_autofree char *deployment_path | ||
= ostree_sysroot_get_deployment_dirpath (self->sysroot, target_deployment); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As i see, this function uses bwrap
but doesn't map/bind /boot
, so zipl
uses its default zipl.conf
. This could be also avoided by using --blsdir
option.
I've invited @nikita-dubrovskii to be a collaborator, but someone else with commit rights needs to approve... @jmarrero ? |
failure seems legit re-running just in case. |
We will use it in e.g. s390x zipl backend.
xref https://issues.redhat.com/browse/MGMT-16303 Basically the OCP Assisted installer has now grown code to try to do OS updates offline post-install, and this means we need to handle the case of running zipl from the target root.
3b6d9c0
to
c3aa295
Compare
Should be fixed, let's see |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
sysroot: Expose deployment container executor internally
Prep for using this for zipl.
bootloader/zipl: Run in target deployment as container if needed
xref https://issues.redhat.com/browse/MGMT-16303
Basically the OCP Assisted installer has now grown code
to try to do OS updates offline post-install, and this means
we need to handle the case of running zipl from the target
root.