Bug 619290 - 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 NOTABUG
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 1.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On: 619288
Blocks: space11
TreeView+ depends on / blocked
 
Reported: 2010-07-29 07:48 UTC by Miroslav Suchý
Modified: 2012-03-06 09:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 619288
Environment:
Last Closed: 2010-07-29 07:53:30 UTC
Embargoed:

Attachments (Terms of Use)

Description Miroslav Suchý 2010-07-29 07:48:02 UTC 
+++ This bug was initially created as a clone of Bug #619288 +++

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:

--- Additional comment from xdmoon on 2010-07-29 03:40:01 EDT ---

Created an attachment (id=435206)
satsync.py.TEST.1171433.1.patch
Note You need to log in before you can comment on or make changes to this bug.