Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1458639 - Upgrade [6.2 -> 6.3]: Installer failed: Parameter foreman-websockets-ssl-key invalid:
Summary: Upgrade [6.2 -> 6.3]: Installer failed: Parameter foreman-websockets-ssl-key ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Sachin Ghai
URL:
Whiteboard:
Depends On:
Blocks: Sat_6.3_Upgrade_tracker
TreeView+ depends on / blocked
 
Reported: 2017-06-05 05:22 UTC by Sachin Ghai
Modified: 2019-04-01 20:26 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
foreman-debug (7.06 MB, application/x-xz)
2017-06-06 02:27 UTC, Sachin Ghai 		no flags Details
View All

Description Sachin Ghai 2017-06-05 05:22:03 UTC 
Description of problem:
Upgraded 6.2.9 -> sat6.3.0 beta snap1. After package updates, satellite-installer failed w/ below error:

[SERVER] run: satellite-installer --scenario satellite --upgrade
[SERVER] out: Parameter foreman-websockets-ssl-key invalid:  is not one of regexes matchiParameter foreman-websockets-ssl-cert invalid:  is not one of regexes matchError during configuration, exiting


Version-Release number of selected component (if applicable):
sat6.2.9 -> sat6.3.0 snap1

How reproducible:


Steps to Reproduce:
1. yum update -y
2. satellite-installer --scenario satellite --upgrade
3.

Actual results:
Installer failed

Expected results: upgrade should be successful.


Additional info:
Comment 2 Sachin Ghai 2017-06-05 05:29:32 UTC 
[ INFO 2017-06-05 01:26:33 verbose] Running validation checks
[ERROR 2017-06-05 01:26:33 verbose] Parameter foreman-websockets-ssl-key invalid:  is not one of regexes matching /^(([a-zA-Z]:[\\\/])|([\\\/][\\\/][^\\\/]+[\\\/][^\\\/]+)|([\\\/][\\\/]\?[\\\/][^\\\/]+))/ or regexes matching /^\/([^\/\0]+\/*)+$/
[ERROR 2017-06-05 01:26:33 verbose] Parameter foreman-websockets-ssl-cert invalid:  is not one of regexes matching /^(([a-zA-Z]:[\\\/])|([\\\/][\\\/][^\\\/]+[\\\/][^\\\/]+)|([\\\/][\\\/]\?[\\\/][^\\\/]+))/ or regexes matching /^\/([^\/\0]+\/*)+$/
Error during configuration, exiting
Comment 4 Sachin Ghai 2017-06-06 02:27:59 UTC 
Created attachment 1285186 [details]
foreman-debug
Comment 5 Sachin Ghai 2017-06-06 02:36:29 UTC 
As per comment3, here is what I see in satellite-answer file

-bash-4.2# cat /etc/foreman-installer/scenarios.d/satellite-answers.yaml | grep websocket
  websockets_encrypt: false
  websockets_ssl_key: ''
  websockets_ssl_cert: ''
Comment 6 Sachin Ghai 2017-09-27 09:20:30 UTC 
Verified w/ sat6.2.11 -> sat6.3 snap16, the reported issue is no longer reproducible.
Comment 8 Satellite Program 2018-02-21 16:54:37 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-2018:0336
Note You need to log in before you can comment on or make changes to this bug.