Bug 619288 - Confusing error message from satellite-sync if mount point is empty (ERROR: server.mount_point not set in the configuration file)
Summary: Confusing error message from satellite-sync if mount point is empty (ERROR: s...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization
Version: 530
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact: Martin Minar
URL:
Whiteboard:
Depends On:
Blocks: sat540-blockers 619290
TreeView+ depends on / blocked
 
Reported: 2010-07-29 07:37 UTC by Xixi
Modified: 2018-10-27 13:30 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 619290 (view as bug list)
Environment:
Last Closed: 2010-10-28 14:56:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
satsync.py.TEST.1171433.1.patch (533 bytes, patch)
2010-07-29 07:40 UTC, Xixi
no flags Details | Diff

Description Xixi 2010-07-29 07:37:14 UTC
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

How reproducible:
Always.

Steps to Reproduce:
1. Have mount_point in /etc/rhn/rhn.conf point to an empty directory.
3. Run satellite-sync -l

Actual results:
ERROR: server.mount_point not set in the configuration file

Expected results:
ERROR: invalid server.mount_point set in the configuration file

Additional info:

Comment 1 Xixi 2010-07-29 07:40:01 UTC
Created attachment 435206 [details]
satsync.py.TEST.1171433.1.patch

Comment 2 Miroslav Suchý 2010-07-29 07:57:34 UTC
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

Comment 4 Martin Minar 2010-09-02 13:52:12 UTC
Verified

Comment 8 Clifford Perry 2010-10-28 14:51:50 UTC
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
https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10332

RHEA-2010:0803 - RHN Tools enhancement update
https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10333

RHEA-2010:0802 - RHN Proxy Server 5.4.0 bug fix update
https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10334

RHEA-2010:0800 - RHN Satellite Server 5.4.0
https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10335

Docs are available:

http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/index.html 

Regards,
Clifford


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