Bug 576617 - [apache] ServerName not persisted with Virtual host update
Summary: [apache] ServerName not persisted with Virtual host update
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 3.0.0
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
: ---
Assignee: Filip Drabek
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: jon24-apache
TreeView+ depends on / blocked
 
Reported: 2010-03-24 16:18 UTC by Lukas Krejci
Modified: 2010-08-12 16:56 UTC (History)
1 user (show)

Fixed In Version: 2.4
Clone Of:
Environment:
Last Closed: 2010-08-12 16:56:49 UTC
Embargoed:

Attachments (Terms of Use)

Description Lukas Krejci 2010-03-24 16:18:46 UTC 
Description of problem:

see bug summary

How reproducible:

always

Steps to Reproduce:
1. Make any update throught the UI to some virtual host with ServerName defined in httpd.conf.
2. Save the changes in the UI.
3. Look at the updated httpd.conf. The ServerName directive is missing.
  
Actual results:

Virtual host gets corrupted.

Expected results:

Update should retain the unchanged properties.
Comment 2 Charles Crouch 2010-05-18 14:03:41 UTC 
ServerName should be read-only
Comment 3 Filip Drabek 2010-05-18 15:33:20 UTC 
commit 09013bf47ff002214dad4f9e21130acacf526234
Comment 4 Corey Welton 2010-05-20 18:15:07 UTC 
I was able to edit this and the change was made successfully.  However, per comment #2, should users even be able to populate this field?
Comment 5 Corey Welton 2010-05-20 18:34:39 UTC 
I just checked this on a build from a few hours ago.  User is able to change servername.  Unless this was never checked into master, I think we fixed the first part, but per the comment above, I think we shouldn't be able to change it at all.

Will return to dev for now; once we have a resolution one way or another, I can close it out.
Comment 7 Corey Welton 2010-06-04 13:03:40 UTC 
QA Verified.
Comment 8 Corey Welton 2010-08-12 16:56:49 UTC 
Mass-closure of verified bugs against JON.
Note You need to log in before you can comment on or make changes to this bug.