Bug 1680441
| Summary: | customer db upgrade from 6.4 to 6.5 failed at upgrade task: katello:upgrades:3.11:update_puppet_repos | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Nikhil Kathole <nkathole> |
| Component: | Repositories | Assignee: | Justin Sherrill <jsherril> |
| Status: | CLOSED ERRATA | QA Contact: | Nikhil Kathole <nkathole> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.5.0 | CC: | egolov, jsherril, mmccune, pcreech |
| Target Milestone: | 6.5.0 | Keywords: | Regression, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | tfm-rubygem-katello-3.10.0.22-1,tfm-rubygem-katello-3.10.0.23-1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-14 12:40:17 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: | 1653153 | ||
|
Description
Nikhil Kathole
2019-02-25 02:17:55 UTC
That's interesting, the traceback has RestClient::NotFound, but our rake task only has rescue RestClient::ResourceNotFound in it. Justin, you had added this rescue in the first place, mind having a look? seems those two should be aliases: https://github.com/rest-client/rest-client/blob/master/spec/unit/exceptions_spec.rb#L84-L86 yep!
> RestClient::ResourceNotFound == RestClient::NotFound
true
I think the problem is that this traceback is happening within the foreman-task, so foreman-task is throwing a NotFound, but its likely wrapped in its own exception.
The strange thing here is that fetching the repository did NOT throw a NotFound, which means the repository exists, but the distributor its trying to update doesn't? This are of code was changed recently so maybe there is some regression here (although i didn't think it would have been between these snaps).
Thinking about this a bit more, i highly suspect this is the cause: https://projects.theforeman.org/issues/26005 and the fix has been merged upstream: https://github.com/Katello/katello/pull/7968 The root cause would have been introduced by https://github.com/Katello/katello/pull/7762, but probably wasn't involved in the upgrade process until https://bugzilla.redhat.com/show_bug.cgi?id=1665657 went in in snap 12. However it is a timing issue, a very fast satellite may never see the issue, but a slower one probably would. Is there a workaround if the upgrade fails? Can you just re-run it and likely get past it the 2nd time? There really isn't a workaround, re-runs will likely hit the same issue again on slower hardware. Connecting redmine issue https://projects.theforeman.org/issues/26005 from this bug VERIFIED Version tested: Satellite 6.5 snap 17.1 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/RHSA-2019:1222 |