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.
The installation will occasionally fail on virtual machines. This is due to the extra time which is taken for tomcat to start up and generate keys. The key generation requires entropy which is difficult to get on VMs which are headless.
Can we get some details on how the entropy was generated, etc., for this fix?
Also, need verification steps, specifically which type of VMs might be more prone to install failure.
No new entropy was generated, only the wait time was increased.
Verification is effectively a no-break install. I have been able to generate the error on kvm running on RHEL6, but I expect it to be very hardware specific. So, a successful install I believe is fair verification.
Verified in Sat 6.1 GA Snap 7
Successfully installed on VM 5 times. There may still be configurations that could block an installation on other VMs, but as long as the user follows the recommended guidelines in Satellite documentation, those should be few and far between.