Bug 1483851
Summary: | [RHEL 7.5] support building qcow2 ppc64le guest images | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jaroslav Fedor <jfedor> |
Component: | releng | Assignee: | Lubos Kocman <lkocman> |
Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.5 | CC: | dgilmore, dtodorov, jvavra, jwboyer, lkocman, mbanas, snagar |
Target Milestone: | alpha | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-10 10:10:55 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: | 1516458 | ||
Bug Blocks: |
Description
Jaroslav Fedor
2017-08-22 06:59:04 UTC
clearing the needinfo as we have pm ack Hello Seems, like we've accidentally dropped ppc64le from configuration after merge of nightly and production image-build config. I did return it back and running test compose here /mnt/redhat/devel/lkocman/trees/RHEL-7.5-20171122.t.0/ Linking issue Image was successful https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=14615559 commiting change to production config (affects both nightly and production composes). http://git.app.eng.bos.redhat.com/git/rcm/rcm-metadata.git/commit/?id=5d2e93a8b1ece040ce7e723a8ca1b53c779a0af2 Running new nightly (referenced image was build as part of testing compose /mnt/redhat/devel/lkocman/trees/RHEL-7.5-20171123.t.0). Will be part of /mnt/redhat/nightly/RHEL-7.5-20171123.n.0 Available here http://download.eng.brq.redhat.com/nightly/latest-RHEL-7/compose/Server/ppc64le/images/rhel-guest-image-7.5-17.ppc64le.qcow2 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-2018:0700 |