Bug 1819828 - Build objects migrated and started, causes unexpected mass image updates
Summary: Build objects migrated and started, causes unexpected mass image updates
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Migration Tooling
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.3.z
Assignee: Dylan Murray
QA Contact: Xin jiang
URL:
Whiteboard:
Depends On: 1797851
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-01 16:34 UTC by Dylan Murray
Modified: 2020-04-23 17:32 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1797851
Environment:
Last Closed: 2020-04-23 17:32:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:1552 0 None None None 2020-04-23 17:32:18 UTC

Comment 1 Dylan Murray 2020-04-01 16:34:32 UTC 
https://github.com/konveyor/openshift-migration-plugin/pull/57
Comment 3 Sergio 2020-04-08 14:26:01 UTC 
Verfied in CAM 1.1.2 stage
openshift-migration-controller-rhel8@sha256:29eceff4455d8a1db95a625546aa3fbdf503743caf4b71816b36f979a8dd432e

When these builds are in the source cluster and a migration is executed:
$ oc get build
NAME              TYPE     FROM          STATUS     STARTED          DURATION
hotrod-client-2   Source   Git@27dac29   Complete   19 minutes ago   1m32s
hotrod-client-3   Source   Git@27dac29   Complete   12 minutes ago   1m22s
hotrod-client-4   Source   Git@27dac29   Complete   10 minutes ago   1m21s
hotrod-client-5   Source   Git@27dac29   Complete   9 minutes ago    1m27s
hotrod-client-6   Source   Git@27dac29   Complete   7 minutes ago    1m24s


The result in the target cluster is this:
$ oc get build
NAME              TYPE     FROM          STATUS    STARTED              DURATION
hotrod-client-1   Source   Git@27dac29   Running   About a minute ago
Comment 6 errata-xmlrpc 2020-04-23 17:32:08 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:1552
Note You need to log in before you can comment on or make changes to this bug.