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,
Another question is what type of SSD's are you using. There is a big
difference between not just vendors of SSD's but the size of them as their
internals make a big difference on how the OS interacts with them.
This link is still very usage today:
https://www.sebastien-han.fr/blog/2014/10/10/ceph
