Bug 1638988
Summary: | embed/automate upgrade time genconfig steps within gluster-block | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Prasanna Kumar Kalever <prasanna.kalever> |
Component: | gluster-block | Assignee: | Prasanna Kumar Kalever <prasanna.kalever> |
Status: | CLOSED ERRATA | QA Contact: | Rahul Hinduja <rhinduja> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | ocs-3.11 | CC: | akrishna, asriram, bgoyal, knarra, kramdoss, nberry, pkarampu, pprakash, prasanna.kalever, rcyriac, rhs-bugs, sankarshan, suprasad, vbellur, xiubli |
Target Milestone: | --- | ||
Target Release: | OCS 3.11 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | gluster-block-0.2.1-28.el7rhgs | Doc Type: | Bug Fix |
Doc Text: |
Block volumes created on CNS version 3.9 or below use default Asymmetric Logical Unit Access (alua) group setting at target side configuration. These are meant to be used with 'prio const' at the initiator side multipath.conf. After upgrading OCS to 3.10 or above, the new recommendation at multipath is 'prio alua'. Old block volume having target side alua group set to default are not compatible with newly recommended multipath.conf. Hence, to maintain compatibility of old block volumes with the new multipath.conf recommendation, the default alua group should be changed to glfs alua group. With this update, the block volume target configuration is generated automatically as part of the upgrade to fix the comparability issue. And Hence, the compatibility of old block volume with the new multipath.conf recommendation is maintained.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-24 04:52:58 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: | 1629581, 1637688 |
Description
Prasanna Kumar Kalever
2018-10-13 19:52:52 UTC
@prasanna I have updated the doc text based on our discussion. (In reply to Anjana from comment #18) > @prasanna I have updated the doc text based on our discussion. LGTM, thanks Anjana! 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-2018:2987 Setting the qe_test_coverage flag as '-' as this looks like umbrella bug based on comment 16. |