Bug 1454614
| Summary: | LVM uninstallable in Rawhide | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Richard W.M. Jones <rjones> |
| Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | agk, anprice, bmarzins, bmr, heinzm, jonathan, lvm-team, mcsontos, msnitzer, prajnoha, prockai, rjones, zkabelac |
| Target Milestone: | --- | ||
| 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: | 2017-05-23 09:32:08 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: | 910269 | ||
|
Description
Richard W.M. Jones
2017-05-23 07:47:17 UTC
It is provided for both Server and Workstation. Is this a spin or other "product"? Cloud/container/atomic-whatever? What repos do you have configured? This is in Rawhide, there are no spins. See the failing build: https://koji.fedoraproject.org/koji/taskinfo?taskID=19701375 device-mapper-persistent-data-0.7.0-0.1.rc6.fc27 https://koji.fedoraproject.org/koji/buildinfo?buildID=873112 Oh, looks like mass rebuilt build wrong branches. See releng tasks. https://koji.fedoraproject.org/koji/packageinfo?packageID=13011 Let's check if some other packages are affected... Caused by mass rebuild: https://pagure.io/releng/issue/6807 I submitted new builds to fix it. It will take a while to propagate to repos though. The newly built package is here: https://koji.fedoraproject.org/koji/buildinfo?buildID=896547 It seems to be fixed by your rebuild of device-mapper-persistent-data just now, thanks. |