Public bug reported:
Description
===
I get an error after upgrade half of my cluster. Can't place any VMs.
"RemoteError: Remote error: IncompatibleObjectVersion Version 2.1 of
InstanceList is not supported"
Steps to reproduce
==
1) Install 4 nodes with mitaka
2)
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1628385
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1635627
Reviewed: https://review.openstack.org/384482
Committed:
https://git.openstack.org/cgit/openstack/senlin/commit/?id=8542ba8457d93a14e22f7c7b771d4ac629b77142
Submitter: Jenkins
Branch:master
commit 8542ba8457d93a14e22f7c7b771d4ac629b77142
Author: pallavi
Date:
Reviewed: https://review.openstack.org/389530
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=295175826b393d77c60bd6be739623c147153edc
Submitter: Jenkins
Branch:master
commit 295175826b393d77c60bd6be739623c147153edc
Author: Kenji Ishii
Date:
Reviewed: https://review.openstack.org/390422
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=2fbf3fbdf3da2371219da3bc6509e1b622175f5e
Submitter: Jenkins
Branch:master
commit 2fbf3fbdf3da2371219da3bc6509e1b622175f5e
Author: Kenji Ishii
Date:
upstream lxml bug: https://bugs.launchpad.net/lxml/+bug/1652191
** Changed in: ironic
Status: New => Invalid
** Changed in: nova
Status: New => Invalid
** Summary changed:
- CI jobs failing in devstack/lib/keystone
+ Bad wheel with lxml 3.7.0
** No longer affects: nova
**
Public bug reported:
CI Jobs are failing across OpenStack with an error like this:
http://logs.openstack.org/39/414339/2/check/gate-tempest-dsvm-ironic-
ipa-partition-pxe_snmp-tinyipa-ubuntu-xenial-
nv/1d5e63d/logs/devstacklog.txt.gz#_2016-12-22_22_25_10_787
2016-12-22 22:25:08.714 |
** Also affects: oslo.rootwrap
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/1652157
Title:
privsep configuration is invalid
Status in
Public bug reported:
http://logs.openstack.org/76/414176/6/check/gate-devstack-dsvm-py35
-updown-ubuntu-xenial-
nv/e100b7f/logs/devstacklog.txt.gz#_2016-12-22_19_44_56_941
2016-12-22 19:44:56.941 | 2016-12-22 19:44:56.940 24861 ERROR
neutron.agent.ovsdb.impl_vsctl [-] Unable to execute
Public bug reported:
These are all over the n-cpu logs in master branch CI runs now:
http://logs.openstack.org/75/405575/6/check/gate-tempest-dsvm-neutron-
full-ubuntu-
xenial/e1c5575/logs/screen-n-cpu.txt.gz?level=TRACE#_2016-12-22_16_52_19_551
2016-12-22 16:52:19.551 7348 WARNING
Public bug reported:
We've seen this functional test failing in the gate [0] and it's due to
a bug in the helper module that was written for the functional test. [1]
The problem shows up when process_spawn is not able to find a port to
listen on and the process stays running anyways. That means
Public bug reported:
While trying to debug some failures in an Ironic job, there are a lot of
inventory update warnings in the n-cpu logs for the placement service:
http://logs.openstack.org/39/404239/14/check/gate-tempest-dsvm-ironic-
ipa-wholedisk-pxe_snmp-tinyipa-ubuntu-xenial-
@Nova team: please have look at the issue, request stuck at nova compute
and didn't get to ironic.
** Description changed:
Ironic gate jobs are randomly timing out during last few weeks. Nothing
strange in the logs, just receives slow VMs:
-
- An example is:
Public bug reported:
When switching an ovs-agent from iptables to ovsfw, new instances will
be created using the ovsfw, but old instances will stick with iptables.
In fact, there isn't a way to migrate an instance from iptables to
ovsfw, and one should be provided.
Considerations:
a. It isn't
Public bug reported:
Our token model code will return a default of True for is_admin_project
if that attribute is not defined. The comment next to this says this is
for backward compatibility - but this seems inherently dangerous. We
should investigate what changes are needed (if any) to make the
Public bug reported:
The new capability of is_admin_project is currently only supported for
projects. However, the existing code for token models will return
is_admin_project as True if the attribute has not been set. Hence admin
domain tokens might get interpreted as cloud admin tokens. This is
17 matches
Mail list logo