Bug 1701915 - rebuild rhgs-gluster-block-prov-container for 3.11.3
Summary: rebuild rhgs-gluster-block-prov-container for 3.11.3
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhgs-gluster-block-prov-container
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: OCS 3.11.z Batch Update 3
Assignee: Humble Chirammal
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-22 13:06 UTC by Raghavendra Talur
Modified: 2019-06-13 17:05 UTC (History)
7 users (show)

Fixed In Version: rhgs-gluster-block-prov-container-3.11.3-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-13 17:04:59 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:1470 0 None None None 2019-06-13 17:05:01 UTC

Description Raghavendra Talur 2019-04-22 13:06:47 UTC
Description of problem:
rebuild rhgs-gluster-block-prov-container for 3.11.3

Comment 4 RamaKasturi 2019-05-07 11:18:07 UTC
Moving the bug to verified state as i see that block-prov image has been respun .

sh-4.2$ cat /etc/redhat-storage-release 
Red Hat Gluster Block Provisioner 3.11.3 (Container)
sh-4.2$ cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.6 (Maipo)
sh-4.2$ ls -l /root/buildinfo/
total 8
-rw-r--r--. 1 root root 2798 Apr 16 15:34 Dockerfile-rhel7-7.6-252
-rw-r--r--. 1 root root 2204 Apr 23 22:02 Dockerfile-rhgs3-rhgs-gluster-block-prov-rhel7-3.11.3-1

Comment 6 errata-xmlrpc 2019-06-13 17:04:59 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/RHBA-2019:1470


Note You need to log in before you can comment on or make changes to this bug.