Age | Commit message (Collapse) | Author |
|
Commit f34e9028 ("T5136: properly unmount filesystems after installation") assumed
it would be a good idea to simply rm -rf the new root folder. This could have
a bad, non booting side effect.
Warn user if unmount fails but the filesystem is synced anyway. The rest is
handled by the Kernel on reboot.
(cherry picked from commit 964e06bc3404b096d55e939b2bdb8d9c61a6a9b9)
|
|
(cherry picked from commit f34e9028252034cf17dbf380a2cded8bf14c71c2)
|
|
|
|
This reverts commit b3ce2cae043c96e9bc32fcb72527ce820c6593a0.
This breaks non UEFI installs
|
|
|
|
|
|
T1869: Install and Boot from RAID Doesn't Work
T1126: Reusing a RAID from a BIOS install in an EFI install causes a failure to boot
|
|
|
|
|
|
|
|
|
|
the default was still set to "Yes"
|
|
Fall back to MD5 if SHA256 checksums could not be found
Don't bother downloading .iso.sha256 files
(cherry picked from commit 085d0148c3d7d22afc5ce4fc10750b67c8cdfe26)
|
|
We will first download and try to verify the image using the generated minisign
signature. If this fails, we try to retrieve the GPG signature file.
|
|
menuentry
|
|
(#159)
* add search for same drive size if more than 2 drives are installed
* add ability to configure RAID-1 by selecting 2 drives
* cleaning up sysconf/filecaps rights
* cleaning up sysconf/filecaps rights xtables-monitor
|
|
These scripts have been superseded by the cloud-init tools, and contain
legacy references to XorpConfigParser.pm (via
vyatta-cfg/scripts/vyatta-load-config.pl, via ConfigLoad.pm), which one
would like to retire.
|
|
|
|
Updating a running VyOS installation by using the "add system image" command
pointing to https://downloads.vyos.io/rolling/current/amd64/vyos-rolling-latest.iso
will break the validation due to filename missmatch.
The root cause for this is the sha256 checksum file itself. It contains the hash
and the filename used when hashing. When running "sha256sum --check" during the
upgrade it expects the "real" filename when calculating and verifying the hash.
The real filename differs when using the vyos-rolling-latest.iso symlink on the
webserver as it will tell the running VyOS installation a different filename and
the validation fails.
This is now fixed by not depending on the filename when verifying the hash. We
simply calculate the hash of the downloaded file and compare it to the has we
saved inside the checksum file and totally ignore the filename itself.
|
|
Good:
=====
vyos@vyos:~$ add system image http://foo.com/vyos-1.3-rolling-202010180826-amd64.iso
Trying to fetch ISO file from http://foo.com/vyos-1.3-rolling-202010180826-amd64.iso
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 309M 100 309M 0 0 25.1M 0 0:00:12 0:00:12 --:--:-- 25.2M
ISO download succeeded.
Checking SHA256 (256-bit) checksum...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 106 100 106 0 0 26500 0 --:--:-- --:--:-- --:--:-- 26500
Found it. Verifying checksum...
SHA256 checksum valid.
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 Not Found
Unable to fetch digital signature file.
Do you want to continue without signature check? (yes/no) [yes]
Bad:
====
vyos@vyos:~$ add system image http://foo.com/vyos-1.3-rolling-202010180826-amd64.iso
Trying to fetch ISO file from http://foo.com/vyos-1.3-rolling-202010180826-amd64.iso
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 309M 100 309M 0 0 25.8M 0 0:00:11 0:00:11 --:--:-- 25.8M
ISO download succeeded.
Checking SHA256 (256-bit) checksum...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 106 100 106 0 0 9636 0 --:--:-- --:--:-- --:--:-- 9636
Found it. Verifying checksum...
vyos-1.3-rolling-202010180826-amd64.iso: FAILED
sha256sum: WARNING: 1 computed checksum did NOT match
Signature check FAILED.
Installation will not be performed.
Exiting...
|
|
|
|
When you connect via SSH and run the "add system image" command, it is launched
inside the VRF you are currently connected to. This might become confusing as
the VRF context changes.
Change command to always run in "default" vrf unless "add system image" command
is invoked with the vrf option.
|
|
|
|
This makes it easier to add VRF support.
|
|
|
|
* 'current' of github.com:vyos/vyatta-cfg-system:
syslog: T1845: migration script support bumps system to 12
syslog: T1845: migration script support bumps system to 12
Revert "syslog: T1845 bumping system version for migration script"
syslog: T1845 bumping system version for migration script
Fix rootdev regex to support mmcblk devices
geneve: T1799: add Generic Network Virtualization Encapsulation
|
|
|
|
Auto-merging scripts/rl-system.init
Auto-merging scripts/install/install-image
Auto-merging Jenkinsfile
|
|
|
|
|
|
xen extra checks, they use dmidecode which will not work in efi mode
Get the UUID of the correct partition based on the install type (bios/efi)
|
|
|
|
Update initramfs to include raidconfig avoiding md127 being created on reboot.
|
|
Set the default serial console speed to 115200 in system update scripts,
to accord with the changes in the build scripts.
|
|
|
|
|
|
(i.e. not the bind-mounted /config).
|
|
|
|
|
|
* Add grub-efi package dependencies
* Install grub-efi if we install on efi partition
|
|
|
|
|
|
Documentation https://github.com/vyos/vyatta-cfg-system/blob/current/scripts/install/install-functions#L90
(cherry picked from commit 1a05b1bfe0ccfd3f02a1cd4983b5f899364408c8)
|
|
|
|
configuration.
|
|
|
|
|
|
* upstream/current:
T507: add autocompletion or SSH key exchange algorithms
sometimes drives report they are not aligned
|
|
* c-po/remove-install-system-cmd:
Remove "install system" command
|
|
And then on reboot it hangs where it should start grub
|