Bug 1526863
Summary: | Broken content view blocks the 6.2->6.3 upgrade and leaves the system in a broken state | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Alexey Masolov <amasolov> |
Component: | Content Management | Assignee: | Justin Sherrill <jsherril> |
Status: | CLOSED ERRATA | QA Contact: | Stephen Wadeley <swadeley> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3.0 | CC: | amasolov, apatel, bbuckingham, cdonnell, dmoessne, egolov, inecas, jsenkyri, jsherril, kgaikwad, mmccune, nkathole, pdudley, smane, sthirugn, swadeley, the.benparry |
Target Milestone: | 6.4.0 | Keywords: | PrioBumpGSS, Triaged, Upgrades |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | tfm-rubygem-katello-3.7.0.28-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-16 19:13:23 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: | 1496794 |
Description
Alexey Masolov
2017-12-18 03:34:09 UTC
Is this not a bug in the installer, not foreman-maintain? I think this one is related to the both components actually I don't think there is anything right now in foreman-maintain to update to address this issue: this looks like an issue in migration code of the Katello, moving the component to contnet-management, with keyword set to Upgrades I think the orphaned records should not exist in the first place. To me, this seems to be an issue with content-views, as the error was raised while running migrations. While calling content_facet.update_applicability_counts from migration AddErrataCounts. I am more reluctant to set the component to content-views and create a separate RFE in foreman-maintain to fix/remove orphaned content-views. Removing target milestone - as per the comments, this needs to be handled outside of the foreman-maintain In my opinion foreman-maintain should be able to check for the orphaned records and not going further with upgrading. We have exactly the same error during our Satellite 6.2 -> 6.3 upgrade. Looking through your output I am unable to determine how you able to spot which version of the view is causing the issue? We had to roll back to 6.2.15 which was a real pain. We know which view/environment are causing the issue but I don't know how to identify it in the database to make sure the problem is gone before we try again. The best course of actions would be removing the content view/all old versions probably. Connecting redmine issue https://projects.theforeman.org/issues/24768 from this bug 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-2018:2927 |