-
Notifications
You must be signed in to change notification settings - Fork 53
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
oem: port digitalocean, equinix metal (packet) and openstack #1197
Conversation
I think it's a good idea to clean up unused/untested OEM setups, best would be in a follow-up and not linked to this PR, or? |
Build action triggered: https://github.com/flatcar/scripts/actions/runs/6337223529 |
KEYWORDS="amd64 arm64" | ||
IUSE="" | ||
|
||
OEM_NAME="Packet" |
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.
We can rename this variable, it's used in the shell prompt message but otherwise I think it's not relevant
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.
The grub cfg is gone but it has to be moved to the new place
c52bd33
to
831375f
Compare
831375f
to
55821de
Compare
Ok, anyway it was making the CI failing because it was trying to build the image for this vendor too. I cherry-picked the commit and pushed to another branch to do the removal in a follow-up PR. |
55821de
to
88f915d
Compare
8754e43
to
e72942e
Compare
e72942e
to
149b0a8
Compare
ConditionKernelCommandLine=|flatcar.oem.id=ec2 | ||
ConditionKernelCommandLine=|flatcar.coreos.id=ec2 | ||
|
||
ConditionKernelCommandLine=|flatcar.oem.id=azure | ||
ConditionKernelCommandLine=|flatcar.coreos.id=azure | ||
|
||
ConditionKernelCommandLine=|flatcar.oem.id=digitalocean | ||
ConditionKernelCommandLine=|flatcar.coreos.id=digitalocean | ||
|
||
ConditionKernelCommandLine=|flatcar.oem.id=gce | ||
ConditionKernelCommandLine=|flatcar.coreos.id=gce | ||
|
||
ConditionKernelCommandLine=|flatcar.oem.id=openstack | ||
ConditionKernelCommandLine=|flatcar.coreos.id=openstack | ||
|
||
ConditionKernelCommandLine=|flatcar.oem.id=packet | ||
ConditionKernelCommandLine=|flatcar.coreos.id=packet |
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.
This should be coreos.oem.id
149b0a8
to
cb25663
Compare
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.
With OEM sysext images we can also use the migration mechanism to clean up the old OEM contents. (This will also make the sysext images required on update.)
sdk_container/src/third_party/coreos-overlay/coreos-base/misc-files/files/oems/packet
Show resolved
Hide resolved
Signed-off-by: Mathieu Tortuyaux <[email protected]>
Signed-off-by: Mathieu Tortuyaux <[email protected]>
Signed-off-by: Mathieu Tortuyaux <[email protected]>
Signed-off-by: Mathieu Tortuyaux <[email protected]>
QEMU is not supported by Afterburn, let's add an extra-check to be sure that the service will not run on this platform. On cloud-init provisioned system, units are wrote in '/etc' after a certain moment, if a unit takes precedence on one in '/usr' the one in '/usr' would have certainly already started. That's the case for 'coreos-metadata.service' (wrote in '/etc' by cloud-init but already available in '/usr'). ``` $ journalctl -u coreos-metadata.service Sep 29 07:37:57 localhost systemd[1]: Starting coreos-metadata.service - Flatcar Metadata Agent... Sep 29 07:37:57 localhost coreos-metadata[1266]: Error: failed to run Sep 29 07:37:57 localhost coreos-metadata[1266]: Caused by: Sep 29 07:37:57 localhost coreos-metadata[1266]: 0: fetching metadata from provider Sep 29 07:37:57 localhost coreos-metadata[1266]: 1: unknown provider 'qemu' Sep 29 07:37:57 localhost systemd[1]: coreos-metadata.service: Main process exited, code=exited, status=1/FAILURE Sep 29 07:37:57 localhost systemd[1]: coreos-metadata.service: Failed with result 'exit-code'. Sep 29 07:37:57 localhost systemd[1]: Failed to start coreos-metadata.service - Flatcar Metadata Agent. Sep 29 07:37:58 core1 systemd[1]: coreos-metadata.service: Scheduled restart job, restart counter is at 1. Sep 29 07:37:58 core1 systemd[1]: Stopped coreos-metadata.service - QEMU metadata agent. Sep 29 07:37:58 core1 systemd[1]: Starting coreos-metadata.service - QEMU metadata agent... Sep 29 07:37:58 core1 systemd[1]: coreos-metadata.service: Deactivated successfully. Sep 29 07:37:58 core1 systemd[1]: Finished coreos-metadata.service - QEMU metadata agent. ``` Signed-off-by: Mathieu Tortuyaux <[email protected]>
133a855
to
bafe49f
Compare
These OEM do not ship any software, they only use systemd services (
[email protected]
andpacket-phone-home.service
).Need:
Closes:
I don't think a changelog entry is required as the sysext images are "empty".