Yaacov should this be moved to POST?
Backported: https://github.com/ManageIQ/manageiq/pull/9947
Created attachment 1204389 [details] provider showing line. Bug returned to dev. After editing a new provider, the same line appears: Default Authentication - None. Screenshot attached.
Bug failed. Line is still showing up. new screenshot attached.
https://github.com/ManageIQ/manageiq/pull/11504
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/a1147c93451a834c6476151f7a30e82297ee3f5b commit a1147c93451a834c6476151f7a30e82297ee3f5b Author: yaacov <kobi.zamir> AuthorDate: Sun Sep 25 15:38:27 2016 +0300 Commit: yaacov <kobi.zamir> CommitDate: Tue Nov 1 11:21:16 2016 +0200 Reove the extra "default" authentication created when editing a container provider. PR #9947 solved the removal of the extra "default" authentications only in cases where the params[:default_password] was not blank (this is not always true), this PR fixes that, and remove the extra authenication in all the cases the where the external manegment system is container manager. Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1370576 https://bugzilla.redhat.com/show_bug.cgi?id=1389278 app/controllers/mixins/ems_common_angular.rb | 21 +++++++++++---------- .../providers/kubernetes/container_manager_mixin.rb | 2 +- app/models/mixins/authentication_mixin.rb | 6 +++--- spec/controllers/ems_common_controller_spec.rb | 6 ++++++ 4 files changed, 21 insertions(+), 14 deletions(-)
Yaacov should this be in POST?
> Yaacov should this be in POST? This BZ is on Darga, and it's not backported yet.
a PR specific for Darga submited upstream: https://github.com/ManageIQ/manageiq/pull/12367
merged: https://github.com/ManageIQ/manageiq/pull/12367
Verified. Steps: Modified Provider name - Save new details. View Provider summary page. Results: No new additional line with "Default Authentication" seen.
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://rhn.redhat.com/errata/RHSA-2016-2839.html