Bug 741610 - Bad sequence of steps or extra pointless command in 3.1 Start Console - First Run
Summary: Bad sequence of steps or extra pointless command in 3.1 Start Console - First...
Keywords:
Status: CLOSED DUPLICATE of bug 738793
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Management_Console_Installation_Guide
Version: Development
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Alison Young
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-27 12:35 UTC by Daniel Horák
Modified: 2011-09-30 14:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-30 14:08:25 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Daniel Horák 2011-09-27 12:35:43 UTC
Description of problem:
In 'Management Console Installation Guide' in chapter '3. Start Console' in
section '3.1. First Run' last command in 3th step is '# /sbin/service cumin stop' and then 4th step is about open internet browser and go to http://localhost:45672/. But the service provides this page is not running (in relationship with previous command). The last command for stop cumin is probably not necessary.

Version-Release number of selected component (if applicable):
2.0 stage documentation

Actual results:
# /sbin/service cumin status 
cumin (pid PID) is running... 

# /sbin/service cumin restart 
Stopping Cumin daemon:                    [  OK   ] 
Starting Cumin daemon:                    [  OK   ] 

# /sbin/service cumin stop 
Stopping Cumin daemon:                    [  OK   ]


Expected results:
# /sbin/service cumin status 
cumin (pid PID) is running... 

# /sbin/service cumin restart 
Stopping Cumin daemon:                    [  OK   ] 
Starting Cumin daemon:                    [  OK   ]

Comment 2 Matthew Farrellee 2011-09-30 14:08:25 UTC

*** This bug has been marked as a duplicate of bug 738793 ***


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