Hide Forgot
Description of problem: When customer try to provision one new content host, receive the error according below *Query instance details for <satellite hostname> task failed with the following error: Fog::Compute::Vsphere::NotFound* Version-Release number of selected component (if applicable): satellite-6.2.6-2.0.el7sat.noarch How reproducible: 100% on the customer environment Steps to Reproduce: 1. Create new Content Host 2. Define all parameters 3. Submit Actual results: Error message according below * Unable to save Query instance details for <satellite hostname> task failed with the following error: Fog::Compute::Vsphere::NotFound * Expected results: Create the content host Additional info:
I would like to ask for output of this script: cat <<EOF | foreman-rake console require 'pp' Foreman::Model::Vmware.all.each do |cr| service = cr.send(:client); "" pp cr.attributes.except('password') raw_networks = service.list_networks(:datacenter => cr.datacenter) pp raw_networks end;"" EOF This will print information about the compute resources and the available networks.
After analylizing the provided source and additional data, it seems the issue was in applying wrong patch to address https://bugzilla.redhat.com/show_bug.cgi?id=1394290: it seems the patch 'vsphere-unique-networks.patch' was applied, which was later in the original BZ as commented in https://bugzilla.redhat.com/show_bug.cgi?id=1394290#c40, where also the right patch is provided. To fix the issue, I suggest first reverting the original patch and then applying the new one: cd /usr/share/foreman # revert the original patch patch -Rp1 < ~/vsphere-unique-networks.patch # apply new patch patch -p1 < ~/vsphere-dvportgroup-key.patch service httpd restart After doing this, it might be needed to re-save the compute profile used while using the previous patch, but should help with the original issue. In case this doesn't help, please share latest sosreports and fresh tar of `/usr/share/foreman` to see the state of sources after reversing the old patch and applying the new one
Since this issue was caused by applying wrong patch to resolve https://bugzilla.redhat.com/show_bug.cgi?id=1394290, I'm closing this BZ as NOTABUG