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

Backport XML passing to LTS as jump version for airgapped environments #1600

Merged
merged 1 commit into from
Jan 31, 2024

Conversation

pothos
Copy link
Member

@pothos pothos commented Jan 25, 2024

Old versions didn't pass the Omaha XML response to the update-engine postinst action, thus triggering the fallback download which doesn't work for clients on a restricted network.
Backport the XML passing to make it possible to use this LTS version as jump version because it doesn't require OEM payloads.

How to use

Test on Jenkins, and call out in the Stable release notes that this jump version is required to be used for clients on a restricted network - unless we add workarounds to the postinst action to find the xml from the service logs.

Testing done

Update from built image to current Stable with sudo -A ./flatcar-update -V 3760.2.0 -P ./flatcar_production_update.gz -E ./oem-qemu.gz -F worked without Internet access because it didn't run into the fallback download case.

  • Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)
  • Inspected CI output for image differences: /boot and /usr size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.

Old versions didn't pass the Omaha XML response to the update-engine
postinst action, thus triggering the fallback download which doesn't
work for clients on a restricted network.
Backport the XML passing to make it possible to use this LTS version as
jump version because it doesn't require OEM payloads.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants