Bug 1455295
| Summary: | failed x86 changes broke aarch64 cloud images | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Peter Robinson <pbrobinson> |
| Component: | distribution | Assignee: | Václav Pavlín <vpavlin> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 26 | CC: | awilliam, dennis, dustymabe, kevin, mboddu, pbrobinson, pschindl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | AcceptedFreezeException | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-07-01 15:29:20 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: | 245418, 1349187 | ||
|
Description
Peter Robinson
2017-05-24 16:53:59 UTC
Proposed as a Freeze Exception for 26-beta by Fedora user pbrobinson using the blocker tracking app because: This is a FE because it's a core release component for Alternate architectures. I'm +1 FE From my understanding alt arch qualify for FE under: "bugs which constitute infringements of Fedora_Release_Criteria for secondary architectures will be presumed to be valid freeze exception bugs (unless there is a strong argument against, in a particular case)" and since there is a release criteria of: 'Release-blocking cloud images must boot' (i.e. x86_64) then having aarch64 cloud images that don't boot mean they apply to the first block of text above and are valid for FE unless there is a strong argument against. (In reply to Peter Robinson from comment #0) > So Dusty pushed a badly tested change to the kickstarts that broke aarch64 > cloud images I would appreciate people not assigning blame to things like this. I'd like to point out that my change [1] that broke this went in 16 days ago, which was way before your most recent change [2], which went in 9 days ago. This means that whatever testing you may have done was flawed itself as well. I also didn't even know how to get access to aarch64 hardware until yesterday. And when i did finally get access to that hardware i was able to figure out and (hopefully) get the issues fixed. Assigning blame is not very productive here. [1] https://pagure.io/fedora-kickstarts/pull-request/219 [2] https://pagure.io/fedora-kickstarts/pull-request/227 As Dusty says he's tested this on x86_64, +1 FE. +1 FE +1 FE Discussed at 2017-05-30 blocker review meeting: [1]. This bug was accepted as beta freeze exception: A tested fix exists for this and we'd like to pull this in. [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2017-05-30/ Fixed |