Expanding on that, you get that binding error usually when Neutron thinks
it can't wire up the ports on the compute nodes. So ensure that you started
the appropriate Neutron agents on the new compute nodes and that they are
alive by running 'neutron agent-list'.
On Mon, Feb 20, 2017 at 8:14 AM, Ko
Hi,
this 'Unexpected vif_type=binding_failed’ is as well fairly-generic, but you
can change focus from Nova to Neutron+virtual switch.
So check:
-Neutron server logs
-Logs of Neutron agent on target Compute Host(s)
-OVS logs and possibly things like /var/log/messages for things related to
virtu
Further when i tried and attempt to launch new instance, i can see the
following
tail -f /var/log/nova/nova-compute.log
2017-02-20 12:45:26.596 5365 TRACE nova.compute.manager [instance:
1840ac2e-5a54-4941-a96f-a431b2a2c236] flavor, virt_type)
2017-02-20 12:45:26.596 5365 TRACE nova.compute
Since the error was with scheduling you will want to modify the config for
nova to show verbose output, try to create another instance, and check for
the uuid and/or requestid of the creation attempt in the log -
nova-scheduler.log
I would turn verbose logging off right after you get a failed atte
Well,
I have no idea from this log file. Trying to make nova-compute more
verbose if you dont find anything in the logs
Saverio
2017-02-20 7:50 GMT+01:00 Anwar Durrani :
>
> On Thu, Feb 16, 2017 at 1:44 PM, Saverio Proto wrote:
>>
>> openstack server show uuid
>
>
> Hi Saverio,
>
> I have invest
On Thu, Feb 16, 2017 at 1:44 PM, Saverio Proto wrote:
> openstack server show uuid
Hi Saverio,
I have investigated and progressed the case as per your saying, i got to
know that instance was supposed to be launched on one of the nova node,
where i dig and tried find out log as you mentioned,
The three new compute nodes that you added are empty, so most likely
the new instances are scheduled to those three (3 attempts) and
something goes wrong.
with admin rights do:
openstack server show uuid
this should give you the info about the compute node where the
instance was scheduled. Check
Hi team,
I am running Kilo setup with 1 Controller and 7 nova nodes, i have added 3
additional nova nodes, where i can see, in system information under compute
nodes that nodes are up and running, but when i am trying to launch
instance then it is prompting below error :
*Error: *Failed to perfor
