Description of problem:
When /var/satellite (or whatever the mount_point is) is empty, satellite-sync (e.g., satellite-sync -l) returns "ERROR: server.mount_point not set in the configuration file". This is confusing to the user, customer suggests displaying "invalid server.mount_point" instead.
Version-Release number of selected component (if applicable):
Red Hat Network (RHN) Satellite 5.3.0
Steps to Reproduce:
1. Have mount_point in /etc/rhn/rhn.conf point to an empty directory.
3. Run satellite-sync -l
ERROR: server.mount_point not set in the configuration file
ERROR: invalid server.mount_point set in the configuration file
Created attachment 435206 [details]
Already fixed during my investigation of BZ 614667 in commit 62a13f980c1b4fd016b9b3b00d1631b6a8969c77 in spacewalk.git.
Leaving to open to have it pass through QA as separate BZ.
The message should be:
ERROR: server.mount_point %s do not exist
and if some other path in server.mount_point do not exist, it should print:
ERROR: path under server.mount_point (%s) do not exist
The 5.4.0 RHN Satellite and RHN Proxy release has occurred. This issue has been resolved with this release.
RHEA-2010:0801 - RHN Satellite Server 5.4.0 Upgrade
RHEA-2010:0803 - RHN Tools enhancement update
RHEA-2010:0802 - RHN Proxy Server 5.4.0 bug fix update
RHEA-2010:0800 - RHN Satellite Server 5.4.0
Docs are available: