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:
https://github.com/konveyor/openshift-velero-plugin/pull/20/
Verfied using CAM 1.2 stage Migrating a namespace with several builds result in only one build being triggered in the target cluster.
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