Bug 1226457
Summary: | Install will occasionally fail on virtual machines | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Bryan Kearney <bkearney> |
Component: | Installation | Assignee: | Katello Bug Bin <katello-bugs> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | jcallaha |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | Unspecified | CC: | bkearney, cwelton, lzap |
Target Milestone: | Unspecified | ||
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://projects.theforeman.org/issues/10654 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-12 14:00:25 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
Bryan Kearney
2015-05-29 20:34:18 UTC
Created redmine issue http://projects.theforeman.org/issues/10654 from this bug fixed by 48e6321ccf9091fb41dc33d3c73846377f98e2a5 Moving to POST since upstream bug http://projects.theforeman.org/issues/10654 has been closed 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. *** Bug 1224256 has been marked as a duplicate of this bug. *** This bug is slated to be released with Satellite 6.1. This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015. |