I honestly don't see any evidence of some broken behaviour in Nova if,
particularly, other instances with other guest image using cloud-init
can boot correctly.
Please provide us some logs or better trace of a potential Nova problem
in order for us to classify the potential root cause and a
The bug is also present in master.
** Tags added: libvirt low-hanging-fruit
** Changed in: nova
Importance: Undecided => Low
** Changed in: nova
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Could you please tell us which Nova version is corresponding to the
Ubuntu package 1:2015.1.2-0ubuntu2~cloud0 ?
Also, could you please tell us if another request coming in would get
the accurate number of hosts within the Aggregate ? In general, you
don't need to restart the scheduler service,
** Tags removed: race-condition
** Changed in: ubuntu
Status: New => Invalid
** Changed in: nova
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542491
Title:
Not sure I understand your problem. Do you want the configuration file
more explicit ? Please describe exactly what you think is missing, and
what you would like.
Please also change the status back to New if you think you answer to my
question.
** Changed in: nova
Importance: Undecided =
Not sure I understand your problem. Do you want the configuration file
more explicit ? Please describe exactly what you think is missing, and
what you would like.
Please also change the status back to New if you think you answer to my
question.
** Changed in: nova
Importance: Undecided =
Not sure it's Nova related, since the connection is managed by MySQLdb here.
That's all due to the configuration done on SQLA like said in
http://docs.sqlalchemy.org/en/rel_1_0/core/engines.html
Please check your connection option for the nova.conf file as this is
how it's called.
** Changed
Not sure it's Nova related, since the connection is managed by MySQLdb here.
That's all due to the configuration done on SQLA like said in
http://docs.sqlalchemy.org/en/rel_1_0/core/engines.html
Please check your connection option for the nova.conf file as this is
how it's called.
** Changed
