Red Hat Bugzilla – Bug 1287637
Pressing Save or Reset in Advanced Config disables buttons permanently
Last modified: 2016-06-29 11:15:52 EDT
Description of problem: Save/Reset buttons turn on when first using the Advanced Config form, but are disabled if a change is saved or reset. The buttons no longer become enabled when typing changes in. Version-Release number of selected component (if applicable): 5.5.0 How reproducible: Make changes in advanced config, save/reset, try to make more changes Actual results: Buttons stay disabled Expected results: Buttons enabled when changes are made Additional info: Discovered when testing https://github.com/ManageIQ/manageiq/pull/5656
https://github.com/ManageIQ/manageiq/pull/5682
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/666490053b83845b7b983ebba74f8ed0bbabec6b commit 666490053b83845b7b983ebba74f8ed0bbabec6b Author: Dávid Halász <dhalasz@redhat.com> AuthorDate: Wed Dec 2 16:38:38 2015 +0100 Commit: Dávid Halász <dhalasz@redhat.com> CommitDate: Mon Dec 7 13:55:18 2015 +0100 Fixed onchange enabling of save/reset buttons in ops codemirror https://bugzilla.redhat.com/show_bug.cgi?id=1287637 app/controllers/ops_controller.rb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
New commit detected on cfme/5.5.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=f18e42a87762cf0c43c1478183f4bde91620a34e commit f18e42a87762cf0c43c1478183f4bde91620a34e Author: Dávid Halász <dhalasz@redhat.com> AuthorDate: Wed Dec 2 16:38:38 2015 +0100 Commit: Dávid Halász <dhalasz@redhat.com> CommitDate: Mon Dec 7 15:54:07 2015 +0100 Fixed onchange enabling of save/reset buttons in ops codemirror https://bugzilla.redhat.com/show_bug.cgi?id=1287637 Clean cherrypick from: https://github.com/ManageIQ/manageiq/pull/5682 (cherry picked from commit 666490053b83845b7b983ebba74f8ed0bbabec6b) app/controllers/ops_controller.rb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
Verified in 5.6.0.1-beta2
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. https://access.redhat.com/errata/RHBA-2016:1348