I had a Forman 1.7 server setup previously and provisioning fine, but the
katello side was pretty broken so I pushed the upgrade to the most recent
stable releases of both Katello and Foreman (1.8.2). Upon doing this
provisioning virtual machines on our Vmware clusters is failing with a
"Could not find virtual interface matching IP blah" error.
The setup I use is I have one Vlan (vlan 99) that has DHCP and is used for
provisioning, and another interface setup for the server network. When
provisioning is complete, I remove vlan 99 and continue on with the server.
If I set this up in foreman 1.8 though, I can see the VM created and the 2
interface created on the VMware side, but it it immediately torn down with
the error above referencing the IP address on the primary interface.
I am setting up both interfaces as managed, I have tried adding in a device
ID (both ethX and emX), assign the subnet, put an IP address on the
primary, but leave the provisioning IP empty since that network is DHCP,
and set a DNS name, but the error stays the same. I'm not really sure
where to go from here since it was working previously.
I just uploaded a foreman-debug file on this to provide a bit more
information on the issue if that helps anyone out
···
On Thursday, June 25, 2015 at 2:35:09 AM UTC-5, Seth Doty wrote:
>
> I had a Forman 1.7 server setup previously and provisioning fine, but the
> katello side was pretty broken so I pushed the upgrade to the most recent
> stable releases of both Katello and Foreman (1.8.2). Upon doing this
> provisioning virtual machines on our Vmware clusters is failing with a
> "Could not find virtual interface matching IP blah" error.
>
> The setup I use is I have one Vlan (vlan 99) that has DHCP and is used for
> provisioning, and another interface setup for the server network. When
> provisioning is complete, I remove vlan 99 and continue on with the server.
> If I set this up in foreman 1.8 though, I can see the VM created and the 2
> interface created on the VMware side, but it it immediately torn down with
> the error above referencing the IP address on the primary interface.
>
> I am setting up both interfaces as managed, I have tried adding in a
> device ID (both ethX and emX), assign the subnet, put an IP address on the
> primary, but leave the provisioning IP empty since that network is DHCP,
> and set a DNS name, but the error stays the same. I'm not really sure
> where to go from here since it was working previously.
>
> Any assistance on this would be appreciated.
>
> Thanks
>
Nope, I set the DNS name, domain, subnet, IP address for the primary
interface only. I then check Managed, Primary/provision, the nic type
(vmxnet) and appropriate network from vmware. I have also tried setting
the identifier (eth0 for instance), but the failure is the same.
···
On Wednesday, July 1, 2015 at 5:03:00 AM UTC-5, Lukas Zapletal wrote:
>
> > provisioning virtual machines on our Vmware clusters is failing with a
> > "Could not find virtual interface matching IP blah" error.
>
> Shooting in the dark, are the interfaces flagged with "Virtual"
> checkbox?
>
> --
> Later,
> Lukas #lzap Zapletal
>
