Bug 963176
| Summary: | G4S: there is no automounting for gluster volumes for UFO thus all REST request fails,PUT with 404 ,GET/HEAD with 503 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | pushpesh sharma <psharma> | ||||
| Component: | object-storage | Assignee: | Thiago da Silva <thiago> | ||||
| Status: | CLOSED DEFERRED | QA Contact: | |||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.3.1 | CC: | bugs, david.macdonald, gluster-bugs | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-12-14 19:40:31 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: | |||||||
| Attachments: |
|
||||||
|
Description
pushpesh sharma
2013-05-15 10:33:59 UTC
Created attachment 748183 [details]
dmesgs
[root@dhcp207-238 swift]# rpm -qa|grep gluster glusterfs-fuse-3.3.1-14.fc18.x86_64 glusterfs-swift-account-3.3.1-14.fc18.noarch glusterfs-swift-proxy-3.3.1-14.fc18.noarch glusterfs-ufo-3.3.1-14.fc18.noarch glusterfs-server-3.3.1-14.fc18.x86_64 glusterfs-3.3.1-14.fc18.x86_64 glusterfs-swift-3.3.1-14.fc18.noarch glusterfs-swift-container-3.3.1-14.fc18.noarch glusterfs-swift-object-3.3.1-14.fc18.noarch manual mounting and building again does not help. [root@dhcp207-232 swift]# cat /etc/issue Fedora release 18 (Spherical Cow) Kernel \r on an \m (\l) [root@dhcp207-232 swift]# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/vg-lv6 10475520 33104 10442416 1% /mnt/lv6 /dev/mapper/vg-lv7 10475520 33104 10442416 1% /mnt/lv7 /dev/mapper/vg-lv8 10475520 33104 10442416 1% /mnt/lv8 /dev/mapper/vg-lv9 10475520 32976 10442544 1% /mnt/lv9 curl -v http://10.65.207.232:8080/v1/AUTH_test * About to connect() to 10.65.207.232 port 8080 (#0) * Trying 10.65.207.232... * connected * Connected to 10.65.207.232 (10.65.207.232) port 8080 (#0) > GET /v1/AUTH_test HTTP/1.1 > User-Agent: curl/7.27.0 > Host: 10.65.207.232:8080 > Accept: */* > < HTTP/1.1 204 No Content < X-Account-Container-Count: 0 < X-Account-Object-Count: 0 < X-Bytes-Used: 0 < X-Timestamp: 1368629841.43600 < X-Object-Count: 0 < X-Account-Bytes-Used: 0 < X-Type: Account < X-Container-Count: 0 < Accept-Ranges: bytes < Content-Length: 0 < Date: Thu, 16 May 2013 13:17:26 GMT < * Connection #0 to host 10.65.207.232 left intact * Closing connection #0 [root@dhcp207-232 swift]# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/vg-lv6 10475520 33104 10442416 1% /mnt/lv6 /dev/mapper/vg-lv7 10475520 33104 10442416 1% /mnt/lv7 /dev/mapper/vg-lv8 10475520 33104 10442416 1% /mnt/lv8 /dev/mapper/vg-lv9 10475520 32976 10442544 1% /mnt/lv9 localhost:test 41902080 132480 41769600 1% /mnt/gluster-object/test Please point me to the machine on which this is reproducible. Pushpesh, I figure see the problem with your script. The line Generate builders: cd /etc/swift ; /usr/bin/gluster-swift-gen-builders test ; /usr/bin/gluster-swift-gen-builders test2 The problem with this line is when you run /usr/bin/gluster-swift-gen-builders test2, it overwrites the pervious builders. Can you try Generate builders: cd /etc/swift ; /usr/bin/gluster-swift-gen-builders test test2 Will verify this again with multiple volumes , once gluster-sift upstream rpms are available. Works as expected with latest, upstream G4S.Documentation is updated to mount manually and run the ring builder. The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug. If there has been no update before 9 December 2014, this bug will get automatocally closed. |