Bug 1819828
| Summary: | Build objects migrated and started, causes unexpected mass image updates | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Dylan Murray <dymurray> |
| 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, pvauter, sregidor, tkimura, whu, xjiang |
| Target Milestone: | --- | ||
| Target Release: | 4.3.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1797851 | Environment: | |
| Last Closed: | 2020-04-23 17:32:08 UTC | Type: | --- |
| 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: | 1797851 | ||
| Bug Blocks: | |||
|
Comment 1
Dylan Murray
2020-04-01 16:34:32 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 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 |