Upgrade 1.1.8 to vyos-rolling-latest - problems

Bugs
, , ,
1

Hello fellows, how are you?
Please let me know if this issue below is a BUG. I’m trying to do a upgrade from vyos 1.1.8 to latest rolling version, following the steps below:

My current version:
show version
Version: VyOS 1.1.8
Description: VyOS 1.1.8 (helium)
Copyright: 2017 VyOS maintainers and contributors
Built by: maintainers@vyos.net
Built on: Sat Nov 11 12:59:07 UTC 2017
Build ID: 1711111259-b483efc
System type: x86 32-bit
Boot via: image
HW model: Series 3500
HW S/N: 1XS4TR1
HW UUID: 44454C4C-5800-1053-8034-B1C04F545231
Uptime: 04:53:41 up 36 min, 2 users, load average: 0.28, 0.30, 0.37

Procedures:

add system image VyOS Community

Output:
Trying to fetch ISO file from VyOS Community
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 409M 100 409M 0 0 13.7M 0 0:00:29 0:00:29 --:–:-- 16.3M
ISO download succeeded.
Checking for digital signature file…
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
curl: (22) The requested URL returned error: 404
Unable to fetch digital signature file.
Do you want to continue without signature check? (yes/no) [yes] y
Checking MD5 checksums of files on the ISO image…OK.
Error trying to mount a partition/directory.
Please see /tmp/install-16884.log for details.
Failed to mount the squashfs image.
Exiting…

cat /tmp/install-16884.log
Error trying to mount a partition/directory.
mount -o loop,ro /mnt/cdrom/live/filesystem.squashfs /mnt/cdsquash
mount: wrong fs type, bad option, bad superblock on /dev/loop2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

Trying again:
add system image VyOS Community

Output:
add system image VyOS Community
Trying to fetch ISO file from VyOS Community
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 409M 100 409M 0 0 14.5M 0 0:00:28 0:00:28 --:–:-- 17.5M
ISO download succeeded.
Checking for digital signature file…
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- 0:00:01 --:–:-- 0
curl: (22) The requested URL returned error: 404
Unable to fetch digital signature file.
Do you want to continue without signature check? (yes/no) [yes] y
Checking MD5 checksums of files on the ISO image…OK.
Error trying to mount a partition/directory.
Please see /tmp/install-17362.log for details.
Failed to mount the squashfs image.
Exiting…
vyatta@ositel-C:~$ cat /tmp/install-17362.log
Error trying to mount a partition/directory.
mount -o loop,ro /mnt/cdrom/live/filesystem.squashfs /mnt/cdsquash
mount: wrong fs type, bad option, bad superblock on /dev/loop2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

So, how to proceed to do a safe upgrade? I’m trying this because some reason my system use high memory, keep low allow memory.

With Best Regards

Josue

2

Hi! I was updating my old VyOS instances to the latest version with an intermediate step, try to update 1.1.8 to 1.2.0 first, and then to the latest(or to the latest 1.2.x and then to 1.3.x).

Worked for me when 1.2.2 was the latest, but think that will work as well.

3

Hi Kirillk, how are you?
Thank you so much, for your reply, I’ll try this, but on Vyos portal, don’t found 1.2.x versions, just 1.3, so I found a snapshot version, like vyos-1.2-snapshot-2019Q4-amd64.iso, is fit to use?
The configurations that I use in 1.1.8 will be compatible with new versions?

With Best Regards

Josue

4

I tryed, but same error:
show version
Version: VyOS 1.1.8
Description: VyOS 1.1.8 (helium)
Copyright: 2017 VyOS maintainers and contributors
Built by: maintainers@vyos.net
Built on: Sat Nov 11 12:59:07 UTC 2017
Build ID: 1711111259-b483efc
System type: x86 32-bit
Boot via: image
HW model: Series 3500
HW S/N: 1XS4TR1
HW UUID: 44454C4C-5800-1053-8034-B1C04F545231
Uptime: 22:11:06 up 17:53, 1 user, load average: 0.37, 0.47, 0.43

add system image VyOS Community
Trying to fetch ISO file from VyOS Community
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 406M 100 406M 0 0 14.3M 0 0:00:28 0:00:28 --:–:-- 17.3M
ISO download succeeded.
Checking for digital signature file…
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 836 100 836 0 0 425 0 0:00:01 0:00:01 --:–:-- 1318
Found it. Checking digital signature…
gpg: directory /root/.gnupg' created gpg: new configuration file /root/.gnupg/gpg.conf’ created
gpg: WARNING: options in /root/.gnupg/gpg.conf' are not yet active during this run gpg: keyring /root/.gnupg/pubring.gpg’ created
gpg: Signature made Wed Dec 18 13:01:59 2019 GMT using RSA key ID A0FE6D7E
gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: Good signature from “VyOS Maintainers (VyOS Release) maintainers@vyos.net”
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 0694 A923 0F51 39BF 834B A458 FD22 0285 A0FE 6D7E
Digital signature is valid.
Checking MD5 checksums of files on the ISO image…OK.
Error trying to mount a partition/directory.
Please see /tmp/install-16820.log for details.
Failed to mount the squashfs image.
Exiting…

cat /tmp/install-16820.log
Error trying to mount a partition/directory.
mount -o loop,ro /mnt/cdrom/live/filesystem.squashfs /mnt/cdsquash
mount: wrong fs type, bad option, bad superblock on /dev/loop2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

Please do have idea?

With Best Regards

Josue

6

One thing I’ve found upgrading from 1.1.8 to 1.2.x is that the DHCP Server doesn’t seem to work at all after upgrading. Not sure why. The only way I was able to convert was to export the config file to external storage, do a fresh install of 1.2.4, and then reload the config file.

Obviously that means hand-migrating all crypto files, key files, etc from /config/auth as well.

And if you have any openvpn tunnels and you still want them to work, you should add “persistent-tunnel” to each interface stanza.

8

Hi corndog, how are you? thanks for your reply. We user just like a core router, with BGP peers and routing (static) for LAN customers.
But I’m worried, because the system is loading much ram memory and the idea was update system, to fix this issue, but not doing a new installation.

With Best Regards

Josue