Bug 1645737
Summary: | Capsule upgrade to 6.5 failed with undefined method `enabled?' for nil:NilClass | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Nikhil Kathole <nkathole> |
Component: | Installation | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED ERRATA | QA Contact: | Nikhil Kathole <nkathole> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.5.0 | CC: | egolov, ekohlvan, inecas, mbacovsk |
Target Milestone: | 6.5.0 | Keywords: | Regression, Triaged, Upgrades |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | katello-installer-base-3.9.0-0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-14 12:38:32 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
2018-11-03 07:38:50 UTC
This happens when the foreman module is not enabled. https://projects.theforeman.org/issues/25058 makes the function more robust but is unreleased. Ewoud, am I right that Foreman #25058 should fix this? Upstream bug assigned to ekohlvan Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25058 has been resolved. VERIFIED Version tested: Satellite 6.5 snap 6 satellite-capsule-6.5.0-5.beta.el7sat.noarch Datacat_fragment[foreman_proxy::enabled_features:: [99%]Installing Service[smart_proxy_dynflow_core] [99%]Installing Done [100%]Installing Done [100%] The full log is at /var/log/foreman-installer/capsule.log Upgrade completed! 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 |