Upgrade of flatcar to 3760.2.0 with update-engine fails when behind a proxy #1332
Comments
github-project-automation
bot
moved this to 📝 Needs Triage
in Flatcar tactical, release planning, and roadmap
|
Hello, this was reported in #1326 and a fix got merged today and will be part of the next releases - however, the fix is required in the OS that does the update. If you don't have connectivity without the proxy, you can do an airgapped update with |
github-project-automation
bot
moved this from 📝 Needs Triage
to Implemented
in Flatcar tactical, release planning, and roadmap
|
@pothos The flatcar-update does not have a -E option. I presume this option is for extensions. I have tried updating with flatcar-update now, using -P for both update file and extension file, but the update still fails as it still tries to connect to update.release.flatcar-linux.net according to the update-engine logs. Do I need a newer flatcar-update for this to work? |
|
I found one more problem on the way: Even with a newer flatcar-update ( |
|
We are thinking about adding workaround for the two issues of proxy settings and custom payload URLs to make it work with any old client. Will post when done. |
|
Same problem here, we are stuck at 3602.2.3 and we are behind a corporate web proxy, same error when downloading the OEM update payload. @pothos can you please let us know if/when there will be a way to bypass this problem with an airgapped update or something along those lines? Not exactly related but I wal also curious if using Nebraska to distribute the updates will work as an "not-so-quick workaround", what do you think? Thanks in advance for the help. |
|
Hi, hadn't time to prepare the planned workaround for this week's releases but what you'll be able to do next week is to jump through the to-be-released LTS and from then on the proxy env vars will be honored. A Nebraska with self-hosted packages won't work because of the other issue where a fix wasn't backported. Here again, we jump through the to-be-released LTS would be needed for now. |
|
A PR is up flatcar/update_engine#38 and I'll test it soon |
|
Workaround is rolling out for Stable, Beta, Alpha - hope all is good now. |
|
Yup, last update works as expected. Thank you for the fix and the updates a long the way! |
|
Great to hear that. If you run some nodes on Beta or Alpha, you can spot problems early and tell us ;) |
|
Can confirm that works for us too, thanks for your help. We have some machines on Beta, I'll keep an eye on them in the next releases. |
We have a number of flatcar nodes using a proxy to download images. When update-engine tries to upgrade to the latest release the download seems to work fine, but when the PostInstallRunnerAction starts it fails to connect to update.release.flatcar-linux.net.
We have set the dropin config for update-engine:
We have also tried to set the proxy settings system-wide as described here: https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/#system-wide-environment-variables
The error is still present and we are unable to upgrade any further. Do you have a workaround for this or are we missing some configuration? There have been no notable changes to our setup for quite some time, the issue was probably introduced with 3602.2.3.
/etc/flatcar/update.conf:
The text was updated successfully, but these errors were encountered: