Description of problem: After installing with software raid, the ~/anaconda-ks.cfg does not have the commands to recreate the install. Version-Release number of selected component (if applicable): anaconda 19.25-1 How reproducible: Very. Steps to Reproduce: 1. Select Installation Destination 2. Select multiple disks 3. Select custom partitioning 4. Delete previous installs 5. Click here to create them automatically 6. Modify the / partition to use RAID 5 7. Modify the /home partition to use RAID 5 8. Click Done 9. Click Begin Installation Actual results: ~/anaconda-ks.cfg contains the following: 8<-----8<-----8<-----8<----- #version=DEVEL # System authorization information auth --enableshadow --passalgo=sha512 # Use CDROM installation media cdrom # Run the Setup Agent on first boot firstboot --enable ignoredisk --only-use=sda,sdb,sdc # Keyboard layouts keyboard --vckeymap=us --xlayouts='us' # System language lang en_US.UTF-8 # Network information network --bootproto=static --device=eth0 --gateway=9.5.114.1 --ip=9.5.114.36 --nameserver=9.10.244.100 --netmask=255.255.255.0 --noipv6 --activate network --bootproto=static --device=eth1 --gateway=9.5.114.1 --ip=9.5.114.41 --nameserver=9.10.244.100 --netmask=255.255.255.0 --noipv6 --activate network --hostname=sharpie.rch.stglabs.ibm.com # Root password rootpw --iscrypted $6$gPF/IbKNm4mcRtRp$.xiCi3pqCJef5rp.3XLMI9L1cdmU7p80w7G9AFRPzoD/ItjgNciRAWUXMsfjjv4AF/0s7fjEqkQOFLukxLkTP0 # System services services --enabled="chronyd" # System timezone timezone America/Chicago --isUtc user --groups=wheel --name=hamzy --password=$6$JtMdd/aHChrDcpuX$KVZGgjBr77fsSw05glHRpJaGWexStrvH/MkknaN29xF7PsCNQIRypMNrFZJZcdQv4nIRp6uOSc9LMti.HaH5t/ --iscrypted --gecos="Mark Hamzy" # System bootloader configuration bootloader --location=mbr --boot-drive=sda # Partition clearing information clearpart --none --initlabel --drives=sda,sdb,sdc %packages @core @standard chrony %end 8<-----8<-----8<-----8<----- Expected results: anaconda-ks.cfg should have part commands necessary to recreate the install. Additional info:
This one looks like a duplicate of bug 929119
Yeah, it is. Sorry to say it but this has not been a high priority item lately. *** This bug has been marked as a duplicate of bug 929119 ***