maik
January 25, 2017, 9:51pm
1
hi there,
i just wanted to upgrade from a running server with rancher/os:v0.8.0-rc5 to rancher/os:v0.8.0-rc6 but it always starts again with rc5. any clue what i do wrong?
ros os upgrade -f -i rancher/os:v0.8.0-rc6
Upgrading to rancher/os:v0.8.0-rc6
os-upgrade_1 | > time="2017-01-25T21:45:32Z" level=warning msg="Cloud-config not provided: you might need to provide cloud-config on bootDir with ssh_authorized_keys"
os-upgrade_1 | Installing from :v0.8.0-rc6
> INFO[0000] Rebooting
thanks for help
looks an awful lot like upgrade is broken.
[root@test docker]# ros os upgrade -f -i rancher/os:v0.8.0-rc6
Upgrading to rancher/os:v0.8.0-rc6
Pulling os-upgrade (rancher/os:v0.8.0-rc6)...
v0.8.0-rc6: Pulling from rancher/os
0a8490d0dfd3: Pull complete
0690e52389de: Pull complete
9d941214f486: Pull complete
2643593d92dc: Pull complete
5ebef577beda: Pull complete
39e6e88df41d: Pull complete
79902cb25aea: Pull complete
a38f53a2be24: Pull complete
0061afe50916: Pull complete
Digest: sha256:70ad3b9cec1594691118364f8896a8ab53fb311b58d06bcb6b39e05ee15751b2
Status: Downloaded newer image for rancher/os:v0.8.0-rc6
os-upgrade_1 | > time="2017-01-26T10:48:31Z" level=warning msg="Cloud-config not provided: you might need to provide cloud-config on bootDir with ssh_authorized_keys"
os-upgrade_1 | Installing from :v0.8.0-rc6
os-upgrade_1 | lsblk: 1: not a block device
os-upgrade_1 | > time="2017-01-26T10:48:31Z" level=error msg="error layDownOS exit status 32"
os-upgrade_1 | > time="2017-01-26T10:48:31Z" level=fatal msg="Failed to run install" err="exit status 32"
> INFO[0086] Rebooting
Connection to 127.0.0.1 closed by remote host.
exit status 255
sven@i7:~/src/rancher$ docker-machine ssh test
[docker@test ~]$ uname -a
Linux test 4.9.5-rancher #1 SMP Sat Jan 21 13:35:55 UTC 2017 x86_64 GNU/Linux
[docker@test ~]$ ros -v
ros version v0.8.0-rc5
[docker@test ~]$ ls -la /bin/ros
-rwxr-xr-x 1 root root 17678832 Jan 22 12:55 /bin/ros
I’ll look into it tomorrow and make an rc7.
sorry, ignore that example - that was using docker-machine, which doesn’t install - it only uses the disk for state (and reboots to use the ISO)
but it is something where i need to improve the error reporting (to say that there is no upgrading a RO ISO when there’s only a STATE partition :/)
I’ll do some real testing tomorrow.
maik
January 26, 2017, 6:04pm
4
hi sven,
thanks for helping.
cheers maik
yeah, it looks like upgrading from an installed 0.7.1 to 0.8.0-rc6 works, but from 0.8.0-rc5 doesn’t.
another detail that i need to figure out
maik
January 27, 2017, 7:34pm
7
hi sven,
thanks for the fix.
if so is there some handy script to backup all my stuff on the server (was something i wanted to look into next week but maybe u can give me a tipp)?
so far i use a privat catalog where i have my stacks, so this is fine.rancher export function so im quick up with the functionality.
p.s. on another machine i just upgraded from rc6 to rc7 without any problems.
the last rc should be able to upgrade previous rc’s now
maik
January 31, 2017, 12:00pm
9
nice, thanks sven.
Hello,
I’m facing the same type of issue: sudo ros os version
v1.1.3
[rancher@rancher ~] sudo ros os list
[rancher@rancher ~] sudo ros os upgrade#1 SMP Sat Jan 6 00:16:10 UTC 2018
, , ______ _ _____ _____TM
,------------|’------’| | ___ \ | | / _ / | / /| | ___ _ __ | | | \ '–.’ | ’ \ / | ’ \ / _ \ '.’----’ | |\ \ (_| | | | | ( | | | | / | | _/ /_/ / ,| | |_|_ || | |_/ / _ _/ Linux 4.9.75-rancher
RancherOS #1 SMP Sat Jan 6 00:16:10 UTC 2018 rancher ttyS0
docker-sys: 172.18.42.2 eth0: 192.168.2.16 lo: 127.0.0.1
rancher login: rancher sudo ros os version
v1.1.3
[rancher@rancher ~]
I always end-up with 1.1.3
Looks like an issue on freenas
V.
