Red Hat Bugzilla – Bug 1445735
Add provider: No validation for non 'default' tab on init
Last modified: 2018-06-05 07:53:43 EDT
Description of problem: In the add provider page for all providers, when there is more then one endpoint the first tab starts as non valid with a red marker next to the tab name. You can then fill in the first tab and add the provider. The reason i'm pretty sure this is not intentional is that if you go to a secondary tab, press inside an input element and then out side they tab will switch to invalid. Version-Release number of selected component (if applicable): 5.8.12 How reproducible: 100% Steps to Reproduce: 1. Go to compute/containers -> add provider Actual results: - 'default' tab has red error marker next to tab name. 'hawkular' tab does not - after filling in & validating only the 'default' endpoint it is possible to add the provider Expected results: - both tabs should start with the error marker. - it should not be possible to add a provider with out filling and validating both endpoints
Creating both a rhev provider without going to the second tab will result in: > x.connection_configurations[:metrics].hostname => nil Doing the same with a container provider will result in > x.connection_configurations['hawkular'].port => nil These are both malformed endpoints
https://github.com/ManageIQ/manageiq-ui-classic/pull/1172
New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/e5bc4751cf256203cd8c91f26f120833f71fbee2 commit e5bc4751cf256203cd8c91f26f120833f71fbee2 Author: Aparna Karve <akarve@redhat.com> AuthorDate: Wed Apr 26 12:55:11 2017 -0700 Commit: Aparna Karve <akarve@redhat.com> CommitDate: Wed Apr 26 12:55:11 2017 -0700 Ensure that the Hawkular tab displays an error indicator https://bugzilla.redhat.com/show_bug.cgi?id=1445735 .../javascripts/controllers/ems_common/ems_common_form_controller.js | 2 +- app/controllers/mixins/ems_common_angular.rb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
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/RHSA-2018:0380