Bug 1209695
Summary: | yum/dnf changes break composoing ostree trees | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dennis Gilmore <dennis> |
Component: | rpm-ostree | Assignee: | Colin Walters <walters> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 22 | CC: | agrimm, awilliam, dgregor, kevin, mattdm, robatino, satellitgo, walters |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | RejectedBlocker AcceptedFreezeException | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-04-14 21:09:05 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: | 1043128 |
Description
Dennis Gilmore
2015-04-08 01:56:02 UTC
For the record, automatic blocker process: https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Automatic_blockers "Bugs which entirely prevent the composition of one or more of the release-blocking images required to be built for a currently-pending (pre-)release" (though, uh, when did we decide the Atomic images were release-blocking?) So in fact the RC1 Atomic images *did* compose, therefore this shouldn't be an automatic blocker. Moving it to proposed so we can discuss its actual impact. Are the Atomic images completely broken/wrong in some regard? the atomic images have an unknown tree installed, that is another bug that should also be a blocker. this is a blocker. it's not on the list of automatic blocker issues, therefore you can't just throw an AcceptedBlocker tag at it. Part of the point is so that we'll have a discussion of what's actually going on and what the resolution needs to be - this is useful even for 'obvious' blockers. rpm-ostree-2015.3-7.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/rpm-ostree-2015.3-7.fc22 Cloud WG agreed at a meeting today that the Atomic images are not considered 'release blocking', I believe, which makes this not a blocker bug. I'm +1 FE, though. Yeah, I think it will be a shame if we don't ship ostree trees in beta, but oh well. Definitely +1 FE. Package rpm-ostree-2015.3-7.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing rpm-ostree-2015.3-7.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-5905/rpm-ostree-2015.3-7.fc22 then log in and leave karma (feedback). Discussed at 2015-04-09 Go/No-Go meeting, acting as a blocker review meeting: https://meetbot.fedoraproject.org/fedora-meeting-2/2015-04-09/f22_beta_gono-go_meeting.2015-04-09-17.00.html . Rejected as a blocker, as Cloud WG determined that the Atomic images are not release blocking at present. Accepted as a freeze exception, as we would like to fix them if possible. Update has gone stable, closing. |