Bug 2019467
| Summary: | [RFE] Add an upgrade check for mismatches | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Pavel Moravec <pmoravec> |
| Component: | Satellite Maintain | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.10.0 | CC: | ahumbe, apatel, ehelms, gscarbor, jyejare, kgaikwad, kkinge, mjia, nkim, peter.vreman, rlavi, saydas |
| Target Milestone: | Unspecified | Keywords: | FutureFeature, Reopened, Upgrades |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-12-01 18:26:35 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: | |||
|
Description
Pavel Moravec
2021-11-02 15:43:22 UTC
I actually came across the same issue on my own satellite, where it was due to domain. 2021-11-10 14:21:42 [INFO ] [configure] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: rake aborted! 2021-11-10 14:21:42 [INFO ] [configure] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: ActiveRecord::RecordInvalid: Validation failed: Doma ins expecting domains used by hosts or inherited (check mismatches report). I had example.com as the domain. Two orgs created RedHat and SCA where, the domain was part of first org but was not with second. Now a host was registered with SCA org i.e. host.example.com and if I am not incorrect, that host data was creating the problem in db:seed stage as the domain was not part of SCA org but the host was. I could not figure out how to fix the mismatch as obviously, we don't have GUI working at that point. Only DB and rake console was working at that point and I could not found how to trigger the "Fix Mismatches" for an organization via rake. So, I went ahead and deleted that host from Satellite DB via rake console and then db:seed completed without any errors. Obviously, we need to fix this within the installer but I like the idea of having a prerequisite mentioned in Sat 6.10 upgrade doc i.e. Check and click on "Fix Mismatches" for every single Organization and Location someone has in their satellite. If everyone agrees, I can go for a DOC RFE here. (In reply to Sayan Das from comment #2) > I actually came across the same issue on my own satellite, where it was due > to domain. > > 2021-11-10 14:21:42 [INFO ] [configure] > /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db: > seed]/returns: rake aborted! > 2021-11-10 14:21:42 [INFO ] [configure] > /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db: > seed]/returns: ActiveRecord::RecordInvalid: Validation failed: Doma > ins expecting domains used by hosts or inherited (check mismatches report). > > > I had example.com as the domain. Two orgs created RedHat and SCA where, the > domain was part of first org but was not with second. > > Now a host was registered with SCA org i.e. host.example.com and if I am not > incorrect, that host data was creating the problem in db:seed stage as the > domain was not part of SCA org but the host was. > > > I could not figure out how to fix the mismatch as obviously, we don't have > GUI working at that point. Only DB and rake console was working at that > point and I could not found how to trigger the "Fix Mismatches" for an > organization via rake. > > So, I went ahead and deleted that host from Satellite DB via rake console > and then db:seed completed without any errors. > > Obviously, we need to fix this within the installer but I like the idea of > having a prerequisite mentioned in Sat 6.10 upgrade doc i.e. Check and click > on "Fix Mismatches" for every single Organization and Location someone has > in their satellite. > > If everyone agrees, I can go for a DOC RFE here. And yes, It could be great is some sort of rake method is available to trigger "Fix Mismatches" for Org or Locations from rake console. That could very much help in cases where upgrade is stuck in midway and we have no way to access UI to do the Fix Mismatches. Please be aware of following BZ and PR as well. 2028205 – db:seed can fail when there are host mismatches https://bugzilla.redhat.com/show_bug.cgi?id=2028205 Fixes #34059 - disable validation when seeding existing org by jturel · Pull Request #9822 · Katello/katello https://github.com/Katello/katello/pull/9822/files *** This bug has been marked as a duplicate of bug 2028205 *** Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you. Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you. |