Bug 1797851

Summary:	Build objects migrated and started, causes unexpected mass image updates
Product:	OpenShift Container Platform	Reporter:	Takayoshi Kimura <tkimura>
Component:	Migration Tooling	Assignee:	Dylan Murray <dymurray>
Status:	CLOSED ERRATA	QA Contact:	Xin jiang <xjiang>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.2.0	CC:	ansverma, chezhang, dymurray, jmatthew, mfuruta, sregidor, whu
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:
Clones:	1819828 (view as bug list)		Environment:
Last Closed:	2020-05-28 11:09:55 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:
Bug Depends On:
Bug Blocks:	1819828

Description Takayoshi Kimura 2020-02-04 03:22:20 UTC

Description of problem:

It seems CAM migrates build objects. The target OpenShift cluster starts to build them, images updated, get unexpected image version deployments, sometimes failed, binary build hangs, etc. In most cases, this is not expected behavior.

We may need:

- to treat build objects differently
- exclude resource functionality and exclude builds by default
- to document this behavior and advice we may need to delete builds before the migration

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

- RHCAM 1.0.1

How reproducible:

Always

Steps to Reproduce:
1.
2.
3.

Actual results:

Builds migrated and started in the target cluster, may lead unexpected results

Expected results:

Several options:

- Builds not migrated
- Builds migrated without stating them
- Document this behavior

Additional info:

Comment 4 Dylan Murray 2020-04-01 13:35:31 UTC

https://github.com/konveyor/openshift-velero-plugin/pull/20/

Comment 8 Sergio 2020-05-07 14:34:25 UTC

Verfied using CAM 1.2 stage

Migrating a namespace with several builds result in only one build being triggered in the target cluster.

Comment 10 errata-xmlrpc 2020-05-28 11:09:55 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