Bug 1477245

Summary: spacewalk-hostname-rename: File not found: /usr/share/rhn/config-defaults/rhn_pgversion.conf
Product: Red Hat Satellite 5 Reporter: Lukáš Hellebrandt <lhellebr>
Component: ServerAssignee: Tomáš Kašpárek <tkasparek>
Status: CLOSED WONTFIX QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 580CC: dyordano, rdrazny, tkasparek, tlestach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-01 13:13:50 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: 1450111, 1582457    

Description Lukáš Hellebrandt 2017-08-01 14:43:38 UTC
Description of problem:
When running spacewalk-hostname-rename on a satellite withOUT embedded database, spacewalk-hostname rename says:

CONFIG PARSE WARNING: File not found or can't be read /usr/share/rhn/config-defaults/rhn_pgversion.conf
CONFIG PARSE WARNING: key not found in config default dict ('pgversion',)

I do not know of any issues caused by this yet. However, these error messages are not something users should see, particularly the "key not found" one.

How reproducible:
Deterministic

Steps to Reproduce:
On Satellite running against ManagedDB:
#spacewalk-hostname-rename <IP>
CONFIG PARSE WARNING: File not found or can't be read /usr/share/rhn/config-defaults/rhn_pgversion.conf
CONFIG PARSE WARNING: key not found in config default dict ('pgversion',)
Validating IP ... OK
=============================================
hostname: <hostname>
ip: <IP>
=============================================
Stopping rhn-satellite services ... OK
Testing DB connection ... OK
Updating /etc/rhn/rhn.conf ... OK
Actual SSL key pair package: <package>
 No need to re-generate SSL certificate.
Regenerating new bootstrap client-config-overrides.txt ... OK
Updating NOCpulse.ini ... OK
Updating monitoring data ... OK
Updating other DB entries ... OK
Changing cobbler settings ... OK
Changing jabberd settings ... OK
Starting rhn-satellite services ... OK


Actual results:
Warnings, but probably (!) no issues caused

Expected results:
No warning and no issue caused