Bug 1336648

Summary:	Period push fails while trying to connect to the remote machine
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	shilpa <smanjara>
Component:	RGW	Assignee:	Casey Bodley <cbodley>
Status:	CLOSED ERRATA	QA Contact:	shilpa <smanjara>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.0	CC:	cbodley, ceph-eng-bugs, hnallurv, kbader, kdreyer, mbenjamin, owasserm, smanjara, sweil
Target Milestone:	rc
Target Release:	2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-10.2.1-5.el7cp Ubuntu: ceph_10.2.1-4redhat1xenial	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-23 19:38: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 shilpa 2016-05-17 06:53:00 UTC

Description of problem:

While running the command from rgw2: 

# radosgw-admin period push --url=http://rgw1:8080 --access-key=access --secret=secret > could not find connection to: http://rgw1:8080 > request failed: (2) No such file or directory


Version-Release number of selected component (if applicable):
10.2.0-1.el7cp.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Configure multisite with two zones
2. Try period push from one of the zones to the other

Seems very specific to period push. The same url works for period pull, realm pull.

Comment 2 Casey Bodley 2016-05-18 19:46:23 UTC

upstream ticket: http://tracker.ceph.com/issues/15926

fix pending review: https://github.com/ceph/ceph/pull/9146

Comment 8 shilpa 2016-06-15 09:34:21 UTC

Tested on 10.2.1-18. Period push hangs with http Bad Request error in logs: 

2016-06-15 09:10:47.988997 7f79957fa700 10 master zone rejecting period id=f6036416-4895-4cc1-8174-e568307c113e epoch=6
2016-06-15 09:10:47.989002 7f79957fa700  2 req 11:1.001853::POST /admin/realm/period:post_period:completing
2016-06-15 09:10:47.989053 7f79957fa700  2 req 11:1.001904::POST /admin/realm/period:post_period:op status=0
2016-06-15 09:10:47.989059 7f79957fa700  2 req 11:1.001910::POST /admin/realm/period:post_period:http status=400
2016-06-15 09:10:47.989066 7f79957fa700  1 ====== req done req=0x7f79957f4710 op status=0 http_status=400 ======
2016-06-15 09:10:47.989074 7f79957fa700 20 process_request() returned -22


radosgw-admin period push --url=http://rgw2:8080 --access-key=access --secret=secret/admin/realm/period

The command does not exit and it hangs at this point:
 7fd2cd8509c0 15 generated auth header: AWS access:X9evui683/LMpyW+Gv+VryRmV4s=
 7fd2cd8509c0 20 sending request to http://rgw2:8080/admin/realm/period

Re-assigning it back.

Comment 9 Casey Bodley 2016-06-15 12:35:13 UTC

The command should not hang, that is indeed a bug. But the 'period push' is rejected because you can only change the master zone's configuration with 'period commit'.

Comment 10 Ken Dreyer (Red Hat) 2016-06-15 18:13:58 UTC

shilpa, it seems like the original reported bug is now fixed?

Would you please open a new BZ for the issue of period push hanging?

Comment 11 shilpa 2016-06-16 07:42:50 UTC

(In reply to Ken Dreyer (Red Hat) from comment #10)
> shilpa, it seems like the original reported bug is now fixed?
> 
> Would you please open a new BZ for the issue of period push hanging?


Agreed. The issue now seems to be unrelated to period push. Will follow this up in a different bug. Closing this. The original issue is fixed.

Comment 13 errata-xmlrpc 2016-08-23 19:38:33 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://rhn.redhat.com/errata/RHBA-2016-1755.html