Public bug reported:
when this flag is disbaled in nova.conf "allow_duplicate_networks=false"
allocating the port from the same network is failing with the following
error.
$ nova boot --image cirros --flavor 1 --nic net-id=`neutron net-list | grep
internal | awk {'print $2'}` --nic net-id=`neu
Public bug reported:
If networking-foo depends on networking-bar, then a requirement may
arise for an alembic revision in networking-foo to depend on an alembic
revision in networking-bar. Currently this cannot be accommodated
because each subproject has its own alembic environment.
To solve this
Public bug reported:
The LBaaS V2 Octavia driver currently uses the context that is passed
from the plugin. Since the driver spins up a thread to poll Octavia,
each thread should create its own context.
** Affects: neutron
Importance: Undecided
Assignee: Brandon Logan (brandon-logan)
** Project changed: puppet-nova => nova
--
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/1497689
Title:
Flavor Resource Limit Disk IO do not create limit entry in
libvi
You have been subscribed to a public bug:
Openstack KILO, Cinder with Ceph backend
When i add IOPS, Read,Write limit metada to flavor. The instances that was
created from that Flavor do not have limit record in libvirt.xml
Network and CPU still work. So that the instances have maximum diskIO
pe
Post-Kilo Cinder uses os-brick. Since this fix went in to os-brick and
was released with version 0.4.0, Cinder now should work as of the
requirements update to that library version in commit
e50576c2d495e6828f335029e713655c27a6fc5b.
** Changed in: cinder
Status: New => Invalid
--
You rece
Public bug reported:
Version of Nova/OpenStack: liberty
Calls to associate a floating IP with an instance currently returns a
202 status. When proxying these calls to neutron, just returning 202
without having validated the status of the floating IP first leads to
raceful failures in tempest sce
Rolled into blueprint: https://blueprints.launchpad.net/horizon/+spec
/drop-dj17
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.laun
Public bug reported:
When attempting to connect multiple security groups to a single port
concurrently, some of the security groups may not actually get connected
despite the call returning successfully and with no error.
see similar bug but when connecting the security-groups to a server
rather
9 matches
Mail list logo
