Satellite 6.1 Not Importing From virt-who
New installation of Satellite 6.1 and I'm getting it set up on a RHEL7.2 server. I have virt-who running with proper access to the VMWare VCenter url. There are 1,869 Virtual Machines in the log file so I know it's logging in and enumerating correctly, just not importing the VMs into Satellite.
In checking the Satellite Console, Content Hosts which is where these should be showing up per the User Guide, I'm getting nothing.
Per the User Guide, there should be a key file for the ESX server in the /var/lib/virt-who directory but only the key file is there.
I'm using the config files in /etc/virt-who.d and ran the identify command to get the site id for the config file.
Everything appears to be set up correctly, just no hosts.
With all these Virtual Machines, I thought it might just be taking a while but nothing after several days.
I went out to the virt-who site to see if there were any conversations on the tool but there have been no emails for almost a year so it seems pretty quiet.
Responses
Unix Admin,
How many ESX hosts do you have in your environment?
Are your ESX hosts showing up as Content Hosts in Satellite 6.x? (they may be a random collection of UUIDs).
I had several reliability issues with virt-who on an environment with ~120 ESX hosts, and after re-running it without changing configuration several times it seemed to resolve itself.
It should also be clarified that virt-who doesn't import all the VMs (in my experience) only the ESX hosts as content hosts. You then register the VMs as normal (usual Satellite process), and the licenses and host/guest relationships are mapped using the information brought in through virt-who.
I have setup virt-who... and deleted all my hosts that I had subscribed earlier. I am not seeing any of the ESXi machines showing up as hosts in Satellite 6. Can you let me know whether there is something else I need to be doing or a log I could send you?
Can you also validate that we are licensed to have up to 25 hypervisor hosts with unlimited guests?
The problem description is not clear. The virt-who service pulls in your hypervisors and show them in Satellite6 Web UI and the actual VMs. The VMs should be registered manually to Satellite6. Alternatively you can provision using Satellite6 which would take care of doing all these automatically for you. Detailed explanation below:
Setup/run virt-who server:
- Setup virt-who server and run it once by
virt-who --one-shot. To enable and start it permanently, do # systemctl start virt-who.service
# systemctl enable virt-who.service
- Setup virt-who server and run it once by
Verify that hypervisors are imported to Satellite6:
- If
virt-who --one-shotran with no errors, all your hypervisors would be automatically imported to Satellite6. But the actual vms will not be imported.
- If
Attach Virtual Datacenter Subscription: - Go to Satellite6 Web UI -> Select the hypervisor -> Assign your Virtual Datacenter Subscription - this opens up unlimited subscriptions for all guests for that hypervisor - The unlimited subscriptions can be identified with their subscription type -
Guests of hypervisor_server_1in Satellite6 Web UI -> Content -> Red Hat Subscriptions.Create Activation key for virtual guests
- Go to Satellite6 Web UI -> Content -> Activation keys.
- Create an Activation key with the content you want for the guests.
- Attach the unlimited subscription (name should read similar to
Guests of hypervisor_server_1) corresponding to your hypervisor.
Provision your guest
- Provision a new guest in your hypervisor.
- Register and subscribe the guest to your Satellite using the Activation key created from previous step.
- Review the Satellite6 server to make sure that the new guest is created and it consumes the unlimited subscriptions from its hypervisor.
- Alternatively if you are provisioning using Satellite6, make sure to attach the Activation key to your hostgroup, which makes sure that your guest gets the right subscription.
I got below error when setup virt-who configuration first time, but cannot connect to our VM ESXI 5.5, firewall and user right test successfully, any idea? thanks a lot
2018-08-06 17:33:35,623 [virtwho.main INFO] MainProcess(24882):MainThread @esx.py:logout:366 - Can't log out from ESX: Server raised fault: 'The session is not authenticated.'
2018-08-06 17:33:36,546 [virtwho.rhsm_log WARNING] MainProcess(6969):MainThread @config.py:init_config:1395 - [global]: Value for "oneshot" not set, using default: False 2018-08-06 17:33:36,548 [virtwho.rhsm_log WARNING] MainProcess(6969):MainThread @config.py:init_config:1395 - [global]: Value for "log_per_config" not set, using default: False 2018-08-06 17:33:36,548 [virtwho.rhsm_log WARNING] MainProcess(6969):MainThread @config.py:init_config:1395 - [global]: Value for "print_" not set, using default: False 2018-08-06 17:33:36,548 [virtwho.rhsm_log WARNING] MainProcess(6969):MainThread @config.py:init_config:1395 - [global]: Value for "reporter_id" not set, using default: 2018-08-06 17:33:36,549 [virtwho.rhsm_log WARNING] MainProcess(6969):MainThread @config.py:init_config:1395 - [global]: Value for "log_dir" not set, using default: /var/log/rhsm 2018-08-06 17:33:36,549 [virtwho.rhsm_log WARNING] MainProcess(6969):MainThread @config.py:init_config:1395 - [global]: Value for "background" not set, using default: False 2018-08-06 17:33:36,549 [virtwho.rhsm_log WARNING] MainProcess(6969):MainThread @config.py:init_config:1395 - [global]: Value for "configs" not set, using default: [] 2018-08-06 17:33:36,550 [virtwho.rhsm_log WARNING] MainProcess(6969):MainThread @config.py:init_config:1395 - [global]: Value for "log_file" not set, using default: rhsm.log 2018-08-06 17:33:36,550 [virtwho.rhsm_log WARNING] MainProcess(6969):MainThread @config.py:init_config:1395 - [virt-who-config-1]: Value for "simplified_vim" not set, using default: True 2018-08-06 17:33:36,551 [virtwho.rhsm_log WARNING] MainProcess(6969):MainThread @config.py:init_config:1395 - [virt-who-config-1]: Value for "is_hypervisor" not set, using default: True 2018-08-06 17:33:36,551 [virtwho.rhsm_log DEBUG] MainProcess(6969):MainThread @executor.py:init:52 - Using config named 'virt-who-config-1' 2018-08-06 17:33:36,552 [virtwho.rhsm_log INFO] MainProcess(6969):MainThread @main.py:main:158 - Using configuration "virt-who-config-1" ("esx" mode) 2018-08-06 17:33:36,552 [virtwho.rhsm_log INFO] MainProcess(6969):MainThread @main.py:main:160 - Using reporter_id='dlsatifwh0a-b144cc94a7124fdf97e5644e79463fdc' 2018-08-06 17:33:36,555 [virtwho.main DEBUG] MainProcess(6969):MainThread @executor.py:run:184 - Starting infinite loop with 3600 seconds interval 2018-08-06 17:33:36,570 [rhsm.https DEBUG] MainProcess(6969):MainThread @https.py::56 - Using standard libs to provide httplib and ssl 2018-08-06 17:33:36,591 [virtwho.main DEBUG] MainProcess(6969):Thread-2 @virt.py:run:374 - Thread 'virt-who-config-1' started 2018-08-06 17:33:36,591 [virtwho.main DEBUG] MainProcess(6969):Thread-2 @esx.py:_prepare:129 - Log into ESX 2018-08-06 17:33:36,596 [virtwho.destination_127229156281439283 DEBUG] MainProcess(6969):Thread-3 @virt.py:run:374 - Thread 'destination_127229156281439283' started 2018-08-06 17:33:40,938 [virtwho.main ERROR] MainProcess(6969):Thread-2 @esx.py:login:356 - Unable to login to ESX Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/virtwho/virt/esx/esx.py", line 350, in login password=unicode(self.password, 'utf-8') File "/usr/lib/python2.7/site-packages/suds/client.py", line 542, in call return client.invoke(args, kwargs) File "/usr/lib/python2.7/site-packages/suds/client.py", line 602, in invoke result = self.send(soapenv) File "/usr/lib/python2.7/site-packages/suds/client.py", line 647, in send result = self.succeeded(binding, reply.message) File "/usr/lib/python2.7/site-packages/suds/client.py", line 684, in succeeded reply, result = binding.get_reply(self.method, reply) File "/usr/lib/python2.7/site-packages/suds/bindings/binding.py", line 151, in get_reply self.detect_fault(soapbody) File "/usr/lib/python2.7/site-packages/suds/bindings/binding.py", line 182, in detect_fault raise WebFault(p, fault) WebFault: Server raised fault: 'Permission to perform this operation was denied.' 2018-08-06 17:33:40,941 [virtwho.main ERROR] MainProcess(6969):Thread-2 @virt.py:run:383 - Thread 'virt-who-config-1' fails with error: Server raised fault: 'Permission to perform this operation was denied.' 2018-08-06 17:33:40,942 [virtwho.main INFO] MainProcess(6969):Thread-2 @virt.py:_send_data:922 - Report for config "virt-who-config-1" gathered, placing in datastore 2018-08-06 17:33:40,948 [virtwho.main INFO] MainProcess(6969):Thread-2 @virt.py:run:407 - Waiting 3600 seconds before performing action again 'virt-who-config-1' 2018-08-06 17:33:41,608 [virtwho.destination_127229156281439283 DEBUG] MainProcess(6969):Thread-3 @virt.py:_send_data:599 - ErrorReport received for source: virt-who-config-1
Dan - In this instance I recommend raising a support case with Red Hat. As you already have this set up, we will be able to troubleshoot the installation. That is likely to be the fastest means of getting the issue resolved.
Otherwise, we need more information, including:
- Satellite version (including version of RHEL on which it's installed);
- virt-who version
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
