Bug 1232699
| Summary: | Meta volume is not used in geo-replication even with 'use meta volume' config option set to true by default. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Arthy Loganathan <aloganat> | ||||
| Component: | rhsc | Assignee: | anmol babu <anbabu> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Arthy Loganathan <aloganat> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | rhgs-3.1 | CC: | knarra, nlevinki, rhs-bugs, rnachimu, sabose | ||||
| Target Milestone: | --- | ||||||
| Target Release: | RHGS 3.1.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | rhsc-3.1.0-62 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-07-29 05:34:04 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: | 1202842 | ||||||
| Attachments: |
|
||||||
Basically, the issue here is that if use_meta_volume is not set for a session, gluster doesn't list it in the session config command and hence we populate it through our master data in db. Also, from the db the allowed values for this config i.e, true and false are available. The ui by default puts true selected and it appears as if true is set on the option when user opens config window which is wrong. Actaully setting the option to true just to overcome this issue isn't correct. And hence now with the fix UI defaults to false which doesn't mean the use_meta_volume is set to false on gluster but absence of option is equivalent to option being false(might need to confirm although). Verified the fix in build, rhsc-3.1.0-0.62.el6.noarch use_meta_volume option is set to true and lock files are present in meta volume mount directory I am still seeing the issue, hence moving this bug to ASSIGNED state. Arthy: Upgrading from previous build of rhsc (previous everglades) is not supported. Can u do a fresh install of rhsc 3.1 and verify?. After doing fresh install, verified the fix in build, rhsc-3.1.0-0.62.el6.noarch use_meta_volume option is set to false by default and when use_meta_volume is set to true, lock files are present in meta volume mount directory 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://rhn.redhat.com/errata/RHEA-2015-1494.html |
Created attachment 1039872 [details] vdsm logs Description of problem: Meta volume is not used in geo-replication even with 'use meta volume' config option set to true by default. Version-Release number of selected component (if applicable): rhsc-3.1.0-0.60.el6.noarch How reproducible: Always Steps to Reproduce: 1. Create a geo rep session. 2. Create meta volume using cmd, gluster volume set all cluster.enable-shared-storage enable 3. Set meta volume option to True in geo replication sub tab of the master volume in UI. 4. Start a geo rep session. 5. Ensure use_meta_volume config option is set to true in rhs node cli output. gluster volume geo-replication <master vol> <user_name>@<slave_host_given_while_you_create_session>::<slave_volume> config Actual results: use_meta_volume option is not set to true in cli. Hence, in meta volume mount directory(/var/run/gluster/shared_storage) lock files are not present. Expected results: use_meta_volume option sould be set to true and lock files should be present in meta volume mount directory Additional info: [root@node1 ~]# gluster volume geo-replication vol1 root.46.83::vol1_slave config special_sync_mode: partial state_socket_unencoded: /var/lib/glusterd/geo-replication/vol1_10.70.46.83_vol1_slave/ssh%3A%2F%2Froot%4010.70.46.83%3Agluster%3A%2F%2F127.0.0.1%3Avol1_slave.socket gluster_log_file: /var/log/glusterfs/geo-replication/vol1/ssh%3A%2F%2Froot%4010.70.46.83%3Agluster%3A%2F%2F127.0.0.1%3Avol1_slave.gluster.log ssh_command: ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/secret.pem ignore_deletes: false change_detector: changelog gluster_command_dir: /usr/sbin/ state_file: /var/lib/glusterd/geo-replication/vol1_10.70.46.83_vol1_slave/ssh%3A%2F%2Froot%4010.70.46.83%3Agluster%3A%2F%2F127.0.0.1%3Avol1_slave.status remote_gsyncd: /nonexistent/gsyncd log_file: /var/log/glusterfs/geo-replication/vol1/ssh%3A%2F%2Froot%4010.70.46.83%3Agluster%3A%2F%2F127.0.0.1%3Avol1_slave.log changelog_log_file: /var/log/glusterfs/geo-replication/vol1/ssh%3A%2F%2Froot%4010.70.46.83%3Agluster%3A%2F%2F127.0.0.1%3Avol1_slave-changes.log socketdir: /var/run/gluster working_dir: /var/lib/misc/glusterfsd/vol1/ssh%3A%2F%2Froot%4010.70.46.83%3Agluster%3A%2F%2F127.0.0.1%3Avol1_slave state_detail_file: /var/lib/glusterd/geo-replication/vol1_10.70.46.83_vol1_slave/ssh%3A%2F%2Froot%4010.70.46.83%3Agluster%3A%2F%2F127.0.0.1%3Avol1_slave-detail.status session_owner: 419fac15-cdff-4dfe-b14a-e34d1f9b43a2 ssh_command_tar: ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/tar_ssh.pem pid_file: /var/lib/glusterd/geo-replication/vol1_10.70.46.83_vol1_slave/ssh%3A%2F%2Froot%4010.70.46.83%3Agluster%3A%2F%2F127.0.0.1%3Avol1_slave.pid georep_session_working_dir: /var/lib/glusterd/geo-replication/vol1_10.70.46.83_vol1_slave/ gluster_params: aux-gfid-mount acl volume_id: 419fac15-cdff-4dfe-b14a-e34d1f9b43a2