Bug 1560066 - Request for downstream build from gluster-colonizer v1.1 tag
Summary: Request for downstream build from gluster-colonizer v1.1 tag
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-colonizer
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.3.1 Async
Assignee: Ramakrishna Reddy Yekulla
QA Contact: Nag Pavan Chilakam
URL:
Whiteboard:
Depends On: 1535403 1546492 1563582
Blocks: 1564133
TreeView+ depends on / blocked
 
Reported: 2018-03-23 20:11 UTC by Dustin Black
Modified: 2018-05-03 08:27 UTC (History)
5 users (show)

Fixed In Version: gluster-colonizer-1.1-2.el7rhgs.noarch.rpm
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-03 08:27:12 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:1317 0 None None None 2018-05-03 08:27:50 UTC

Description Dustin Black 2018-03-23 20:11:33 UTC 
Upstream release version 1.1 has been tagged. This is the intended basis for the next major downstream release.

https://github.com/gluster/gluster-colonizer/releases/tag/v1.1
Comment 2 Dustin Black 2018-04-02 15:38:42 UTC 
Due to performance concerns, we need to pull the below commits from upstream into the release build. Let me know if this requires a separate BZ for tracking.

41f110dffa7239d859f72735dfa14cce9681dcd1
118f59d3572a2f47f7f0c5db3c0e553e046e87cf
Comment 3 Dustin Black 2018-04-02 15:41:29 UTC 
Another update needed for the release build...

We previously wanted to exclude the playbook/ansible/g1-smb-ctdb.yml file because we did not yet have SMB enabled, but with this release we need this file in the downstream build.
Comment 5 Ramakrishna Reddy Yekulla 2018-04-04 04:45:29 UTC 
@Nag, I require a PM ack for this bug.
Comment 7 Nag Pavan Chilakam 2018-05-02 12:07:44 UTC 
moving this to verified as the testing is complete
Comment 10 errata-xmlrpc 2018-05-03 08:27:12 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-2018:1317
Note You need to log in before you can comment on or make changes to this bug.