You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge pull request #17080 from enj/enj/i/migrate_not_found_doraw_/1506006
Automatic merge from submit-queue.
Correctly handle NotFound errors during migration
This change makes it so that the migrate storage command will now reprocess the body of a failed GET request to follow the standard path of extracting a status error. This normalizes the structure of the errors the code must handle.
When comparing the resource.Info to an error, the info's REST mapping is now used to extract group kind information since the associated runtime.Object is not guaranteed to have valid type meta data. This is combined with relaxed case-insensitive matching to make sure that we only fail the migrate storage command on NotFound errors that we know do not match the info.
When a NotFound error occurs, the migrate command now correctly reports that it did not change the resource. Previously it reported that it had successfully migrated the resource, which is not true since it is impossible to migrate a resource that does not exist.
Bug 1506006
Signed-off-by: Monis Khan <[email protected]>
---
Add timestamps to migration command's reporting
This change adds glog style timestamps to the reporting output of the migration tracker. This will aid in debugging migration errors by making it easier to correlate client errors with master logs.
Signed-off-by: Monis Khan <[email protected]>
---
/assign @smarterclayton
/kind bug
xref https://bugzilla.redhat.com/show_bug.cgi?id=1506006@sdodson@jupierce
0 commit comments