vmtest: fix image-sync after maas URL stream rename
Image syncing for vmtest has been failing since MAAS renamed their
daily image stream to stable. In an effort to keep the 'daily' URL
valid the website redirects this to 'stable' path. However the content
was also modified and includes references to files and URLs which have
the 'stable' name included. This broke vmtest image sync which expected
the 'daily' string to be present in filenames and content.
The observable result was that curtin would attempt to find content it
had just *synced* to /srv/images but when searching, it would load up
the cached content files which only referenced the 'daily' stream data
and would indicate that the target file was missing.
This branch moves vmtest to using the 'stable' maas image stream
directly. This value is controllable via an environment variable,
MAAS_IMAGE_STREAM, if set will be used to compose the IMAGE_SRC_URL
and the STREAM_BASE variable which is used to find cached content in
/srv/images/.vmtest_data/ directory.
install_grub: Fix bootloader-id for RHEL systems, must be redhat
In 7310b4fe61465, the port from shell dropped a change where the boot-id
value for Redhat family OSes is the value 'redhat' not the os-release ID
value (which is rhel, on RHEL systems).
Add this change back to install_grub and fix unittests that fail with
'rhel' instead of 'redhat' in os-release values. Hardcode 'redhat'
paths in expected values.
The storage_config handling of dasds only accounted for ECKD
dasds. FBA dasds need different handling -- in many ways they are
more like a regular disk (that can only be formatted with a DOS
partition table, but this code doesn't need to handle that), but
the kernel creates a magic fake partition for a FBA dasd with no
DOS partition table and we want to pretend that doesn't exist.
e099e32...
by
Nishanth Aravamudan <email address hidden>
apt_config: stop using the deprecated apt-key command
This applies the same changes as apt-setup has for
dumping the keys specified in the configuration to
the target filesystem.
Now that the only thing we need dasdview output for is to determine
the format type of the dasd (ldl vs cdl vs unformatted) we can make
a few things simpler.
