Bug 545708 - Apache - Apache server does not return an error when attempted to start from UI when it is already running.
Summary: Apache - Apache server does not return an error when attempted to start from ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: RHQ Project
Classification: Other
Component: Configuration
Version: 1.4
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: rhq_spearhead jon24-apache
TreeView+ depends on / blocked
 
Reported: 2009-12-09 06:42 UTC by Sunil Kondkar
Modified: 2010-05-11 19:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-11 19:25:04 UTC
Embargoed:

Attachments (Terms of Use)

Description Sunil Kondkar 2009-12-09 06:42:44 UTC 
Description of problem:

If Apache server is already running and user tries to start it again from imanage UI, it displays the operation status as success. It should return an error.

Version-Release number of selected component (if applicable):
1.4.0-SNAPSHOT

How reproducible:


Steps to Reproduce:

Login to imanage UI.
Navigate to dashboard
select apache service.
Navigate to 'Operations' tab.
Click on the link 'Start'(Apache server should be already running.
Select shedular component as 'immediately'.
Click on the 'Schedule' button.
  
Actual results:
It displays success and does not return error.

Expected results:
It should return an error message.

Additional info:
Comment 1 wes hayutin 2010-02-16 16:54:22 UTC 
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug
Comment 2 wes hayutin 2010-02-16 16:59:49 UTC 
making sure we're not missing any bugs in rhq_triage
Comment 3 Filip Drabek 2010-04-22 10:40:52 UTC 
I'm not sure if this is a problem or bug. 
User can see the availability of httpd server in RHQ and start operation will not fail, so I don't see a reason for reporting error.
Note You need to log in before you can comment on or make changes to this bug.