Bug 1839692

Summary:	Default hooks runner image is konveyor's instead of CAM's
Product:	OpenShift Container Platform	Reporter:	Sergio <sregidor>
Component:	Migration Tooling	Assignee:	Jason Montleon <jmontleo>
Status:	CLOSED ERRATA	QA Contact:	Xin jiang <xjiang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4	CC:	chezhang, jmontleo, mberube, rjohnson, rpattath, whu, xjiang
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-28 11:10:47 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 Sergio 2020-05-25 09:15:21 UTC

Description of problem:
When we create a new hook, the default hook runner image shown in the UI is the konveyor's one instead of CAM's

Version-Release number of selected component (if applicable):
CAM 1.2 stage

How reproducible:
Always

Steps to Reproduce:
1.Create a migration
2.Add a hook to the migration plan

Actual results:

"Ansible runtime image*" field will show konveyor's hook runner image

quay.io/konveyor/hook-runner:latest


Expected results:
"Ansible runtime image*" field  should show  CAM'S hook runner image
registry.stage.redhat.io/rhcam-1-2/openshift-migration-hook-runner-rhel7:v1.2

Additional info:

Comment 1 Jason Montleon 2020-05-25 15:14:02 UTC

https://github.com/konveyor/mig-operator/pull/354
https://github.com/konveyor/mig-ui/pull/877

Comment 2 whu 2020-05-26 06:54:40 UTC

verified this bug against CAM 1.2.0 stage.

The cam information are 
    - name: REGISTRY
      value: quay-enterprise-quay-enterprise.apps.qe-appmig-tgt-4011.qe.devcluster.openshift.com
    - name: PROJECT
      value: admin
    - name: HOOK_RUNNER_REPO
      value: openshift-migration-hook-runner-rhel7@sha256
    - name: HOOK_RUNNER_TAG
      value: 86a048f0ee9726b4331d10190dc5851330b66c0326d94652ac07f33a501ae323
    - name: MIG_CONTROLLER_REPO
      value: openshift-migration-controller-rhel8@sha256
    - name: MIG_CONTROLLER_TAG
      value: 6f0014650d15dcdd8a15b925e603f4e44c51b2eca420c27c6d09a81b81817209
    - name: MIG_UI_REPO
      value: openshift-migration-ui-rhel8@sha256
    - name: MIG_UI_TAG
      value: 7475399a5d660fdc3fb89c94cc3984b347d6e2ad0c4119836cf2957907be700e
    - name: MIGRATION_REGISTRY_REPO
      value: openshift-migration-registry-rhel8@sha256
    - name: MIGRATION_REGISTRY_TAG
      value: ea6301a15277d448c8756881c7e2e712893ca8041c913476640f52da9e76cad9
    - name: VELERO_REPO
      value: openshift-migration-velero-rhel8@sha256
    - name: VELERO_TAG
      value: 67e34863ff7a671c86d65274a47febe783c76039e0e1526186da0079245021bc
    - name: VELERO_PLUGIN_REPO
      value: openshift-migration-plugin-rhel8@sha256
       ..................


After creating a migration plan, got below image in "Ansible runtime image":
quay-enterprise-quay-enterprise.apps.qe-appmig-tgt-4011.qe.devcluster.openshift.com/admin/openshift-migration-hook-runner-rhel7@sha256:86a048f0ee9726b4331d10190dc5851330b66c0326d94652ac07f33a501ae323

So that seems this bug has been fixed.

Comment 5 Xin jiang 2020-05-27 06:59:54 UTC

verified with CAM 1.2 image.

controller images is  image: quay-enterprise-quay-enterprise.apps.cam-tgt-4090.qe.devcluster.openshift.com/admin/openshift-migration-controller-rhel8@sha256:6f0014650d15dcdd8a15b925e603f4e44c51b2eca420c27c6d09a81b81817209

Comment 7 errata-xmlrpc 2020-05-28 11:10:47 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/RHEA-2020:2326