Bug 1899407 - satellite-installer --list-scenarios failed with NamedError
Summary: satellite-installer --list-scenarios failed with NamedError
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.9.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: 6.9.0
Assignee: Eric Helms
QA Contact: Devendra Singh
URL:
Whiteboard:
: 1903584 (view as bug list)
Depends On:
Blocks: 1903599
TreeView+ depends on / blocked
 
Reported: 2020-11-19 06:19 UTC by Devendra Singh
Modified: 2021-04-21 13:18 UTC (History)
2 users (show)

Fixed In Version: kafo-6.1.2,tfm-rubygem-kafo-6.1.2-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 13:18:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31466 0 Normal Closed satellite-installer --list-scenarios failed with NamedError 2021-02-08 15:13:51 UTC

Description Devendra Singh 2020-11-19 06:19:49 UTC
Description of problem: satellite-installer --list-scenarios failed with NamedError

Version-Release number of selected component (if applicable):
6.9 Snap2

How reproducible:
always

Steps to Reproduce:
1. Prepare the 6.8 Satellite and Capsule.
2. Upgrade Satellite from 6.8 to 6.9
3. Satellite upgrade completed successfully.
4. Run satellite-installer with list-scenarios options, but it failed with NameError.

#satellite-installer --list-scenarios
Traceback (most recent call last):
	7: from /usr/sbin/satellite-installer:8:in `<main>'
	6: from /opt/theforeman/tfm/root/usr/share/gems/gems/kafo-6.1.0/lib/kafo/kafo_configure.rb:50:in `run'
	5: from /opt/theforeman/tfm/root/usr/share/gems/gems/clamp-1.1.2/lib/clamp/command.rb:132:in `run'
	4: from /opt/theforeman/tfm/root/usr/share/gems/gems/clamp-1.1.2/lib/clamp/command.rb:132:in `new'
	3: from /opt/theforeman/tfm/root/usr/share/gems/gems/kafo-6.1.0/lib/kafo/kafo_configure.rb:108:in `initialize'
	2: from /opt/theforeman/tfm/root/usr/share/gems/gems/kafo-6.1.0/lib/kafo/scenario_manager.rb:34:in `list_available_scenarios'
	1: from /opt/theforeman/tfm/root/usr/share/gems/gems/highline-1.7.8/lib/highline.rb:383:in `color'
/opt/theforeman/tfm/root/usr/share/gems/gems/highline-1.7.8/lib/highline/style.rb:33:in `Style': :notice is not a defined Style (NameError)


Actual results:
After Upgrade, satellite-installer --list-scenarios command failed with NamedError

Expected results:
satellite-installer --list-scenarios command should be completed successfully.

Additional info:

Comment 2 Eric Helms 2020-12-07 19:09:35 UTC
Created redmine issue https://projects.theforeman.org/issues/31466 from this bug

Comment 3 Bryan Kearney 2020-12-07 20:00:57 UTC
Upstream bug assigned to ehelms

Comment 4 Bryan Kearney 2020-12-07 20:00:59 UTC
Upstream bug assigned to ehelms

Comment 5 Bryan Kearney 2020-12-09 16:01:06 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31466 has been resolved.

Comment 6 Eric Helms 2020-12-14 15:23:31 UTC
*** Bug 1903584 has been marked as a duplicate of this bug. ***

Comment 8 Devendra Singh 2020-12-18 11:49:59 UTC
Verified on 6.9 Snap 6

Verification points:

1: satellite-installer list down all the available scenarios.

# satellite-installer --list-scenarios
Available scenarios
  Capsule (use: --scenario capsule)
        Install a stand-alone Satellite Capsule.
  Satellite (INSTALLED)
        Install Satellite server
2: #rpm -qa|grep -e kafo-6.1.2 
tfm-rubygem-kafo-6.1.2-1.el7sat.noarch

Comment 11 errata-xmlrpc 2021-04-21 13:18:56 UTC
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 (Moderate: Satellite 6.9 Release), 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-2021:1313


Note You need to log in before you can comment on or make changes to this bug.