Bug 1966149 - The osd removal job name on OCS4.7 and OCS4.8 is different
Summary: The osd removal job name on OCS4.7 and OCS4.8 is different
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: ocs-operator
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: OCS 4.8.0
Assignee: Prajith
QA Contact: Oded
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-31 14:15 UTC by Oded
Modified: 2021-08-03 18:17 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-03 18:16:39 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift ocs-operator pull 1198 0 None open Re-Change job template name to its original one, 2021-06-03 12:44:38 UTC
Github openshift ocs-operator pull 1206 0 None open Bug 1966149: [release-4.8] Re-Change the job template name back to its original one 2021-06-04 07:24:36 UTC
Red Hat Product Errata RHBA-2021:3003 0 None None None 2021-08-03 18:17:03 UTC

Description Oded 2021-05-31 14:15:58 UTC
Description of problem (please be detailed as possible and provide log
snippests):
The osd removal job name on OCS4.7 and OCS4.8 are different 

The osd removal job name on OCS4.7 is "ocs-osd-removal-job"
The osd removal job name on OCS4.8 is "ocs-osd-removal"


Version of all relevant components (if applicable):
OCS4.8

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


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


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

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:
The osd removal job name on OCS4.7 and OCS4.8 is different

Expected results:
The osd removal job name on OCS4.7 and OCS4.8 is same


Additional info:
**If the job name is "ocs-osd-removal", all relevant documents must be updated in OCS4.8

Comment 2 Prajith 2021-06-01 18:27:07 UTC
Shouldn't this be targeted to OCS 4.8? Since the PR which I'm about to raise will use the previous name of (OCS 4.7) itself?

Comment 3 Prajith 2021-06-01 19:46:56 UTC
Submitted a PR for this :- https://github.com/openshift/ocs-operator/pull/1198

Comment 4 Servesha 2021-06-02 07:54:08 UTC
Clearing the needinfo since the bug has been updated.

Comment 7 Prajith 2021-06-04 05:55:44 UTC
The PR has been merged to ocs-operator

Comment 8 Mudit Agarwal 2021-06-04 06:00:34 UTC
As far as I can see, PR is merged only in master, we need to backport this to release-4.8

Comment 9 Prajith 2021-06-04 15:46:56 UTC
Right sorry about that, its merged now to release-4.8

Comment 12 Oded 2021-06-10 12:55:24 UTC
The osd removal job name on OCS4.7 and OCS4.8 is same [ocs-osd-removal-job]

SetUp:
OCP Version:4.8.0-0.nightly-2021-06-09-065137
OCS Version: ocs-operator.v4.8.0-413.ci
LSO version:4.7.0-202102110027.p0
Provider: Vmware


oc process -n openshift-storage ocs-osd-removal -p FAILED_OSD_IDS=0 |oc create -n openshift-storage -f -
$ oc get pod -l job-name=ocs-osd-removal-job -n openshift-storage
NAME                        READY   STATUS      RESTARTS   AGE
ocs-osd-removal-job-zh2nx   0/1     Completed   0          12s

$ oc get job
NAME                                                           COMPLETIONS   DURATION   AGE
ocs-osd-removal-job                                            1/1           8s         39s

$ oc delete -n openshift-storage job ocs-osd-removal-job
job.batch "ocs-osd-removal-job" deleted

Comment 14 errata-xmlrpc 2021-08-03 18:16:39 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 Container Storage 4.8.0 container images bug fix and enhancement 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-2021:3003


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