Bug 1337250
Summary: | ipxe freeze during HTTP download with last RPM | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Jason Guiditta <jguiditt> |
Component: | openstack-puppet-modules | Assignee: | Jason Guiditta <jguiditt> |
Status: | CLOSED ERRATA | QA Contact: | Raviv Bar-Tal <rbartal> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 9.0 (Mitaka) | CC: | achernet, apevec, dnavale, emacchi, gael_rehault, goneri, jason.dobies, jcoufal, jguiditt, kbasil, lhh, mburns, rhos-maint, srevivo |
Target Milestone: | ga | Keywords: | Triaged, ZStream |
Target Release: | 9.0 (Mitaka) | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | openstack-puppet-modules-8.1.1-1.el7ost | Doc Type: | Bug Fix |
Doc Text: |
Previously, iPXE would freeze during HTTP download resulting in the Bare Metal Provisioning (ironic) service to hang.
This update makes sure that iPXE retries to boot from the network in case of a failure. The '--timeout' option can be used to avoid an unlimited freeze. As a result, a freeze does not occur during the HTTP download.
|
Story Points: | --- |
Clone Of: | 1336473 | Environment: | |
Last Closed: | 2016-08-11 12:20:37 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: | |||
Bug Depends On: | 1336473 | ||
Bug Blocks: |
Comment 3
Jason Guiditta
2016-06-09 12:44:17 UTC
I'd prefer to get acks and move to on_qa so this gets tested. Keith, can you provide the ack, please? Jaromir, I believe you said you were the correct person to contact about setting the acks here. As noted earlier, we already have this functionality, but we want to keep the bug so the functionality can be properly QA'ed. Thanks Acutally, I see 8.0.6 was not rebuilt for osp, so I am going to just set it to newest osp build Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-1597.html |