Red Hat Bugzilla – Bug 683108
System settings not all set in GUI for fresh DB
Last modified: 2011-05-23 21:15:46 EDT
2) Start CoreGUI
3) Admin->System Settings
4) Inspect the Yes/No radio box props
5) Try to save a change to, say, Agent suspect down time
For me, this failed and I had to explicitly set all of the Yes/No props. These should be set to defaults at install time and should not need to be set in the GUI when visiting system settings (of course, they should be able to be changed as desired).
we need to look at the data in RHQ_SYSTEM_CONFIG and make sure the values coming out of it and into the radio button components are valid values. If the setValue() values of the radio buttons are what the component wants (non-null Boolean) then it won't render any value and you will be forced to enter one.
the problem is enable_debug and enable_experimental settings aren't in rhq_system_config by default. I made the system config view more tolerant in any case where a config setting isn't in the db but we have a default value we can assume.
With a fresh DB, in addition to the two mentioned above, the following properties were also flagged as invalid when I tried to save the system settings:
Enable Agent Auto-Updates
Reindex Data Tables Nightly
Strangely, they had values (i.e. one of the Yes/No radio buttons was selected), so I'm not sure why they were considered invalid.
I'm gonna flip this back to ON_QA and see how testing goes. My fix was general - it should correct any missing props.
this is verified in the 4/29/2011 release testing.
Bookkeeping - closing bug - fixed in recent release.