Bug 1371459 – [RFE] installer should deploy the atomic-registry console to normal OCP clusters by default

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1371459 - [RFE] installer should deploy the atomic-registry console to normal OCP clusters by default

Summary:	[RFE] installer should deploy the atomic-registry console to normal OCP clust...

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	RFE (Show other bugs)
Sub Component:
Version:	3.3.0
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	3.3.1
Assigned To:	Mike Barrett
QA Contact:	Johnny Liu
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-08-30 05:12 EDT by Johnny Liu
Modified:	2016-11-25 02:45 EST (History)
CC List:	8 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:	Starting in OCP 3.3.1 the new Registry Console is now deployed during OCP installation.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-10-27 12:13:15 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2016:2122	normal	SHIPPED_LIVE	OpenShift Container Platform atomic-openshift-utils bug fix update	2016-10-27 16:11:30 EDT

Groups: None (edit)

Description Johnny Liu 2016-08-30 05:12:33 EDT

Description of problem:
Currently installer only support standalone atomic registry deployment, s2i, web console in cluster will be disabled.  

Open this bug for requesting to deploy the atomic-registry console to normal OCP clusters by default as well.


Here is our discussion:
https://github.com/smunilla/openshift-ansible/commit/53d51db6f2da179e867009a0ab0b411ede7d9fe4#commitcomment-18811354


Version-Release number of selected component (if applicable):
openshift-ansible-3.3.16-1.git.0.9ed3fd2.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Eric Rich 2016-09-26 09:43:06 EDT

Upstream docs: 

[0] https://docs.openshift.org/latest/install_config/install/stand_alone_registry.html
[1] https://docs.openshift.org/latest/install_config/install/advanced_install.html#multiple-masters
[2] https://docs.openshift.org/latest/install_config/registry/deploy_registry_existing_clusters.html#deploying-the-registry-console

Comment 4 openshift-github-bot 2016-09-30 14:53:44 EDT

Commit pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/a3ab3d539bb57bc224b3f4457a0bfc68484cf8ee
Install Registry by Default

Instead of restricting cockpit-ui to Atomic Registry installations,
install it by default everywhere.

Fixes Bug 1371459

Comment 5 Johnny Liu 2016-10-10 03:50:30 EDT

This bug should be already fixed in openshift-ansible-3.3.30-1.git.0.b260e04.el7.noarch, now installer would deploy registry-console by default, once this bug is moved to ON_QA, will verify it.

Comment 6 Johnny Liu 2016-10-10 22:06:36 EDT

@Scott, would you mind attach this bug to 3.3.1 installer errata?

Comment 7 Johnny Liu 2016-10-10 23:41:00 EDT

Verified this bug with openshift-ansible-3.3.34-1.git.0.5b998bb.el7.noarch, and PASS.

Comment 9 errata-xmlrpc 2016-10-27 12:13:15 EDT

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-2016:2122

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