Bug 1771917
Summary: | "Rebase" lvm2 to new upstream release 2.03.xx | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Marian Csontos <mcsontos> |
Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> |
lvm2 sub component: | Other | QA Contact: | cluster-qe <cluster-qe> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | unspecified | ||
Priority: | unspecified | CC: | agk, cmarthal, heinzm, jbrassow, msnitzer, prajnoha, rhandlin, zkabelac |
Version: | 8.2 | Keywords: | Rebase |
Target Milestone: | rc | ||
Target Release: | 8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | lvm2-2.03.08-1.el8 | Doc Type: | Rebase: Bug Fixes and Enhancements |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-28 16:58:59 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: |
Description
Marian Csontos
2019-11-13 08:57:21 UTC
Rebasing to bugfix release 2.03.08 containing no incompatible changes. Regression testing is well under way on what appears to be the final build for 8.2 with no major issues found so far. Marking this rebase tracker verified (SanityOnly). lvm2-2.03.08-3.el8 BUILT: Wed Mar 18 08:37:57 CDT 2020 lvm2-libs-2.03.08-3.el8 BUILT: Wed Mar 18 08:37:57 CDT 2020 lvm2-dbusd-2.03.08-3.el8 BUILT: Wed Mar 18 08:40:15 CDT 2020 lvm2-lockd-2.03.08-3.el8 BUILT: Wed Mar 18 08:37:57 CDT 2020 device-mapper-1.02.169-3.el8 BUILT: Wed Mar 18 08:37:57 CDT 2020 device-mapper-libs-1.02.169-3.el8 BUILT: Wed Mar 18 08:37:57 CDT 2020 device-mapper-event-1.02.169-3.el8 BUILT: Wed Mar 18 08:37:57 CDT 2020 device-mapper-event-libs-1.02.169-3.el8 BUILT: Wed Mar 18 08:37:57 CDT 2020 device-mapper-persistent-data-0.8.5-3.el8 BUILT: Wed Nov 27 07:05:21 CST 2019 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-2020:1881 |