Bug 559897

Summary:	Apache: cannot uncheck unset checkbox for apache Name Virtual Host 'index' field.
Product:	[Other] RHQ Project	Reporter:	Sunil Kondkar <skondkar>
Component:	Configuration	Assignee:	Lukas Krejci <lkrejci>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.4	CC:	fdrabek, lkrejci, sdharane
Target Milestone:	---	Keywords:	SubBug
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-04-22 10:29:23 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	565635, 574605, 576714

Description Sunil Kondkar 2010-01-29 10:08:01 UTC

Description of problem:
Apache: The unset checkbox for apache Name Virtual Host 'index' field cannot be checked/unchecked.

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

How reproducible:


Steps to Reproduce:

Login to imanage UI
Select the apache httpd resource
Click on 'Configuration' tab.
Click on 'Edit' button.
Click on 'Add New' button for 'Name Virtual Host' section.
Enter address and try to click on 'Unset' checkbox for index field.
  
Actual results:
The unset checkbox for apache Name Virtual Host 'index' field cannot be checked/unchecked.

Expected results:
User should be able to click and check/uncheck 'Unset' checkbox for index field.

Additional info:

Comment 1 Sunil Kondkar 2010-02-09 08:00:52 UTC

*** Bug 560584 has been marked as a duplicate of this bug. ***

Comment 2 wes hayutin 2010-02-16 16:55:40 UTC

Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug

Comment 3 wes hayutin 2010-02-16 17:00:45 UTC

making sure we're not missing any bugs in rhq_triage

Comment 4 Lukas Krejci 2010-03-18 13:48:31 UTC

This is intended behaviour. The _index property is auxiliary and used internally by the plugin. The user should not have the ability to edit them. Unfortunately, there is no way of hiding configuration properties from the UI but I think effort has been made to stress that the property is not user-oriented. The leading "_" + the description of the property should explain the purpose of the property.

The description reads:
"Helper property to retain the consistent ordering inside Apache configuration files."

which could probably be rephrased a bit to be more clear about the purpose.