blkid & lsblk commands can fail in the kickstarts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Ovidiu Poncea |
Bug Description
Brief Description
-----------------
The kickstart code checks for the existence of the platform_backup partition and if any of its checks doesn't match what is is expecting the partition is created. There is no error checking on the various blkid/lsblk/parted commands used. On some occasions these commands fail to read data likely due to a udev bug. This leads to the wrong steps taken in the install (example the existing partition gets wiped and recreated causing all previous data to be lost).
The kickstart code needs to handle the possibility of commands failing or not reading proper data.
Severity
--------
Major
Steps to Reproduce
------------------
At this point it is not clear what disk will trigger the issue.
Expected Behavior
------------------
Installation should be able to properly detect if the platform_backup partition exists. And if the partition does not exist it should create the platform_backup partition properly.
Actual Behavior
----------------
The kickstarts sometimes re-create a platform_backup partition when it shouldn't. The kickstarts sometimes create the backup_partition with incorrect attributes (size or type or guid).
Reproducibility
---------------
Seen once. Difficult to reproduce.
System Configuration
-------
AIO-SX
Branch/Pull Time/Commit
-------
stx4.0 load
Last Pass
---------
n/a
Timestamp/Logs
--------------
n/a
Test Activity
-------------
testing
Workaround
----------
none
Marking stx.5.0 gating - issue is hard to reproduce and rarely seen but will lead to AIO-SX configuration set up incorrectly.