Bug 1918789 - Wrapped kube errors are causing false negative error checks that prevent requeues and halt migrations
Summary: Wrapped kube errors are causing false negative error checks that prevent requ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: Controller
Version: 1.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 1.4.0
Assignee: Alay Patel
QA Contact: Xin jiang
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-21 14:53 UTC by Erik Nelson
Modified: 2021-02-11 12:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-11 12:55:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github konveyor mig-controller pull 902 0 None closed Bug 1918789: Use Unwrap for api errors that were being checked away from point of creation 2021-02-08 13:51:18 UTC
Red Hat Product Errata RHBA-2020:5329 0 None None None 2021-02-11 12:55:45 UTC

Description Erik Nelson 2021-01-21 14:53:22 UTC 
Description of problem:
In the MTC controller, we wrapped kube errors with our own struct that when passed to api machinery error checking methods, result in false negatives. The impact of this is that problems like API conflicts will not be requeued and retried as expected, causing migrations that should otherwise run to completion to halt.

Version-Release number of selected component (if applicable):
1.4.0
Comment 1 Erik Nelson 2021-01-21 14:54:12 UTC 
https://github.com/konveyor/mig-controller/pull/902
Comment 6 errata-xmlrpc 2021-02-11 12:55:27 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 (Migration Toolkit for Containers (MTC) tool image release advisory 1.4.0), 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/RHBA-2020:5329
Note You need to log in before you can comment on or make changes to this bug.