Bug 2030619

Description of problem (please be detailed as possible and provide log
snippests):

I created CR using this
```
apiVersion: updateservice.operator.openshift.io/v1
kind: UpdateService
metadata:
  name: kka
  namespace: openshift-update-service
spec:
  replicas: 1
  releases: "konstantinos-kvm.cloud.lab.eng.bos.redhat.com:5000/ocp4/release"
  graphDataImage: "konstantinos-kvm.cloud.lab.eng.bos.redhat.com:5000/cincinnati/graph-data:v1"

```
and then i create v2 with a newer release and apply the change

```
apiVersion: updateservice.operator.openshift.io/v1
kind: UpdateService
metadata:
  name: kka
  namespace: openshift-update-service
spec:
  replicas: 1
  releases: "konstantinos-kvm.cloud.lab.eng.bos.redhat.com:5000/ocp4/release"
  graphDataImage: "konstantinos-kvm.cloud.lab.eng.bos.redhat.com:5000/cincinnati/graph-data:v2"

```

I do not see the pod does get recreated, and if i delete it manually then it come up with the old graph data.

I can only update by deleting the UpdateService and recreating it.



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

Low impact, user experience can be improved.


Is there any workaround available to the best of your knowledge?
yes, delete and create the instance


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?
yes


Can this issue reproduce from the UI?
I use the CLI but probably yes


If this is a regression, please provide more details to justify this:
First time I use it.

Steps to Reproduce:
1. Create an UpdateService with tag v1 in graphDataImage
2. Update content of graphDataImage and tag it v2
3. Update the UpdatService with tag v2
4. See that no update is available


Actual results:
See no update available

Expected results:
See the actual new content.


Additional info: