Bug 1619603
| Summary: | Introducing new parameters to the vdo config file breaks compatability with RHEL7.5 [rhel-7.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | vdo | Assignee: | Joe Shimkus <jshimkus> |
| Status: | CLOSED ERRATA | QA Contact: | Jakub Krysl <jkrysl> |
| Severity: | unspecified | Docs Contact: | Marie Hornickova <mdolezel> |
| Priority: | high | ||
| Version: | 7.6 | CC: | awalsh, bgurney, corwin, jkrysl, jshimkus, limershe, rhandlin |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 6.1.0.184 | Doc Type: | Bug Fix |
| Doc Text: |
New parameters introduced to VDO volume configuration files in RHEL 7.6 previously broke compatibility with Red Hat Enterprise Linux 7.5. Consequently, the vdo utility failed to read the configuration file, and the VDO volume was not started. With this update, the problem has been fixed, and vdo is now able to start the old VDO volume as expected.
|
Story Points: | --- |
| Clone Of: | 1604060 | Environment: | |
| Last Closed: | 2018-11-06 16:16:04 UTC | Type: | --- |
| 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: | 1604060 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-08-21 09:57:48 UTC
Merged changes. tested with: kmod-kvdo-6.1.0.185-17.el7_5.x86_64 vdo-6.1.0.185-18.x86_6 Adding new lines and values to config does not prevent vdo from starting anymore. The description reasonable captures the issue. (In reply to Joe Shimkus from comment #6) > The description reasonable captures the issue. Hi Joe, Thanks a lot for the confirmation. Marie 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/RHBA-2018:3509 |