Bug 1751260 - OLM release-1.0 installation deploys stable version instead of release 1.0 version
Summary: OLM release-1.0 installation deploys stable version instead of release 1.0 ve...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Migration Tooling
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.2.0
Assignee: John Matthews
QA Contact: Sergio
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-11 14:19 UTC by Sergio
Modified: 2019-10-16 06:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:40:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:41:02 UTC

Description Sergio 2019-09-11 14:19:51 UTC
Description of problem:
OLM App Migration Tool installation of branch release-1.0 does not install release-1.0 version of the images, but stable version.


Version-Release number of selected component (if applicable):
mig-operator commit ID:
commit a0ed9d5521ba91ba81f6520a01ea426716ec42d7
Merge: 3eb4ff0 1fc26c0

    Merge pull request #87 from eriknelson/pin-img-tags
    
    Pin image tags to release-1.0

OCP4:
$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.2.0-0.nightly-2019-09-11-032939   True        False         5h14m   Cluster version is 4.2.0-0.nightly-2019-09-11-032939


How reproducible:
Always

Steps to Reproduce:
1. git clone https://github.com/fusor/mig-operator.git
2. git checkout -b release-1.0 origin/release-1.0
3. cd mig-operator
4. oc create -f mig-operator-source.yaml
5. oc create namespace openshift-migration

6. Access the web console of OCP 4, install Migration Operator from MarketPlace
Choose project openshift-migration
Choose Operators->OperatorHub
Click 'Migration Operator' -> Install->Subscirbe

7. Create MigrationController
From 'Installed Operators' -> 'Migration Operator'

create instance for 'MigrationController'
using default vaule:

apiVersion: migration.openshift.io/v1alpha1
kind: MigrationController
metadata:
  name: migration-controller
  namespace: mig
spec:
  cluster_name: host
  migration_velero: true
  migration_controller: true
  migration_ui: true



Actual results:

After installing the operator and the controller the images deployed are deployed with tag version "stable"
$ oc get pods -o yaml -n openshift-migration | grep image
      image: quay.io/ocpmigrate/mig-controller:stable
      imagePullPolicy: Always
    imagePullSecrets:
      image: quay.io/ocpmigrate/mig-controller:stable
      imageID: quay.io/ocpmigrate/mig-controller@sha256:7ec48a557240f1d2fa6ee6cd62234b0e75f178eca2a0cc5b95124e01bcd2c114
      image: quay.io/ocpmigrate/mig-operator:stable
      imagePullPolicy: Always
      image: quay.io/ocpmigrate/mig-operator:stable
      imagePullPolicy: Always
    imagePullSecrets:
      image: quay.io/ocpmigrate/mig-operator:stable
      imageID: quay.io/ocpmigrate/mig-operator@sha256:067bf5324405c516500d26a05c6c1e7575a98994167cc8a1591b41986975a4ee
      image: quay.io/ocpmigrate/mig-operator:stable
      imageID: quay.io/ocpmigrate/mig-operator@sha256:067bf5324405c516500d26a05c6c1e7575a98994167cc8a1591b41986975a4ee
    - image: quay.io/ocpmigrate/mig-ui:stable
      imagePullPolicy: Always
    imagePullSecrets:
      image: quay.io/ocpmigrate/mig-ui:stable
      imageID: quay.io/ocpmigrate/mig-ui@sha256:bffe00e5c6a812a14018c0d0916e626e00342b5254546de47d0ce5d6052776d8
      image: quay.io/ocpmigrate/velero:stable
      imagePullPolicy: Always
    imagePullSecrets:
      image: quay.io/ocpmigrate/velero:stable
      imageID: quay.io/ocpmigrate/velero@sha256:957725dec5f0fb6a46dee78bd49de9ec4ab66903eabb4561b62ad8f4ad9e6f05
      image: quay.io/ocpmigrate/velero:stable
      imagePullPolicy: Always
    imagePullSecrets:
      image: quay.io/ocpmigrate/velero:stable
      imageID: quay.io/ocpmigrate/velero@sha256:957725dec5f0fb6a46dee78bd49de9ec4ab66903eabb4561b62ad8f4ad9e6f05
      image: quay.io/ocpmigrate/velero:stable
      imagePullPolicy: Always
    imagePullSecrets:
    - image: quay.io/ocpmigrate/migration-plugin:stable
      imagePullPolicy: Always
      image: quay.io/ocpmigrate/velero:stable
      imageID: quay.io/ocpmigrate/velero@sha256:957725dec5f0fb6a46dee78bd49de9ec4ab66903eabb4561b62ad8f4ad9e6f05
      image: quay.io/ocpmigrate/migration-plugin:stable
      imageID: quay.io/ocpmigrate/migration-plugin@sha256:b4493d826260eb1e3e02ba935aaedfd5310fefefb461ca7dcd9a5d55d4aa8f35


Expected results:

The version of the deployed images should be release-1.0

Additional info:

Comment 1 errata-xmlrpc 2019-10-16 06:40:54 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/RHBA-2019:2922


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