Bug 1727417 - Capsule upgrade gets failed with Unrecognised option '--certs-tar'
Summary: Capsule upgrade gets failed with Unrecognised option '--certs-tar'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.6.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: 6.6.0
Assignee: Evgeni Golov
QA Contact: Devendra Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-06 02:09 UTC by Devendra Singh
Modified: 2019-10-22 19:48 UTC (History)
5 users (show)

Fixed In Version: satellite-installer-6.6.0.18-1.beta
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:48:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Devendra Singh 2019-07-06 02:09:20 UTC
Description of problem:
Capsule upgrade gets failed with Unrecognised option '--certs-tar'

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

How reproducible:
Always

Steps to Reproduce:
1. Satellite Upgraded successfully from 6.5.1 to 6.6.0 snap10
2. Capsule upgrade gets failed with Unrecognised option '--certs-tar' option.

Actual results:
Get below error 
run: satellite-installer --scenario capsule --upgrade --certs-tar /home/qe-capsule.redhat.com-certs.tar --certs-update-all --regenerate true --deploy true
out: ERROR: Unrecognised option '--certs-tar'

Expected results:
Capsule upgrade should be completed successfully.

Additional info:

Comment 12 Devendra Singh 2019-07-16 13:00:37 UTC
Hi Evgeni,

As I observed two other optional parameters get removed from Capsule upgrade i.e mentioned below.

* regenerate
* deploy

Please confirm, If it is correct?

Comment 13 Evgeni Golov 2019-07-16 13:19:15 UTC
They aren't removed, they are called --certs-regenerate and --certs-deploy (and always were, just not with no_prefix:true as in your install)

Comment 14 Devendra Singh 2019-07-17 08:35:52 UTC
Verified in 6.6.0 beta(snap11).

Verified no_prefix status in capsule.yaml file.

# cat /etc/foreman-installer/scenarios.d/capsule.yaml 
---
:name: Capsule
:description: Install a stand-alone Satellite Capsule.
:enabled: true
:log_dir: /var/log/foreman-installer
:store_dir: ''
:log_name: capsule.log
:log_level: DEBUG
:no_prefix: false


Verified RPM details.
# rpm -q satellite-installer-6.6.0.18-1.beta.el7sat
satellite-installer-6.6.0.18-1.beta.el7sat.noarch

Comment 15 Bryan Kearney 2019-10-22 19:48:26 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, 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:3172


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