Plugins » Katello

Hi

Mario K wrote:
...

The logfile /var/log/rhsm/rhsm.log on the virt-who system does not contain any errors. If I stop the virt-who service and do a

virt-who --debug --one-shot

then I can see all ESXi hosts on the output including the ESXi hosts that were added after the Katello update. So virt-who is able to find the new ESXi Hosts. The virt-who command above also tells me that the Report for the config has been sent.

I did have a look in the /var/log/foreman/production.log logfile on the Katello System and found entries
2017-06-30 10:36:33 64adcac0 [app] [I] Started POST "/rhsm/hypervisors?owner=OWNERNAME&env=Library" for 2.3.4.5 at 2017-06-30 10:36:33 +0200
2017-06-30 10:36:33 64adcac0 [app] [I] Processing by Katello::Api::Rhsm::CandlepinProxiesController#hypervisors_update as JSON
2017-06-30 10:36:33 64adcac0 [app] [I] Parameters: ...
2017-06-30 10:36:33 64adcac0 [app] [I] Expire fragment views/tabs_and_title_records-17 (0.1ms)
2017-06-30 10:36:33 64adcac0 [katello/cp_proxy] [I] Authorized user katellovirtwhouser(katellovirtwhouser katellovirtwhouser)
2017-06-30 10:36:36 64adcac0 [app] [I] Completed 200 OK in 2502ms (Views: 0.3ms | ActiveRecord: 186.3ms)

OWNERNAME is my companyname
2.3.4.5 is a placeholder for the IPv4 Adress of the virt-who machine.
katellovirtwhouser is a placeholder for the virt-who User in Katello
... is a placeholder for a long JSON List containting the ESXi hosts and the UUIDs and som other parameters. The ESXi hosts also include the new ESXi Hosts which are not present in the Content Hosts view in Katello.

There is still no error message.

Hi Marek Hulán

Marek Hulán wrote:

It seems the report arrived to Katello just fine. Look at monitor -> tasks if you see something suspicious. Each report creates a task which parses the data. Search for tasks with hypervisor in name and result not success. Following search should do it "label = Actions::Katello::Host::HypervisorsUpdate and result != success"

I found lots of Tasks with the Label Hypervisors. All of them are stopped and have finished successful. But it does not work yet because the content Hosts are not created by these tasks.

Please help me to solve the issue.

sincerely yours

icingauserm

Hi!

A guy on IRC did solve the issue.

The Content Hosts were created but not with the name esxi.domain.tld as I did expect the content host name but with the name virt-who-esxi.domain.tld-1. I found the missing Content Hosts and renamed them to the prefered name.

thanks for the great support

sincerely yours

Mario Koppensteiner

Mario K wrote:

Hi!

I'm using Katello 3.2.2 with Foreman 1.13.4 on an CentOS 7.3 System. I have an VMware vSphere 6.0.0 environment and we using virt-who Version 0.16-8 on an RHEL 6.8 system to report the ESXi Hosts to Katello.

In January 2017 we did update Katello from Version 3.0.0 to Version 3.2.2. Before the update, the virt-who service did create a Content Host for each ESXi Host in Katello. Now I found that all the ESXi hosts that were added to the VMware vSphere Environment after the update of Katello are not in the Content Hosts in Katello.

The logfile /var/log/rhsm/rhsm.log on the virt-who system does not contain any errors. If I stop the virt-who service and do a

virt-who --debug --one-shot

then I can see all ESXi hosts on the output including the ESXi hosts that were added after the Katello update. So virt-who is able to find the new ESXi Hosts. The virt-who command above also tells me that the Report for the config has been sent.

Please help me to identify the issue. If you need more information, then please tell me.

sincerely yours

icingauserm