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

Bug 1717623

Summary:	OLM installed operators are not getting new version numbers in the release pipeline
Product:	OpenShift Container Platform	Reporter:	Jessica Forrester <jforrest>
Component:	Release	Assignee:	Tim Bielawa <tbielawa>
Status:	CLOSED NEXTRELEASE	QA Contact:	Mike Fiedler <mifiedle>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.1.z	CC:	aos-bugs, bandrade, jokerman, lmeyer, mifiedle, mmccomas, smunilla, sponnaga
Target Milestone:	---
Target Release:	4.1.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	4.1.3
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1717627 (view as bug list)		Environment:
Last Closed:	2019-06-13 20:49:16 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:
Bug Depends On:
Bug Blocks:	1718956

Description Jessica Forrester 2019-06-05 20:04:21 UTC

The ClusterServiceVersions for:
Template Service Broker Operator
Ansible Service Broker Operator
Cluster Logging Operator
ElasticSearch Operator

are not being automatically updated in the ART release pipeline with new version numbers, this means we would not be able to upgrade existing installed operators that went out with 4.1.0

Because the automation is not there we are manually updating the 4 operators to have a 4.1.1 version number.

See:
https://github.com/openshift/elasticsearch-operator/pull/151
https://github.com/openshift/template-service-broker-operator/pull/44
https://github.com/openshift/ansible-service-broker/pull/1226
https://github.com/openshift/cluster-logging-operator/pull/196

When these are merged we should be able to update from a 4.1.0 installed operator to the 4.1.1 version of the operator.

Note: this is a one-off fix for 4.1.1, we may have to do the same for 4.1.2 but we will be automating this as soon as possible.

Comment 1 Sudha Ponnaganti 2019-06-06 04:26:03 UTC

Merged

Comment 5 Mike Fiedler 2019-06-07 15:22:12 UTC

verified on 4.1.0-0.ci-2019-06-06-142449.   Following the internal instructions for testing the latest down stream OperatorHub operators:

- clusterlogging, elasticsearch, ASB and TSB operators show 4.1.1 in the catalog
- previously installed 4.1.0 operators upgraded successfully to 4.1.1 according to Automatic or Manual policy

Comment 6 Sudha Ponnaganti 2019-06-12 17:51:15 UTC

Why Need Info ? in the title