Bug 559897 - Apache: cannot uncheck unset checkbox for apache Name Virtual Host 'index' field.
Summary: Apache: cannot uncheck unset checkbox for apache Name Virtual Host 'index' fi...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: RHQ Project
Classification: Other
Component: Configuration
Version: 1.4
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Lukas Krejci
QA Contact:
URL:
Whiteboard:
: 560584 (view as bug list)
Depends On:
Blocks: rhq_spearhead jon-sprint7-bugs jon-sprint8-bugs
TreeView+ depends on / blocked
 
Reported: 2010-01-29 10:08 UTC by Sunil Kondkar
Modified: 2010-04-22 10:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-22 10:29:23 UTC
Embargoed:


Attachments (Terms of Use)

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.


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