Closed HarithaRamesh closed 2 months ago
Hello @HarithaRamesh,
Before going further can you try again with the new release 3815.2.4 to see if you still have this behavior?
Looks like there is some timeout issue between socat and the update-engine.
Ah, yes I tried again with the 3815.2.4 patch and that worked. Thank you!
For what is worth, I tried to repro yesterday with /usr/bin/flatcar-update -P flatcar/flatcar_production_update.gz -V 3815.2.3 -E flatcar/oem-vmware.gz
and it worked fine.
It might be a transient issue. If it's ok with you, can you close this? Feel free to re-open if you are facing again this issue.
Yes it was the GCE that was problematic, but the new patch works on all gce, vmware and azure, so I'm happy.
Description
I use flatcar in an airgapped system, so my mode of upgrade from 3760.2.0 was to run
Having downloaded the artifacts from https://update.release.flatcar-linux.net/amd64-usr. This works fine going from 3760.2.0 --> 3815.2.0 or 3760.2.0 --> 3815.2.3. However, I'm seeing errors when going from 3815.2.0 --> 3815.2.3 on GCE specifically
Impact
I am not able to upgrade from 3815.2.0 in my airgapped environment on GCE VM. I have tested the 3815.2.0 --> 3815.2.3 path on vmware and azure, those seem to work with the respective oem-vmware.gz and oem-azure.gz files
Environment and steps to reproduce
I've also attached logs from the update-engine
Expected behavior
I expect it to run the update successfully like it does for VMware and Azure.
Successful run:
Is this an issue with oem-gce.gz in later flatcars?