** Changed in: cirros
Status: Invalid => Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1459042
Title:
cloud-init fails to report IPv6 connectivity when booting
Public bug reported:
A floating IP can only be associated with an IPv4 address, trying to use
an IPv6 address leads to an error like this:
Error: Bad floatingip request: Cannot process floating IP association
with fdb7:6005:3c07:0:f816:3eff:fe94:35d4, since that is not an IPv4
address. Neutron se
Public bug reported:
When running an instance on a network with ipv6-address-mode
dhcpv6-stateful, the instance fails to receive responses from the DHCP
server. The workaround is to add an explicit security group rule
allowing
--proto udp --dst-port 546 --ethertype IPv6
and then the DHCP handsha
Public bug reported:
When deleting an instance from the detail page for that instance, the
popup says
"You have selected: . Please confirm your selection. Deleted instances
are not recoverable."
Same behaviour for stable/ocata and current master.
Expected behaviour: Show the name of the instanc
Public bug reported:
This is a regression for Ocata, things are working fine for Newton. But
if I create a IPv6 subnet in Ocata, the DHCP namespace gets configured
with an IPv6 address, but is lacking a default route, so dnsmasq fails
to resolv any DNS queries except for the local OpenStack instan
** Changed in: nova/newton
Status: Fix Committed => Fix Released
--
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/1660682
Title:
resource tracker sets wrong initial
Public bug reported:
There are two issues affecting the useability of the network information
presented to an instance via the metadata API:
1. For networks using DHCP, the IP address information is omitted. There
are however use cases where an instance would want to use static address
configurat
Turns out that the default glance-api.conf file is misleading, it is
showing:
[paste_deploy]
#flavor = keystone
implying that "keystone" is the default value for paste_deploy.flavor,
but in fact it is None.
** Changed in: openstack-manuals
Status: New => Invalid
** Also affects: glance
** Changed in: python-openstackclient
Status: In Progress => Fix Released
** Changed in: python-openstacksdk
Assignee: Dr. Jens Rosenboom (j-rosenboom-j) => (unassigned)
** Changed in: python-openstackclient
Assignee: Dr. Jens Rosenboom (j-rosenboom-j) => (unassigned)
** Changed in: python-openstacksdk
Status: In Progress => Fix Released
** Changed in: neutron
Assignee: Dr. Jens Rosenboom (j-rosenboom-j) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
This bug tracker is for errors with the documentation, use the following
as a template and remove or add fields as you see fit. Convert [ ] into
[x] to check boxes:
- [X] This doc is inaccurate in this way: __see below
- [ ] This is a doc addition request.
- [ ] I have a
** Changed in: python-openstackclient
Status: Invalid => In Progress
** Changed in: python-openstackclient
Assignee: (unassigned) => Dr. Jens Rosenboom (j-rosenboom-j)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscri
The attribute is also missing in the Neutron api-ref at
https://developer.openstack.org/api-ref/networking/v2/?expanded=create-
subnet-detail
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: python-openstackclient
Assignee: Dr. Jens Rosenboom (j-rosenboom
This issue is still present for Horizon in Newton, any chance to
backport the Horizon fixes there?
To reproduce:
- Install devstack from stable/newton
- Run stack.sh
- sudo -H pip install -U python-openstackclient
- sudo systemctl restart apache2
=> All nova related tabs like Admin/Flavors log o
*** This bug is a duplicate of bug 1654183 ***
https://bugs.launchpad.net/bugs/1654183
So it turns out that this is another duplicate of 1654183, fixed in
python-novaclient git master currently.
For the Chef deployment, there was a global pip based python-
openstackclient installation that un
Thanks for the hint Mike, I must admit that I never looked at that. In
fact it seems like this would be fixed already in spice-html5-0.1.5
dated more than two years ago, but Ubuntu still ships 0.1.4.
** Also affects: spice-html5 (Ubuntu)
Importance: Undecided
Status: New
--
You receive
Public bug reported:
After installing neutron on Ubuntu Xenial from the Newton UCA
(2:9.0.0-0ubuntu1.16.10.2~cloud0), I noticed these processes:
neutron 11222 2.9 0.8 262628 108712 ? Ss 10:59 1:36
/usr/bin/python /usr/bin/neutron-openvswitch-agent
--config-file=/etc/neutron/neutron
We get the same issue when deploying Newton via Ubuntu UCA. Affected
package versions are:
python-openssl=16.1.0-1~cloud0
python-cryptography=1.5-2~cloud0
The error goes away if similar to the Ansible workaround we downgrade to
the packages from Xenial:
python-openssl=0.15.1-2build1
python-crypt
Public bug reported:
Introduce a new type of action in RBAC for use with QoS (and potentially
useful for other stuff),
The action would be default:
neutron rbac-create --type qos-policy --target-tenant
--action default
That would mean:
Any created network for that tenant would be assigned
54 hits in the last 7 days. Checked a couple and they all have an error
like this:
http://logs.openstack.org/96/384696/1/check/gate-tempest-dsvm-neutron-
placement-full-ubuntu-xenial-
nv/c19ea11/logs/screen-q-svc.txt.gz?level=ERROR#_2016-10-10_20_45_30_546
/usr/local/lib/python2.7/dist-packages/s
** Changed in: nova
Status: In Progress => Invalid
** Changed in: nova
Assignee: Dr. Jens Rosenboom (j-rosenboom-j) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
After upgrading keystone from mitaka to newton-rc1 on Xenial I am
getting this error:
$ keystone-manage db_sync
Traceback (most recent call last):
File "/usr/bin/keystone-manage", line 6, in
from keystone.cmd.manage import main
File "/usr/lib/python2.7/dist-packages
Public bug reported:
The error looks like this:
STDERR: INFO [alembic.runtime.migration] Context impl MySQLImpl.
INFO [alembic.runtime.migration] Will assume non-transactional DDL.
Traceback (most recent call last):
File "/usr/bin/neutron-db-manage", line 10, in
sys.exit(main())
File "
nassigned) => Dr. Jens Rosenboom (j-rosenboom-j)
--
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/1622684
Title:
Keycode error using novnc and Horizon console
Status in
** Also affects: nova
Importance: Undecided
Status: New
--
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/1622684
Title:
Keycode error using novnc and Horizon con
*** This bug is a duplicate of bug 1622684 ***
https://bugs.launchpad.net/bugs/1622684
** This bug is no longer a duplicate of bug 1621257
VNC console keeps reporting "setkeycodes 00" exception
** This bug has been marked a duplicate of bug 1622684
Keycode error using novnc and Horizon c
Gah, forgot there is a knob that needs turning in order to enable this.
Might be worth considering changing the default for this nowadays.
** Changed in: nova
Status: New => Invalid
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are
Public bug reported:
Steps to reproduce:
- Set up devstack with default settings from master
- Start an instance using e.g. the default cirros-0.3.4 image
- The instance will receive both an IPv4 and IPv6 address, but this isn't shown
in the metadata, either on the configdrive or via http:
stac
The output in question comes from cloud-init, so added that package.
After doing a bit of debugging, there seem to be two issues here:
1. The output is created too early when the IPv6 network is using slaac,
so this means that there is no IPv6 address listed because it takes a
bit longer to show u
** Changed in: nova/mitaka
Status: Fix Committed => Fix Released
--
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/1576713
Title:
Network metadata fails to state cor
CONFIRMED FOR: MITAKA
** Changed in: nova
Status: Expired => New
--
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/1387812
Title:
Hypervisor summary shows incorrect
va/.tox/py35/lib/python3.5/site-packages/testtools/testcase.py",
line 411, in assertEqual'
b'self.assertThat(observed, matcher, message)'
b' File
"/home/ubuntu/src/nova/.tox/py35/lib/python3.5/site-packages/testtools/testcase.py",
line 498, in assertThat&#
Public bug reported:
At http://docs.openstack.org/developer/keystone/configuration.html
#cache-configuration-section there is a recommendation to use
backend = keystone.cache.memcache_pool
however this seems to be deprecated in the code:
WARNING oslo_log.versionutils [-] Deprecated:
keystone.ca
Public bug reported:
My goal is to achieve an MTU of 1500 for both Vlan and Vxlan based
tenant networks.
So I set the path_mtu to 1550, while leaving global_physnet_mtu at the
default value of 1500.
However, the MTU for my Vxlan networks is still calculated as 1450,
because the underlying MTU is
Public bug reported:
If I run devstack with
enable_plugin neutron-lbaas https://github.com/openstack/neutron-lbaas.git
ENABLED_SERVICES+=,q-lbaasv1
then the service gets configured, but not started. Using
ENABLED_SERVICES+=,q-lbaas
instead works fine. The reason is that neutron-lbaas/devstack/
Public bug reported:
When booting an instance on a network with encapsulation type vxlan (and
thus automatically set MTU to 1450), this will also lower the MTU of the
integration bridge to that value:
$ ip link show br-int
6: br-int: mtu 1450 qdisc noqueue state UNKNOWN mode
DEFAULT group defau
** Changed in: neutron
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1532171
Title:
lb: hard reboot or destroy of vm can lead to error log a
It seems that this is mainly a bug in how keepalived handles an empty or
otherwise broken pid file. According to the upstream change log, the
issue has been fixed in 1.2.20.
@Ubuntu: Can you look into updating the package or backporting the fix?
** Also affects: keepalived (Ubuntu)
Importance:
Public bug reported:
After a crash of a network node, we were left with empty PID files for
some keepalived processes:
root@network-node14:~# ls -l
/var/lib/neutron/ha_confs/0ab5f647-1e04-4345-ae9b-ee66c6f08882.pid
-rw-r--r-- 1 root root 0 May 19 08:41
/var/lib/neutron/ha_confs/0ab5f647-1e04-4
Public bug reported:
Scenario:
Instance is booted on Neutron tenant network with ML2 OVS driver and
encapsulation. The MTU for that network is automatically calculated as
1450. Instance has --config-drive=true set.
Result:
In /openstack/latest/network_data.json we get:
"links": [{"ethernet_ma
Public bug reported:
Currently there is a limit hardcoded in Neutron that will only allow
16bit ASN being used in the configuration of BGP speakers and peers,
i.e. a range of [1..65535]. But with https://tools.ietf.org/html/rfc6793
it is possible for BGP implementations to allow 32bit numbers to b
7
** Affects: nova
Importance: Undecided
Assignee: Dr. Jens Rosenboom (j-rosenboom-j)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Dr. Jens Rosenboom (j-rosenboom-j)
--
You received this bug notification because you are a member of Yahoo!
En
** Also affects: python-neutronclient
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1513894
Title:
Discrepancy between API and CLI on how to
Gah, turns out that chef installed a file /etc/neutron/dnsmasq.conf
containing
+dhcp-option=26,1454
which overrides all other options. Sorry to the Neutron folks for the
false alarm, I'll go and fix our cookbook.
** Changed in: neutron
Status: In Progress => Invalid
--
You received this
Public bug reported:
When creating a tenant network with type vxlan, the MTU is automatically
set to 1450:
# neutron net-show net2
+---+--+
| Field | Value|
+---
Public bug reported:
As an operator, when I am running a setup with two network nodes, the
idea of running L3 HA is that an outage of one of the network nodes
should have minimum customer impact. With the current code, existing
setups will indeed have little to no impact, but customers will not be
Nova stable/juno is still affected by this issue, since the fix is not
available there currently due to the version cap on python-glanceclient.
** Also affects: nova
Importance: Undecided
Status: New
** Also affects: cinder
Importance: Undecided
Status: New
--
You received t
Public bug reported:
This only affects stable/juno and stable/icehouse, which still use the
deprecated eventlet.util module:
~# nova-manage service list
2015-01-05 13:13:11.202 29016 ERROR stevedore.extension [-] Could not load
'file': cannot import name util
2015-01-05 13:13:11.202 29016 ERROR
*** This bug is a duplicate of bug 1335999 ***
https://bugs.launchpad.net/bugs/1335999
** This bug has been marked a duplicate of bug 1335999
live migration choosing wrong host names
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscr
Public bug reported:
The quickstart document
http://docs.openstack.org/developer/sahara/devref/quickstart.html uses
$SAHARA_URL without defining it. From looking at what the cli client
does, it should be set to:
SAHARA_URL=http://127.0.0.1:8386/v1.0/$TENANT_ID
and the installation for me seems t
Public bug reported:
This happens when booting an instance while nova has ceph backend
enabled:
Oct 31 14:06:59 vagrant-ubuntu-trusty-64 kernel: [ 8264.770442] type=1400
audit(1414764419.818:29): apparmor="DENIED" operation="open"
profile="libvirt-1550f42a-1b8b-4db5-9458-d5b9f496cc0c" name="/tm
Public bug reported:
In the installation guide at http://docs.openstack.org/juno/install-
guide/install/apt/content/glance-install.html section 3.c asks for
[glance-store] parameters to be added to /etc/glance/glance-
registry.conf. These really belong to glance-api.conf however, i.e. that
should
52 matches
Mail list logo
