Bug 1756408
| Summary: | Warnings disappear while the migration is being executed | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Sergio <sregidor> |
| Component: | Migration Tooling | Assignee: | Scott Seago <sseago> |
| Status: | CLOSED ERRATA | QA Contact: | Sergio <sregidor> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 4.2.0 | CC: | chezhang, dymurray, jortel, rpattath, xjiang |
| Target Milestone: | --- | ||
| Target Release: | 4.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-02-06 20:20:44 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: | |||
Related to this PR: https://github.com/fusor/mig-controller/pull/331 Aligning to 4.3.0 Validated in CAM 1.1 from osbs
Controller:
image: image-registry.openshift-image-registry.svc:5000/rhcam-1-1/openshift-migration-controller-rhel8@sha256:b55c0c36333656a46e1d0500cf11cc8aa06e093d312e7c54f8e1075d4ab4c6c1
Forced a warning:
status:
conditions:
- category: Required
lastTransitionTime: "2020-01-15T11:56:42Z"
message: The `persistentVolumes` list has been updated with discovered PVs.
reason: Done
status: "True"
type: PvsDiscovered
- category: Warn
lastTransitionTime: "2020-01-15T11:56:42Z"
message: AccessMode for PVC in `persistentVolumes` [pvc-e7e28aef-378d-11ea-a2e0-42010a800017]
unavailable in chosen storage class
status: "True"
type: PvWarnAccessModeUnavailable
- category: Required
lastTransitionTime: "2020-01-15T11:56:42Z"
message: The storage resources have been created.
status: "True"
type: StorageEnsured
- category: Required
lastTransitionTime: "2020-01-15T11:56:43Z"
message: The migration registry resources have been created.
status: "True"
type: RegistriesEnsured
- category: Required
lastTransitionTime: "2020-01-15T11:56:43Z"
message: The migration plan is ready.
status: "True"
type: Ready
And while the plan is being executed (the suspend type status is true) the warning is still there:
status:
conditions:
- category: Required
lastTransitionTime: "2020-01-15T11:56:42Z"
message: The `persistentVolumes` list has been updated with discovered PVs.
reason: Done
status: "True"
type: PvsDiscovered
- category: Warn
lastTransitionTime: "2020-01-15T11:56:42Z"
message: AccessMode for PVC in `persistentVolumes` [pvc-e7e28aef-378d-11ea-a2e0-42010a800017]
unavailable in chosen storage class
status: "True"
type: PvWarnAccessModeUnavailable
- category: Required
lastTransitionTime: "2020-01-15T11:56:42Z"
message: The storage resources have been created.
status: "True"
type: StorageEnsured
- category: Required
lastTransitionTime: "2020-01-15T11:56:43Z"
message: The migration registry resources have been created.
status: "True"
type: RegistriesEnsured
- category: Required
lastTransitionTime: "2020-01-15T11:56:43Z"
message: The migration plan is ready.
status: "True"
type: Ready
- category: Advisory
lastTransitionTime: "2020-01-15T11:57:31Z"
message: Limited validation; PV discovery and resource reconciliation suspended.
status: "True"
type: Suspended
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:0440 |
Description of problem: While a migration is running, if there are warnings in it migration plan, warnings disappear from MigPlan resource and they are shown again once the migration has finished. Version-Release number of selected component (if applicable): OCP3: oc v3.10.174 kubernetes v1.10.0+b81c8f8 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https:// openshift v3.10.170 kubernetes v1.10.0+b81c8f8 OCP4: NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.0-0.nightly-2019-09-25-233506 True False 29h Cluster version is 4.2.0-0.nightly-2019-09-25-233506 Controller: image: quay.io/ocpmigrate/mig-controller:release-1.0 imageID: quay.io/ocpmigrate/mig-controller@sha256:45d82e1cf33a6f633bbdbaefd778de18414864187ff66cb1d33eb6423bfdce94 Velero: image: quay.io/ocpmigrate/velero:fusor-1.1 imageID: quay.io/ocpmigrate/velero@sha256:6c16a1288bf6aca74afbb0184fa987506839c5193ae8bb2be05cb6aa0a9f3dc5 image: quay.io/ocpmigrate/migration-plugin:release-1.0 imageID: quay.io/ocpmigrate/migration-plugin@sha256:f917ce774c08b3ea4e4d5c422521230d8fb8e03bc13ac0b9a323cbd4599cd341 How reproducible: Always Steps to Reproduce: 1. Prepare a source OCP3 cluster with glusterfs storage. 2. Prepare a target OCP4 cluster WITHOUT ceph storage. 2. Create in OCP3 source cluster any application with a volume. For instance: oc process -p LOGS_ACCESSMODE=ReadWriteOnce -p LOGS_STORAGECLASS=glusterfs-storage-block -p HTML_ACCESSMODE=ReadWriteMany -p HTML_STORAGECLASS=glusterfs-storage -f https://raw.githubusercontent.com/sergiordlr/temp-testfiles/master/app_migration/nginx_pvs/nginx_with_pv_template.yml | oc create -f - 3. Create a migration plan to migrate this application to the target OCP4 cluster without ceph in it. 4. This warning will appear in the migration plan oc get MigPlan -o yaml -n openshift-migration .... - category: Warn lastTransitionTime: "2019-09-27T10:34:11Z" message: 'Ceph is not available on destination. If this is desired, please install the rook operator. The following PVs will use the default storage class instead: [pvc-0ebcf335-e110-11e9-89a6-0e1f72a11f2c,pvc-130dc630-e110-11e9-89a6-0e1f72a11f2c]' 5. Execute the migration. 6. While the migration is being executed, the warnings disappear: oc get MigPlan -o yaml -n openshift-migration 7. Once the migration ends, the warnings are shown again Actual results: Warnings are not displayed in the MigPlan resource while the execution is running. Expected results: Warnings should be displayed while the migration is running. Additional info: