Bug 1477631 - spacewalk-hostname-rename: "cat: /var/lib/nocpulse/.ssh/nocpulse-identity.pub: No such file or directory"
spacewalk-hostname-rename: "cat: /var/lib/nocpulse/.ssh/nocpulse-identity.pub...
Status: CLOSED DEFERRED
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server (Show other bugs)
570
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Tomáš Kašpárek
Red Hat Satellite QA List
:
Depends On:
Blocks: sat5-rhn
  Show dependency treegraph
 
Reported: 2017-08-02 09:49 EDT by Lukáš Hellebrandt
Modified: 2018-04-09 11:34 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-09 11:34:55 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Lukáš Hellebrandt 2017-08-02 09:49:50 EDT
Description of problem:
When there is no /var/lib/nocpulse/.ssh/nocpulse-identity.pub file, spacewalk-hostname-rename says:

cat: /var/lib/nocpulse/.ssh/nocpulse-identity.pub: No such file or directory

... and continues without any issue.

Hint - this condition looks fishy (where does the variable get set?):
if [ -e $NOCPULSE_OLD_PUBLIC_KEY ] on line 499 of spacewalk-hostname-rename.

Version-Release number of selected component (if applicable):
Sat 5.7: spacewalk-utils-2.3.2-32
Also applies to Sat 5.6: spacewalk-utils-2.0.2-28

How reproducible:
Deterministic

Steps to Reproduce:
1. Have a Satellite without /var/lib/nocpulse/.ssh/nocpulse-identity.pub file existing
2. # spacewalk-hostname-rename <IP>
[...]
Updating NOCpulse.ini ... OK
Updating monitoring data ... cat: /var/lib/nocpulse/.ssh/nocpulse-identity.pub: No such file or directory
OK
[...]

Actual results:
Warning shown, I haven't noticed any issues caused by this yet

Expected results:
No warning, no issues
Comment 1 Tomas Lestach 2018-04-09 11:34:55 EDT
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. 

Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.

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