Couple of hosts been able to upgrade to v0.4.3 successfully.
But have a couple of cases, where OS says its upgrade to latest , but after reboot, still remained on old version.
What would prevent the new OS from installing?
anything to do with /mnt folder?
I’m having the same issue with upgrading from v0.4.2 to v0.4.3 . My initial install was from a rancheros.iso
How about you ? Was your initial install from an ISO ?
Indeed it is, Initial install is from a v0.4.1 iso, same iso for all hosts.
some hosts upgraded fine, but now nothing will upgrade.
I’m not sure what happening, I have the output from ros os version and ros os list after a reboot below. Are yours the same?
[rancher@rancher-002 ~]$ sudo ros os version
v0.4.2
[rancher@rancher-002 ~]$ sudo ros os list
rancher/os:v0.4.0 remote
rancher/os:v0.4.1 remote
rancher/os:v0.4.2 remote
rancher/os:v0.4.3 local
rancher@Daakman-Barrek:~$ sudo ros os version
v0.4.1
rancher@Daakman-Barrek:~$ sudo ros os list
rancher/os:v0.4.0 remote
rancher/os:v0.4.1 remote
rancher/os:v0.4.2 remote
rancher/os:v0.4.3 local
rancher@Daakman-Barrek:~$
Strangest part of all two different host, same subset, almost exact same config, apart from hostname and IP.
One upgrades to 43, the other wont, both from clean installs.
How/where have you guys installed RancherOS?
Mine is on VMWare ESX 5.5
All from same source media etc.
Some will update with no issues, others simply wont.
I have since started using the 4.2 image as primary source, so need to go through a process of redoing all current installations with the new source. Best case would be if could find what is preventing the upgrade.
We haven’t been able to reproduce, but we made some changes for upgrade/rollback for the next release that should hopefully resolve issues. Please note it would only be for upgrading to release after the next release, so upgrading to the next release (v0.4.4) might still have issues.