unable to update flatcar #1424
Comments
|
Moarrr logs: Can't make sense of the error though. |
|
Tried an airgabbed update to work around the weird nebraska issue, so I downloaded node-006 core # wget "https://update.release.flatcar-linux.net/${ARCH}-usr/${VER}/flatcar_production_update.gz"
--2024-04-11 17:59:31-- https://update.release.flatcar-linux.net/amd64-usr/3815.2.1/flatcar_production_update.gz
Resolving update.release.flatcar-linux.net... 147.75.87.17
Connecting to update.release.flatcar-linux.net|147.75.87.17|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 458234665 (437M) [application/gzip]
Saving to: 'flatcar_production_update.gz'
flatcar_production_update.gz 100%[========================================================================================================>] 437.01M 137MB/s in 3.3s
2024-04-11 17:59:34 (132 MB/s) - 'flatcar_production_update.gz' saved [458234665/458234665]
node-006 core # ./flatcar-update --to-version "$VER" --to-payload flatcar_production_update.gz
./flatcar-update: line 209: EXTENSIONS[@]: unbound variable |
|
The problem is that the update-engine client can't mount the btrfs partition. You can first update to LTS ( The bash error is a bug in bash 4.3, I prepared a workaround in flatcar/init#119 which you can use to update to LTS explicitly instead of setting |
|
Worked! :) |
|
@pothos I am trying this on another machine that's stuck on an older release and I am hitting the bash error again: |
|
When I comment out this line, it's progressing but dies at: Script is full of these problems. |
|
Update still worked, though had to remove a line from |
Worked for me too, updating from an older version of flatcar (changed GROUP=stable to GROUP=lts, updated and rebooted, and then switched back to stable channel and updated again). |
|
@whysi what did you run? |
|
@till exactly, I ran Also I wanted to mention that running the "air-gapped" mode of the script tries to download the get the update-payload-key from the web...a bit of a nonsense. Anyway even copying the key manually from a non-air-gapped machine didn't solve my errors with the script that I tried before finding this issue and the resolution suggested by @pothos |
|
@dongsupark can you re-schedule this? The script still contains more of these bash errors. |
Description
Trying to update to the latest release fails.
Impact
Cannot update to the latest stable.
Environment and steps to reproduce
Current version:
Ran
update_engine_client -update(after-check_for_updatefailed):Journal:
Update engine log:
Expected behavior
I can reboot into the new version.
Additional information
Please add any information here that does not fit the above format.
The text was updated successfully, but these errors were encountered: