Bug 1685005 - Heketi sets "user.heketi.zone-checking" to strict or none based on DC/template settings & not based on settings in the SC used
Summary: Heketi sets "user.heketi.zone-checking" to strict or none based on DC/templat...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: heketi
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: OCS 3.11.z Batch Update 3
Assignee: John Mulligan
QA Contact: Ashmitha Ambastha
URL:
Whiteboard:
: 1685979 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-04 06:35 UTC by Ashmitha Ambastha
Modified: 2019-06-13 13:47 UTC (History)
13 users (show)

Fixed In Version: heketi-8.0.0-11.el7rhgs
Doc Type: Bug Fix
Doc Text:
Previously, volume options provided with the "user.heketi" prefix was handled in an unexpected order that did not match with the behavior seen in gluster. Now, when any options that start with the "user.heketi" prefix is specified multiple times, the final option in the list takes precedence.
Clone Of:
Environment:
Last Closed: 2019-06-13 13:47:35 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:1408 0 None None None 2019-06-13 13:47:40 UTC

Comment 3 RamaKasturi 2019-03-04 17:23:17 UTC 
Hello John,

     As discussed during our downstream meeting today and since we are going to document both the ways (environment variable plus volume options in sc) of setting the heketi_zone , do you think we need to mark this as a known issue so that customers are aware of this ?

Thanks
kasturi
Comment 4 John Mulligan 2019-03-04 20:13:15 UTC 
(In reply to RamaKasturi from comment #3)
> Hello John,
> 
>      As discussed during our downstream meeting today and since we are going
> to document both the ways (environment variable plus volume options in sc)
> of setting the heketi_zone , do you think we need to mark this as a known
> issue so that customers are aware of this ?
> 
> Thanks
> kasturi

No, if it using the setting of the environment variable over the volume option that is a bug that we must fix IMO.



That said I can't reproduce the behavior reported. When I set the zone checking to "strict" globally (via config) and then set the volume option value to "none" it used "none" to create the volume and also recorded "none" in the gluster metadata.

Do you have a cluster exhibiting the behavior right now? If not, are you able to reproduce on demand?
Comment 8 Ashmitha Ambastha 2019-03-07 02:52:24 UTC 
Hi John, 

After a lot of debugging, I see that there is no issue with respect to the precendence set between DC and SC. 
I'm closing this bug and I've raised another one for the actual issue, https://bugzilla.redhat.com/show_bug.cgi?id=1685979
Comment 9 Ashmitha Ambastha 2019-03-07 06:28:59 UTC 
Hi, 

There is a confusion, After tonnes of debugging I understood that it is a cosmetic issue and not a functional issue. 
And I agree with you that, the bug https://bugzilla.redhat.com/show_bug.cgi?id=1685979 is a DUPLICATE of this bug. 

Reopening this bug.
Comment 11 Ashmitha Ambastha 2019-03-07 06:30:04 UTC 
*** Bug 1685979 has been marked as a duplicate of this bug. ***
Comment 16 RamaKasturi 2019-03-28 12:50:37 UTC 
Acking this for 3.11.3
Comment 19 Anjana KD 2019-06-03 12:57:29 UTC 
Have updated the doc text, kindly review it for technical accuracy.
Comment 21 Anjana KD 2019-06-04 12:00:41 UTC 
Thanks, John.
Comment 23 errata-xmlrpc 2019-06-13 13:47:35 UTC 
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-2019:1408
Note You need to log in before you can comment on or make changes to this bug.