Bug 1738564
Summary: | MigStorage object not updated when AWS bucket is deleted from AWS | |||
---|---|---|---|---|
Product: | Migration Toolkit for Containers | Reporter: | Sergio <sregidor> | |
Component: | General | Assignee: | John Matthews <jmatthew> | |
Status: | CLOSED WORKSFORME | QA Contact: | Xin jiang <xjiang> | |
Severity: | low | Docs Contact: | Avital Pinnick <apinnick> | |
Priority: | low | |||
Version: | 1.3.0 | CC: | chezhang, erich, ernelson, jmatthew, jortel, rpattath | |
Target Milestone: | --- | |||
Target Release: | 1.4.4 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1760994 (view as bug list) | Environment: | ||
Last Closed: | 2021-05-11 15:34:45 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: | 1760994 |
Description
Sergio
2019-08-07 13:17:41 UTC
For 4.2 we do not intend to perform a check on external resources after we've established a ready condition, unless the details of the CR has changed. i.e., if the CR is updated, we'll re-verify. We will consider this for 4.3 release to add a periodic check on external resources. Tracked in github issue: https://github.com/fusor/mig-controller/issues/292 Should we create a docs bug for documenting this as a known issue as part of 4.2? Will add to 4.2 docs as a known issue: https://bugzilla.redhat.com/show_bug.cgi?id=1760994 Sergio, could you confirm that this remains a BZ as of MTC 1.4.2? In 1.4.4 it is not happening any more. After deleting the bucket in AWS the migstorage is updated properly. I think that we can close this issue. (In reply to Sergio from comment #5) > In 1.4.4 it is not happening any more. After deleting the bucket in AWS the > migstorage is updated properly. > > I think that we can close this issue. The bug is included in current docs, Known Issues. I will create a PR to remove it. |