Bug 1612016 - Galaxy - doesn't display "Retype Admin User Password" box while provisioning instance in web console
Summary: Galaxy - doesn't display "Retype Admin User Password" box while provisioning ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.0
Assignee: David Zager
QA Contact: Zhang Cheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-03 09:03 UTC by Zhang Cheng
Modified: 2018-10-11 07:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-11 07:23:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 0 None None None 2018-10-11 07:23:49 UTC

Comment 1 David Zager 2018-08-03 12:43:07 UTC 
Looking to address this on the Ansible Galaxy side.
Comment 2 David Zager 2018-08-06 14:52:15 UTC 
https://github.com/ansible/galaxy/pull/1027
Comment 3 David Zager 2018-08-08 18:55:30 UTC 
Right now galaxy.ansible.com is at version 3.0.5. The above fix will be released with 3.0.6.
Comment 4 David Zager 2018-08-15 19:46:16 UTC 
Looks like the commit was moved out of 3.0.6 and into 3.0.8. The production galaxy instance is at 3.0.7, next release should include this fix.
Comment 5 Zhang Cheng 2018-08-27 06:11:21 UTC 
Verified and Passed.
Changing status to Verified.

Server galaxy.ansible.com
Server Version 3.0.8
Comment 7 errata-xmlrpc 2018-10-11 07:23:29 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-2018:2652
Note You need to log in before you can comment on or make changes to this bug.