Public bug reported:
Description
===
Bulk boot multi instances in a short time, if the amount of resources required
is not the same,
and the number of resources owned by the compute node is also different, there
maybe a KeyError
in nova-scheduler.log .
Steps to reproduce
===
Public bug reported:
Description
===
On compute node,if system time changed by NTP or using cmd "date -s",change
time from 14:00:00 to 12:00:00 for example,the nova-compute service will stop
reporting state to controller. Then nova service-list show the nova-compute
service will be down
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1257875
Title:
nova-network (devstack) network connections to launched i
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1263338
Title:
neutron (devstack) network connections to launched instances fail
Stat
Invalid. QEMU and KVM only support 2GB of memory on a 32-bit host. This
is the reason the instance doesnt launch.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
Public bug reported:
When setting 'scheduler_default_filters = AllHostsFilter' in nova.conf
on devstack, the default filters (like 'RamFilter') are still used.
Steps to reproduce:
./stack.sh
export OS_USERNAME=admin
export OS_PASSWORD=password
export OS_TENANT_NAME=demo
export OS_AUTH_URL=http
Public bug reported:
When running devstack, I run into the issue where I can successfully
launch an instance, but cannot connect to it, not even from the host
running devstack. The error is either " Destination Host Unreachable"
(when using ping) or "No route to host" (when using ssh).
Steps to r
7 matches
Mail list logo
