Bug 1314172

Summary: [RHEL-7] gluster-swift: Backport fixes from swauth to gswauth
Product: Red Hat Gluster Storage Reporter: Prashanth Pai <ppai>
Component: gluster-swiftAssignee: Prashanth Pai <ppai>
Status: CLOSED ERRATA QA Contact: surabhi <sbhaloth>
Severity: low Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: nlevinki, rcyriac, rhinduja, rhs-bugs, thiago
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.1.3   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: swiftonfile-2.3.0-0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-23 05:31: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:
Bug Depends On:    
Bug Blocks: 1299184    

Description Prashanth Pai 2016-03-03 07:29:16 UTC
Description of problem:

This BZ tracks effort of rebasing gswauth to latest swauth code that has many fixes. This rebase effort is limited to back-porting relevant fixes to gswauth.

Backports on review:
http://review.gluster.org/#/q/project:gluster-swift+branch:master+topic:rebase-gswauth

Comment 2 Prashanth Pai 2016-03-10 09:15:21 UTC
There's a series of five upstream changes on review:
http://review.gluster.org/#/q/project:gluster-swift+branch:master+topic:rebase-gswauth

Comment 5 surabhi 2016-04-25 06:20:56 UTC
To verify this backport, took the latest build of swiftonfile with glusterfs latest build and executed the full regression suite for temp auth and gswauth , 
I see no failures or issues with the existing tests.
If in further testing find any issue with gswauth, will be raising another BZ.
Marking the BZ verified.

swiftonfile-2.3.0-2.el7rhgs.noarch
glusterfs-3.7.9-1.el7rhgs.x86_64

Comment 7 errata-xmlrpc 2016-06-23 05:31: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://access.redhat.com/errata/RHEA-2016:1289