Description of problem: With older configuration Version-Release number of selected component (if applicable): virt-who-0.20.4-1.el7 How reproducible: move virt-who config from a server running virt-who-0.19-7.el7_4 older version configuration [vcenter] type=esx owner=satellite env=Library server=vcenter.example.com username=root encrypted_password=12s3sdf3rfegfggdfgfd newer configuration [virt-who-config-1] type=esx hypervisor_id=hostname owner=Default_Organization env=Library server=vcenter.example.com username=root encrypted_password=03388fc9eac3155ee961746de124e1d1 rhsm_hostname=sat1.localdomain rhsm_username=virt_who_reporter_1 rhsm_encrypted_password=0d7e390d8224fd32c18f307237162b99885891b1911443569ad9906754d74711 rhsm_prefix=/rhsm Steps to Reproduce: 1.move virt-who config from a server running virt-who-0.19-7.el7_4 2. run virt-who -o 3. Actual results: 2017-12-08 11:29:56,277 INFO: Using configuration "vcenter" ("esx" mode) 2017-12-08 11:29:56,278 INFO: Using reporter_id='sat1-b5a1839d64c4457b95bd4b9e7f6ec02e' 2017-12-08 11:29:56,598 INFO: Report for config "vcenter" gathered, placing in datastore 2017-12-08 11:29:57,295 INFO: Hosts-to-guests mapping for config "vcenter": 1 hypervisors and 4 guests found 2017-12-08 11:29:58,487 ERROR: Error during hypervisor checkin: ManagerError: Communication with subscription manager failed with code 505: Network error code: 505 Expected results: Additional info:
(In reply to Cory McKee from comment #0) > Description of problem: > With older configuration > > Version-Release number of selected component (if applicable): > virt-who-0.20.4-1.el7 > > How reproducible: > move virt-who config from a server running virt-who-0.19-7.el7_4 > > older version configuration > [vcenter] > type=esx > owner=satellite > env=Library > server=vcenter.example.com > username=root > encrypted_password=12s3sdf3rfegfggdfgfd > > newer configuration > [virt-who-config-1] > type=esx > hypervisor_id=hostname > owner=Default_Organization > env=Library > server=vcenter.example.com > username=root > encrypted_password=03388fc9eac3155ee961746de124e1d1 > rhsm_hostname=sat1.localdomain > rhsm_username=virt_who_reporter_1 > rhsm_encrypted_password=0d7e390d8224fd32c18f307237162b99885891b1911443569ad99 > 06754d74711 > rhsm_prefix=/rhsm > > Steps to Reproduce: > 1.move virt-who config from a server running virt-who-0.19-7.el7_4 > 2. run virt-who -o > > 3. > > Actual results: > 2017-12-08 11:29:56,277 INFO: Using configuration "vcenter" ("esx" mode) > 2017-12-08 11:29:56,278 INFO: Using > reporter_id='sat1-b5a1839d64c4457b95bd4b9e7f6ec02e' > 2017-12-08 11:29:56,598 INFO: Report for config "vcenter" gathered, placing > in datastore > 2017-12-08 11:29:57,295 INFO: Hosts-to-guests mapping for config "vcenter": > 1 hypervisors and 4 guests found > 2017-12-08 11:29:58,487 ERROR: Error during hypervisor checkin: > ManagerError: Communication with subscription manager failed with code 505: > Network error code: 505 > > > Expected results: > > > Additional info: I don't think this one makes much sense. The older version config still works today. The newer config requires that rhsm lines because that is what allows us to run virt-who on a NON self registered Satellite. You can still run the old version config on a client pointing to the satellite or a self registered satellite. +1 to close won't fix