Public bug reported:
According to RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1167496
We need to add support of port-security-enabled=False/True when creating and
updating network.
version :
]# rpm -qa |grep horizon
python-django-horizon-2015.1.0-2.el7.noarch
this flag relevant to port cre
Public bug reported:
1: Exact Version (Latest apt-get dist-upgrade with Kilo repositories for ubuntu
14.04.02)
ii nova-api1:2015.1~rc1-0ubuntu1~cloud0
all OpenStack Compute - API frontend
ii nova-cert 1:2015.1~rc1-0ubuntu1
Public bug reported:
When printing help of neutron net-create / neutron net-update / neutron
port-create / neutron port-update
there is no explanation of new flag : --port_security_enabled.
version:
# rpm -qa |grep neutron
python-neutronclient-2.3.11-1.el7.noarch
openstack-neutron-2015.1.0-
Public bug reported:
According to RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1167496
Port that already created from network with --port_security_enabled=True will
not updated to False when we update network to --port_security_enabled=False.
Version:
# rpm -qa |grep neutron
python-neutronc
Public bug reported:
Latest Kilo code.
In inspect_capabilities() of nova/virt/disk/vfs/guestfs.py, guestfs api,
which is C-extension, will hang nova-compute process when it is invoked.
This problem will result in message queue time out error and instance
booting failure.
And example of this prob
Public bug reported:
Create a vpn service, and using strongswan as its driver or libreswan.
Though the IPsec connection has already established, the status of the
ipsec connection is still in pending_create.
[root@test102 ~]# neutron ipsec-site-connection-list
+---
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs
Public bug reported:
The AZ of an instance is calculated wrong when creating neutron ports.
It uses the requested instance AZ as opposed to the actual AZ of the
instance.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a mem
I'm moving this to the server side, i don't think it is a client issue
because:
1. When you have an id you typically don't use find(), you use get().
Find implies a search by attribute and it returns an array as you will
often have multiple objects that match said attribute. Get is a fetch by
id,
9 matches
Mail list logo
