Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1141428

Summary: Provisioning of RHEL-7 systems stalls with "Reached target Initrd Default Target"
Product: Red Hat Satellite Reporter: Sebastian Hetze <shetze>
Component: ProvisioningAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED NOTABUG QA Contact: Katello QA List <katello-qa-list>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.0.4CC: dcleal, mburgerh
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-16 11:30:08 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:
Attachments:
Description Flags
Screenshot of RHEL7 console: provisioning fails
none
Screenshot of RHEL7 console on old Sat5 setup: provisioning works none

Description Sebastian Hetze 2014-09-13 09:15:10 UTC
Created attachment 937185 [details]
Screenshot of RHEL7 console: provisioning fails

Description of problem:

Satellite-6 fails to provision new RHEL-7 hosts.
Provisioning stops with "[OK] Reached target Initrd Default Target." line.

Version-Release number of selected component (if applicable):
Satellite 6.0.4 (GA version)

How reproducible:

Steps to Reproduce:
1. Install new Sat6 and configure
2. Sync "Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server" and "Red Hat Enterprise Linux 7 Server Kickstart x86_64 7Server" from CDN
3. continue configuration to enable provisioning
4. create "New Host" with RHEL7 profile

Actual results:
Provisioning starts but stalls at "Reached target Initrd Default Target"

Expected results:
Provisioning should continue with "systemd-journald" and "Welcome to Red Hat Enterprise Linux" messages and start the actual installation.


Additional info:
* Provisioning of RHEL6 hosts works
* the 404 Not Found warnings regarding updates.img and product.img are
  misleading: a working Sat5 setup with older Kickstart Trees gives the
  same warnings and the provisioning succeeds.
* the 404 Not Found warning for .treeinfo is probably also misleading.
  There is a 7Server/x86_64/kickstart/treeinfo available, copying this
  to .treeinfo makes this message disapear but does not change the behaviour
* The provisioning worked with a Kickstart Tree from back when Sat6 Beta
  came out. It stopped working at least one week ago (Sept. 6.)

Comment 1 Sebastian Hetze 2014-09-13 09:16:27 UTC
Created attachment 937186 [details]
Screenshot of RHEL7 console on old Sat5 setup: provisioning works

Comment 2 RHEL Program Management 2014-09-13 09:22:55 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 4 Dominic Cleal 2014-09-15 14:53:36 UTC
Maybe you can verify the integrity of the initrd under /var/lib/tftpboot/boot as a starting point, and try resynchronising the CDN kickstart content?

Setting up remote syslog from the kickstart environment may help get data too, as I can't see much from the screenshot, let alone what might cause it to halt.

Comment 5 Sebastian Hetze 2014-09-16 07:28:43 UTC
Here are the MD5 sums of tftpboot/boot files. Can someone confirm that these are OK?

[root@satellite6 boot]# md5sum *
da8bcc37841248afcf5fdd49dfa5ce6d  foreman-discovery-image-latest.el6.iso-img
5afda342f2ed5ee61eb89a6d77d1f0e1  foreman-discovery-image-latest.el6.iso-vmlinuz
090434c5484d2d3552c0cc4d21ee63da  RedHat-6.5-x86_64-initrd.img
cdb61d5189c5b7af3caab5801f9e3f23  RedHat-6.5-x86_64-vmlinuz
5960d2340c6fded06f52d06d29878025  RedHat-7.0-x86_64-initrd.img
8edbd2e995aa094b8fb850eb1b0a9399  RedHat-7.0-x86_64-vmlinuz

Comment 6 Maxim Burgerhout 2014-09-16 10:29:53 UTC
These are mine, and these work for me:

f53f4a5c330faa434d7b73e5a76f82af  foreman-discovery-image-latest.el6.iso-img
5afda342f2ed5ee61eb89a6d77d1f0e1  foreman-discovery-image-latest.el6.iso-vmlinuz
5960d2340c6fded06f52d06d29878025  RedHat-7.0-x86_64-initrd.img
8edbd2e995aa094b8fb850eb1b0a9399  RedHat-7.0-x86_64-vmlinuz

I was curious about this, so I tested again whether RHEL 7 deployment works for me on a pristine 6.0 GA install of Satellite.

I did these tests: 

- Deploy with 1GB RAM VM: works fine
- Deploy with 768MB RAM VM: hangs at the same point as screenshot

After a *very* long time installation of the 768MB RAM VM continues, but *very* *very* slowly.

It was mentioned earlier that installation with 1GB RAM doesn't work for others, but maybe the amount of RAM does come into play here. I can do more tests tomorrow, if needed.

Comment 7 Sebastian Hetze 2014-09-16 11:16:27 UTC
Thanx Maxim for your feedback!
That's the problem.
Changing the RAM size in the Compute Profiles to 1G makes deployment of RHEL7 hosts work. For me no further tests regarding this case are needed.

I've openened a new bug regarding default RAM sizes in Compute Profiles
https://bugzilla.redhat.com/show_bug.cgi?id=1142207