Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1734290

Summary: Console cannot create clusterwide etcdcluster with forms
Product: OpenShift Container Platform Reporter: shahan <hasha>
Component: Management ConsoleAssignee: Alec Merdler <amerdler>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: aos-bugs, jokerman, spadgett
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:33:52 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:
Embargoed:

Description shahan 2019-07-30 07:46:05 UTC
Description of problem:
 Console cannot create clusterwide etcdcluster with forms since no scope annotations created for it.

Version-Release number of selected component (if applicable):
  4.2.0-0.nightly-2019-07-29-154123

How reproducible:
  Always

Steps to Reproduce:
1. Login webconsole and install clusterwide etcd operator
2. Goto /operators.coreos.com~v1alpha1~ClusterServiceVersion/etcdoperator.v0.9.4-clusterwide/etcd.database.coreos.com~v1beta2~EtcdCluster page, click create etcd cluster then create with form
3.

Actual results:
 Cannot get the status of etcd members and console shows "The field status.members is invalid"

Expected results:
Should create etcdcluster successfully

Additional info:
 Console should add following annotations to clusteretcd creating by forms.
 metadata:
  annotations:
    etcd.database.coreos.com/scope: clusterwide

Comment 1 Samuel Padgett 2019-07-31 00:32:14 UTC
https://github.com/openshift/console/pull/2224

Comment 3 shahan 2019-08-16 06:40:40 UTC
Could create etcd cluster successfully.
4.2.0-0.nightly-2019-08-15-205330

Comment 4 errata-xmlrpc 2019-10-16 06:33:52 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:2922