Bug 709977 - cobblerd does not appear to be running/accessible
Summary: cobblerd does not appear to be running/accessible
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Installer
Version: 541
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Pazdziora (Red Hat)
QA Contact: Jiří Mikulka
URL:
Whiteboard:
Depends On:
Blocks: sat560-lowbug
TreeView+ depends on / blocked
 
Reported: 2011-06-02 06:50 UTC by Šimon Lukašík
Modified: 2014-10-06 13:46 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-01 21:56:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Šimon Lukašík 2011-06-02 06:50:12 UTC
Description of problem:
The RHN Satellite instalator prints out:

    cobblerd does not appear to be running/accessible

it happens in 100% cases. Hopefully, the message is harmless and
meanless and as such it can be hidden from the shipshape installer.

Version-Release number of selected component (if applicable):
RHN Satellite 5.4.0
RHN Satellite 5.4.1

How reproducible:
always

Steps to Reproduce:
1. ./install.pl
2.
3.
  
Actual results:
* Update configuration in database.
* Setting up Cobbler..
cobblerd does not appear to be running/accessible
* Restarting services.

Expected results:
* Update configuration in database.
* Setting up Cobbler..
* Restarting services.

Comment 2 Jan Pazdziora (Red Hat) 2013-03-28 09:41:26 UTC
Fixed in Spacewalk master, f3e1c95c7d47778d577daec14f087cbda64c36bf. We no longer try to run cobbler sync when cobblerd is not started at all.

Comment 4 Clifford Perry 2013-10-01 21:56:50 UTC
Satellite 5.6 has been released. This bug was tracked under the release.  

This bug was either VERIFIED or RELEASE_PENDING (re-verified prior shortly
before release). 

Moving to CLOSED CURRENT_RELEASE. 

Text from Upgrade Erratum follows:

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2013-1395.html


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