Bug 1463817

Summary:	Kickstart (re)install of host using 7.4-beta initrd fails on the xfs partition creation stage
Product:	Red Hat Enterprise Linux 7	Reporter:	Dan Yasny <dyasny>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	kwalker, mkolman
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-15 07:38:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dan Yasny 2017-06-21 19:42:14 UTC

Description of problem:
I usually rebuild my hosts as follows:
- download a fresh set of initrd and vmlinux to /boot
- create a "reinstall" grub entry pointing at a kickstart file on the network 
  grubby --add-kernel=/boot/vmlinuz --title=REINSTALL --args="text ks=http://mykickstart" --initrd=/boot/initrd.img --make-default
- restart the host

I had to reinstall a host today, whcih was running 7.3 with ext4 partitions (instead of the default xfs for some reason)

I downloaded the initrd from the internal 7.4-beta location

Install failed at the stage where it was supposed to clear the disk and recreate partitions with XFS, consistently repeated.

When I changed the initrd and vmlinuz to the older files from an internal 7.3 repo everything worked as expected

* See file locations in private comment

How reproducible:
always

Steps to Reproduce:
see above

Actual results:
see above

Expected results:
installation should work

Additional info:

Comment 3 Martin Kolman 2017-06-22 11:48:35 UTC

Please add logs from an affected installation run as separate plain-text
attachments. The log files should be located in /tmp during the installation and there is a root shell running on tty2.

Thanks in advance!

Comment 4 Dan Yasny 2017-06-22 13:30:34 UTC

Since the host has been reprovisioned successfully, using the 7.3 initramfs, it is now in production and cannot be set up as a reproducer. 

It should be fairly easy to reproduce, I provided all the steps and versions in use. If that is something your team cannot do, feel free to close the BZ, all I wanted to do was report on an issue I came across.

Comment 6 RHEL Program Management 2021-01-15 07:38:42 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.