Closed nikita-dubrovskii closed 2 weeks ago
hey @nikita-dubrovskii - if possible can we hold this until https://github.com/coreos/coreos-assembler/pull/3930 merges?
There are a bunch of changes in there, including moving code in buildextend-metal around quite a bit and I'd prefer not to have to do merges conflict resolution for all of those commits.
hey @nikita-dubrovskii - if possible can we hold this until #3930 merges?
There are a bunch of changes in there, including moving code in buildextend-metal around quite a bit and I'd prefer not to have to do merges conflict resolution for all of those commits.
No worries, this can wait. Mind a review?
No worries, this can wait. Mind a review?
The other PR merged now. You'll need to put this logic inside cmd-osbuild
now.
genprotimg.bu: add coreos-genprotimg-generator
This fixes an issue when during firstboot system tried to mount genprotimg partition.
I'm trying to figure out why it was trying to mount on first boot with the units that existed before this change.. Does ConditionKernelCommandLine=!ignition.firstboot
not work on a .mount
unit?
genprotimg.bu: add coreos-genprotimg-generator This fixes an issue when during firstboot system tried to mount genprotimg partition.
I'm trying to figure out why it was trying to mount on first boot with the units that existed before this change.. Does
ConditionKernelCommandLine=!ignition.firstboot
not work on a.mount
unit?
It doesn't. As i got from docs - generator with condition(s) should be used.
Automatically generates
genprotimgvm
during build, when official one is not available and/or there is no so-called "IBM Universal Hostkey". Main goal is to support local/custom build ofqemu-secex
target. Assuming there is a valid hostkey, now it's possible to generatecoreos.qemu-secex.qcow2
just by running:If later there is a need to build some other variant, user can use previously generated
genprotimgvm
: