Bug 1450457

Summary:	Configuration Manager name change not displayed
Product:	Red Hat CloudForms Management Engine	Reporter:	Tasos Papaioannou <tpapaioa>
Component:	UI - OPS	Assignee:	lgalis
Status:	CLOSED CURRENTRELEASE	QA Contact:	Tasos Papaioannou <tpapaioa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.8.0	CC:	hkataria, izapolsk, jhardy, mpovolny, obarenbo, simaishi
Target Milestone:	GA	Keywords:	TestOnly, ZStream
Target Release:	5.9.0
Hardware:	All
OS:	All
Whiteboard:	provider:foreman
Fixed In Version:	5.9.0.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1478513 (view as bug list)		Environment:
Last Closed:	2018-03-06 15:01:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1478513

Description Tasos Papaioannou 2017-05-12 15:40:09 UTC

Description of problem:

After I edit and change the name of a Satellite configuration manager, the name still shows as "<old name> Configuration Manager" when viewing the list of configuration managers. Going back into the edit page does show the new name, however. 

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

5.8.0.14-rc3

How reproducible:

100%

Steps to Reproduce:
1.) Create a new Satellite configuration manager, called "test".
2.) Edit the configuration manager and change the name to "test2".
3.) The Configuration Management Providers page still shows "test Configuration Manager" under Provider Name.
4.) Re-editing the manager shows the new name "test2" under Name.

Actual results:

Old configuration manager name shows on Configuration Management Providers page.

Expected results:

New configuration manager name shows on Configuration Management Providers page.


Additional info:

In the database,

The ems records still show the old name:

vmdb_production=# select id, name, provider_id from ext_management_systems;
 id |            name            | provider_id 
----+----------------------------+-------------
  9 | test Configuration Manager |           5
 10 | test Provisioning Manager  |           5
(2 rows)

Only the provider record name was updated:

vmdb_production=# select id, name from providers;
 id | name  
----+-------
  5 | test2
(1 row)

Comment 2 Tasos Papaioannou 2017-05-12 16:09:50 UTC

Also, after changing the name, the status of the provider becomes "Invalid", with HTTP 401 authorization errors showing up in evm.log:

****
[----] I, [2017-05-12T12:03:24.206773 #12031:727130]  INFO -- : MIQ(MiqGenericWorker::Runner#get_message_via_drb) Message id: [1081], MiqWorker id: [12], Zone: [default], Role: [], Server: [], Ident: [generic], Target id: [], Instance id: [5], Task id: [], Command: [Provider.authentication_check_types], Timeout: [600], Priority: [100], State: [dequeue], Deliver On: [], Data: [], Args: [[:default], {}], Dequeued in: [6.786678324] seconds
[----] I, [2017-05-12T12:03:24.207112 #12031:727130]  INFO -- : MIQ(MiqQueue#deliver) Message id: [1081], Delivering...
[----] I, [2017-05-12T12:03:24.221217 #12031:727130]  INFO -- : MIQ(ManageIQ::Providers::Foreman::Provider#with_provider_connection) Connecting through ManageIQ::Providers::Foreman::Provider: [test2]
[----] I, [2017-05-12T12:03:24.229212 #12031:727130]  INFO -- : ForemanApiClient::Connection#fetch Calling Apipie Resource: :home Action: :index Params: {"root_pass"=>"<FILTERED>"}
[----] W, [2017-05-12T12:03:24.493941 #12031:727130]  WARN -- : MIQ(ManageIQ::Providers::Foreman::Provider#authentication_check_no_validation) type: [:default] for [5] [test2] Validation failed: invalid, 401 Unauthorized
[----] W, [2017-05-12T12:03:24.494846 #12031:727130]  WARN -- : MIQ(AuthUseridPassword#validation_failed) [Provider] [5], previously valid on: 2017-05-12 15:57:16 UTC, previous status: [Valid]
[----] I, [2017-05-12T12:03:24.517652 #12031:727130]  INFO -- : MIQ(MiqQueue#delivered) Message id: [1081], State: [ok], Delivered in [0.3105212] seconds
****

Comment 3 lgalis 2017-06-21 19:01:49 UTC

*** Bug 1462311 has been marked as a duplicate of this bug. ***

Comment 6 Tasos Papaioannou 2017-10-09 14:45:57 UTC

Verified on 5.9.0.1.