Bug 986458
Summary: | gluster-swift-gen-builders should show user where the ring files are created | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Luis Pabón <lpabon> |
Component: | gluster-swift | Assignee: | crisbud <crisbud> |
Status: | CLOSED ERRATA | QA Contact: | pushpesh sharma <psharma> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.1 | CC: | bbandari, madam, rhs-bugs, sdharane, vagarwal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-23 22:32:33 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
Luis Pabón
2013-07-19 20:38:40 UTC
Should we modify the script to cd to /etc/swift directory prior to start ? Rather thank asking user to copy it to /etc/swift. IMO, the rings file generated by gluster-swift-gen-builders should need to overwrite the existing ring files in order get started. I can provide an option of backing up earlier ring file <if any> to a backup_ring_files folder in /etc/swift. Please let me know if this make sense. luster-swift-gen-builders behaviour changes gluster-swift-gen-builders copies the older ring files to /etc/swift/backup_ring. And then creates the new ring files to /etc/swift BUG: 986458 Change-Id: I06e93179e46da56d5046419e66c8864aa08f184d Signed-off-by: Chetan Risbud <crisbud> Reviewed-on: http://review.gluster.org/5384 Reviewed-by: Luis Pabon <lpabon> Tested-by: Luis Pabon <lpabon> Merged to upstream http://review.gluster.org/#/c/5457/ merged to release 1.8 as well. In version gluster-swift-plugin-1.8.0-6 [root@mater ~]# gluster-swift-gen-builders test test2 mkdir: cannot create directory `/etc/swift/backup_rings': File exists WARNING: No region specified for z1-127.0.0.1:6012/test_. Defaulting to region 1. Device r1z1-127.0.0.1:6012/test_"" with 100.0 weight got id 0 WARNING: No region specified for z2-127.0.0.1:6012/test2_. Defaulting to region 1. Device r1z2-127.0.0.1:6012/test2_"" with 100.0 weight got id 1 Reassigned 2 (100.00%) partitions. Balance is now 0.00. account.builder, build version 2 2 partitions, 1.000000 replicas, 1 regions, 2 zones, 2 devices, 0.00 balance The minimum number of hours before a partition can be reassigned is 1 Devices: id region zone ip address port name weight partitions balance meta 0 1 1 127.0.0.1 6012 test 100.00 1 0.00 1 1 2 127.0.0.1 6012 test2 100.00 1 0.00 mkdir: cannot create directory `/etc/swift/backup_rings': File exists WARNING: No region specified for z1-127.0.0.1:6011/test_. Defaulting to region 1. Device r1z1-127.0.0.1:6011/test_"" with 100.0 weight got id 0 WARNING: No region specified for z2-127.0.0.1:6011/test2_. Defaulting to region 1. Device r1z2-127.0.0.1:6011/test2_"" with 100.0 weight got id 1 Reassigned 2 (100.00%) partitions. Balance is now 0.00. container.builder, build version 2 2 partitions, 1.000000 replicas, 1 regions, 2 zones, 2 devices, 0.00 balance The minimum number of hours before a partition can be reassigned is 1 Devices: id region zone ip address port name weight partitions balance meta 0 1 1 127.0.0.1 6011 test 100.00 1 0.00 1 1 2 127.0.0.1 6011 test2 100.00 1 0.00 mkdir: cannot create directory `/etc/swift/backup_rings': File exists WARNING: No region specified for z1-127.0.0.1:6010/test_. Defaulting to region 1. Device r1z1-127.0.0.1:6010/test_"" with 100.0 weight got id 0 WARNING: No region specified for z2-127.0.0.1:6010/test2_. Defaulting to region 1. Device r1z2-127.0.0.1:6010/test2_"" with 100.0 weight got id 1 Reassigned 2 (100.00%) partitions. Balance is now 0.00. object.builder, build version 2 2 partitions, 1.000000 replicas, 1 regions, 2 zones, 2 devices, 0.00 balance The minimum number of hours before a partition can be reassigned is 1 Devices: id region zone ip address port name weight partitions balance meta 0 1 1 127.0.0.1 6010 test 100.00 1 0.00 1 1 2 127.0.0.1 6010 test2 100.00 1 0.00 mater proxy-server Client disconnected without sending enough data (txn: tx12da5da3632c4b3ca20c47a53f8a941f) (client_ip: 127.0.0.1) Aug 18 15:15:51 mater proxy-server 127.0.0.1 127.0.0.1 18/Aug/2013/19/15/51 PUT /v1/AUTH_test/dir/10.img HTTP/1.0 499 - curl/7.19.7%20%28x86_64-redhat-linux-gnu%29%20libcurl/7.19.7%20NSS/3.14.3.0%20zlib/1.2.3%20libidn/1.18%20libssh2/1.4.2 test%2CAUTH_tke4a76ae4646e48b8ac626771cd1d6578 1777876992 89 - tx12da5da3632c4b3ca20c47a53f8a941f - 24.9707 - Aug 18 17:28:54 mater kernel: hrtimer: interrupt took 15531974 ns [root@mater ~]# rpm -qa|grep swift gluster-swift-container-1.8.0-6.11.el6rhs.noarch python-swiftclient-1.4.0-1.el6.noarch gluster-swift-plugin-1.8.0-6.el6rhs.noarch gluster-swift-proxy-1.8.0-6.11.el6rhs.noarch gluster-swift-account-1.8.0-6.11.el6rhs.noarch gluster-swift-1.8.0-6.11.el6rhs.noarch gluster-swift-object-1.8.0-6.11.el6rhs.noarch [root@mater ~]# New code changes are posted for review and merged to master, upstream. http://review.gluster.org/#/c/5658/ Changes have been merged to release 1.8 as well. http://review.gluster.org/#/c/5667/ *** Bug 986456 has been marked as a duplicate of this bug. *** [root@mater etc]# gluster-swift-gen-builders test WARNING: No region specified for z1-127.0.0.1:6012/test_. Defaulting to region 1. Device r1z1-127.0.0.1:6012/test_"" with 100.0 weight got id 0 Reassigned 2 (100.00%) partitions. Balance is now 0.00. account.builder, build version 1 2 partitions, 1.000000 replicas, 1 regions, 1 zones, 1 devices, 0.00 balance The minimum number of hours before a partition can be reassigned is 1 Devices: id region zone ip address port name weight partitions balance meta 0 1 1 127.0.0.1 6012 test 100.00 2 0.00 WARNING: No region specified for z1-127.0.0.1:6011/test_. Defaulting to region 1. Device r1z1-127.0.0.1:6011/test_"" with 100.0 weight got id 0 Reassigned 2 (100.00%) partitions. Balance is now 0.00. container.builder, build version 1 2 partitions, 1.000000 replicas, 1 regions, 1 zones, 1 devices, 0.00 balance The minimum number of hours before a partition can be reassigned is 1 Devices: id region zone ip address port name weight partitions balance meta 0 1 1 127.0.0.1 6011 test 100.00 2 0.00 WARNING: No region specified for z1-127.0.0.1:6010/test_. Defaulting to region 1. Device r1z1-127.0.0.1:6010/test_"" with 100.0 weight got id 0 Reassigned 2 (100.00%) partitions. Balance is now 0.00. object.builder, build version 1 2 partitions, 1.000000 replicas, 1 regions, 1 zones, 1 devices, 0.00 balance The minimum number of hours before a partition can be reassigned is 1 Devices: id region zone ip address port name weight partitions balance meta 0 1 1 127.0.0.1 6010 test 100.00 2 0.00 Ring files are prepared in /etc/swift [root@mater etc]# rpm -qa|grep swift gluster-swift-container-1.8.0-6.11.el6rhs.noarch gluster-swift-proxy-1.8.0-6.11.el6rhs.noarch gluster-swift-account-1.8.0-6.11.el6rhs.noarch gluster-swift-plugin-1.8.0-7.el6rhs.noarch gluster-swift-1.8.0-6.11.el6rhs.noarch gluster-swift-object-1.8.0-6.11.el6rhs.noarch Ring files are created in /etc/swift irrespective of where the gen builder is ran. Marking as fix, based on the above observation. 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. http://rhn.redhat.com/errata/RHBA-2013-1262.html |