Bug 795690 - RHEV-H 6.3: RHEV-H save invalid configuration
Summary: RHEV-H 6.3: RHEV-H save invalid configuration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 6.3
Assignee: Fabian Deutsch
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-21 10:04 UTC by cshao
Modified: 2016-04-26 16:38 UTC (History)
10 users (show)

Fixed In Version: ovirt-node-2.3.0-4.el6
Doc Type: Bug Fix
Doc Text:
Previously, when configuring the Hypervisor, invalid input would be saved to disk and persisted, causing inconsistent or incorrect behavior. Now, when invalid input is detected, it is not persisted to the configuration files.
Clone Of:
Environment:
Last Closed: 2012-07-19 14:18:59 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0741 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2012-07-19 18:10:46 UTC

Description cshao 2012-02-21 10:04:52 UTC
Description of problem:
RHEV-H save invalid configuration.
(such as: Invalid NFS Entry; Invalid NetConsole Hostname or Address)

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.3-20120215.0.el6

How reproducible:
100%

Steps to Reproduce:
1. Install RHEV-H 6.3.
2. Enter logging menu, input invalid server address (e.g. "......")
3. Press "Apply" button.
4. Enter kdump menu, input invalid NFS (e.g. "......")
5. cat /etc/rsysconfig.conf
6. cat /etc/sysconfig/netconsole.conf
7. cat /etc/kdump.conf
  
Actual results:
Warning message will pop-up when input invalid info.
RHEV-H save invalid configuration.

# cat /etc/kdump.conf 
default reboot
net ......

Expected results:
RHEV-H only persist valid configuration.

Additional info:

Comment 2 Fabian Deutsch 2012-04-18 12:07:08 UTC
My plan is to re-check the validity of all fields when the "Apply" button is pressed.
If there are any fields with invalid values, a popup will appear naming the and request the user to fix them before the changes can be applied.

Comments?

Comment 3 Joey Boggs 2012-04-18 12:57:26 UTC
sounds good, for the most part I believe the values if blank or incorrect will clear out, may want to check that first

Comment 4 Mike Burns 2012-04-18 16:30:38 UTC
also make sure that navigating off the screen (up/down) doesn't cause an issue (it shouldn't, but doesn't hurt to double check)

Comment 5 Fabian Deutsch 2012-04-19 07:52:28 UTC
(In reply to comment #3)
> sounds good, for the most part I believe the values if blank or incorrect will
> clear out, may want to check that first

That sounded like a good idea, the problem is that e.g. if someone enters a character as a port number, I can not just blank it, as this might be needed to write the configuration.

Comment 6 Fabian Deutsch 2012-04-19 10:25:03 UTC
Ok, I just saw (In reply to comment #5)
> (In reply to comment #3)
> > sounds good, for the most part I believe the values if blank or incorrect will
> > clear out, may want to check that first

Ok, I just saw how it's done on othe fields right now. This patch also does it this way:

http://gerrit.ovirt.org/#change,3711

Tested as follows:
- Installed node
- Enter the TUI
- Select the Logging page
- Append an "a" to the max file size field
- Leave the field using down-arrow or TAB
- A dialog pops up, telling the field is containing an invalid value
- Select "OK"
= The field is reset to "1024"
- Select the KDump page
- Enable NFS
- Change the NFS server field to "---"
- Leave the field using down-arrow or TAB
- A dialog pops up, telling the field is containing an invalid value
- Select "OK"
= The field is reset to ""
- Press F2 to drop to shell
- /etc/kdump.conf does not exist

Comment 13 Mike Burns 2012-06-13 17:28:50 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, when configuring certain functionality, invalid input would be saved causing inconsistent or incorrect behavior.  Now, when invalid input is detected, it will not be persisted to the configuration files.

Comment 14 Stephen Gordon 2012-06-14 15:05:51 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-Previously, when configuring certain functionality, invalid input would be saved causing inconsistent or incorrect behavior.  Now, when invalid input is detected, it will not be persisted to the configuration files.+Previously, when configuring the Hypervisor, invalid input  would be saved to disk and persisted, causing inconsistent or incorrect behavior. Now, when invalid input is detected, it is not persisted to the configuration files.

Comment 16 errata-xmlrpc 2012-07-19 14:18:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0741.html


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