Bug 2173528

Summary:	Creation of OCS operator tag automatically for verified commits
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Gayathri Menath <gmenath>
Component:	build	Assignee:	Deepshikha khandelwal <dkhandel>
Status:	CLOSED ERRATA	QA Contact:	Petr Balogh <pbalogh>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.12	CC:	branto, dkhandel, mmuench, muagarwa, ocs-bugs, odf-bz-bot, tmuthami, uchapaga
Target Milestone:	---
Target Release:	ODF 4.13.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-06-21 15:24:01 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 Gayathri Menath 2023-02-27 08:23:25 UTC

Description of problem (please be detailed as possible and provide log
snippests):
As a part of supporting ODF on ibmcloud, our dev repo which is using RedHat ocs operator - https://github.com/red-hat-storage/ocs-operator
We were using specific commits and we got into trouble using the commits for each release. So we request to create tag for each version. This will take time and we may need to contact the team for each release/update. After discussing with the RH dev team, they agreed to create an automated way to create tags. This ticket is to track the issue

Version of all relevant components (if applicable):

All ODF version

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
We may miss the updates/fixes as for tag creation we have to contact the team each time. 


Is there any workaround available to the best of your knowledge?

Manual tag creation is doing now, not practically possible.


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:

Comment 3 Gayathri Menath 2023-03-23 03:59:46 UTC

Could you share is there any update?

Comment 4 Gayathri Menath 2023-03-29 04:56:37 UTC

I am raising the severity as we have to depend on the ocs-operator tags to fix any CVE and following up for each version of ocs-operator for each changes is difficult. It is affecting our delivery. Please cgeck this with priority

Comment 7 Deepshikha khandelwal 2023-03-30 06:47:32 UTC

We have a Jenkins job in a place that will push the tags for all the major releases to ocs-operator repo.

Comment 8 Boris Ranto 2023-03-30 07:45:12 UTC

This was already implemented, moving to MODIFIED.

Comment 15 errata-xmlrpc 2023-06-21 15:24:01 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 (Red Hat OpenShift Data Foundation 4.13.0 enhancement and bug fix update), 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-2023:3742