Bug 1304773

Summary: Unable to edit fence agents
Product: [oVirt] ovirt-engine Reporter: Alexander Wels <awels>
Component: Frontend.WebAdminAssignee: Alexander Wels <awels>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.6.3CC: bugs, oourfali, pmatyas, sbonazzo
Target Milestone: ovirt-3.6.3Flags: rule-engine: ovirt-3.6.z+
rule-engine: exception+
rule-engine: planning_ack+
oourfali: devel_ack+
rule-engine: testing_ack+
Target Release: 3.6.3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-18 11:10:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: UX RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alexander Wels 2016-02-04 15:09:06 UTC 
Description of problem:
When editing a fence agent without changing the management ip or type and clicking ok. The UI will highlight the management ip and type and indicate there is a duplicate fence agent.

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


How reproducible:
100%

Steps to Reproduce:
1. Go to edit host with a host that has some fence agents configured.
2. Click one of the existing fence agents to open up the edit dialog.
3. Change something that is no the mangement ip and type (lets say options).
4. Click OK and you will see red boxes around the management IP/type and it won't allow you to save the changes.

Actual results:
See reproduction steps.

Expected results:
You can save changes to non mangement ip/type.

Additional info:
Comment 1 Red Hat Bugzilla Rules Engine 2016-02-04 15:10:59 UTC 
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Comment 2 Red Hat Bugzilla Rules Engine 2016-02-04 15:10:59 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 3 Red Hat Bugzilla Rules Engine 2016-02-04 15:22:18 UTC 
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Comment 4 Red Hat Bugzilla Rules Engine 2016-02-04 16:02:51 UTC 
Fixed bug tickets must have version flags set prior to fixing them. Please set the correct version flags and move the bugs back to the previous status after this is corrected.
Comment 5 Petr Matyáš 2016-02-10 14:30:29 UTC 
Verified on 3.6.3-2