Bug 1690895
| Summary: | RHEL8 based amphora image | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Nir Magnezi <nmagnezi> | ||||
| Component: | rhosp-director-images | Assignee: | Lon Hohberger <lhh> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Pavel Sedlák <psedlak> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 15.0 (Stein) | CC: | apevec, bcafarel, lhh, mburns, sbaker, sclewis | ||||
| Target Milestone: | rc | Keywords: | Triaged | ||||
| Target Release: | 15.0 (Stein) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | rhosp-director-images-15.0-20190614.3.el8ost | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-09-21 11:08:02 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: | |||||||
| Bug Blocks: | 1623857, 1708783 | ||||||
| Attachments: |
|
||||||
|
Description
Nir Magnezi
2019-03-20 12:27:27 UTC
Created attachment 1573922 [details] octavia-amphora-15.0-20190522_boot_fail.log Tested octavia-amphora-15.0-20190522, extracted from octavia-amphora-image-x86_64-15.0-20190526.1.el8ost.noarch.rpm It fails to boot, hence cannot function as a part of Octavia. I got the same results when I tried to build an amphora image from an existing rhel8 cloud image, see patch comments here: https://review.opendev.org/#/c/643731/ > I got the same results when I tried to build an amphora image from an existing rhel8 cloud image, see patch comments here: https://review.opendev.org/#/c/643731/ was this resolved by the latest patchset https://review.opendev.org/#/c/643731/25 ? 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://access.redhat.com/errata/RHEA-2019:2852 |