Public bug reported:
From time to time, I could see that neutron net-external-list was
returning something empty for a non-admin user while this is not true on
my setup.
After quite some debugging, it turned out that it was failing because of
the policy (using the default policy.json, btw):
Public bug reported:
Cleaning up...
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \
${PYTHON:-python} -m subunit.run discover -t ./ ./nova/tests --list
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
Public bug reported:
Running tempest test on devstack (happens also on jenkins gate)
nosetests -sv tempest.api.network.test_load_balancer.py
create_vip failes and returns:
?xml version='1.0' encoding='UTF-8'?
NeutronError xmlns=http://openstack.org/quantum/api/v2.0;
Public bug reported:
2014-02-16 05:18:05.961 TRACE nova raise exception.NoUniqueMatch(msg)
2014-02-16 05:18:05.961 TRACE nova NoUniqueMatch: (uMultiple security groups
found matching '%s'. Use an ID to be more specific., 'sec_group')
2014-02-16 05:18:05.961 TRACE nova
n-cpu failed to start
This code was fixed in
https://github.com/openstack/nova/commit/9b6b874b23dab5ae6ccecae18c5d5664c4951d80
** 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).
** Project changed: neutron = tempest
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1280767
Title:
tempest rest_client _error_checker fails while parsing resoponse
Status in Tempest:
Reviewed: https://review.openstack.org/73838
Committed:
https://git.openstack.org/cgit/openstack/tripleo-image-elements/commit/?id=1d239d5ab571d9fa0244734b2b74ed8460ba7640
Submitter: Jenkins
Branch:master
commit 1d239d5ab571d9fa0244734b2b74ed8460ba7640
Author: Robert Collins
Public bug reported:
In /etc/nova/rootwrap.conf, the following comment contains incorrect
valid values:
# Which syslog facility to use.
# Valid values include auth, authpriv, syslog, user0, user1...
# Default value is 'syslog'
#syslog_log_facility=syslog
The user0, user1 settings are invalid.
** Changed in: tripleo
Status: Fix Released = In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1280692
Title:
old keystone paste configuration embedded in
My two cents: all python bindings should rely on python-keystoneclient
for obtaining token and url from catalogue, rather than duplicating the
logic to get a token and parse the catalogue, like cinder and nova
client do. This will make it easier in future to support new version of
the identity
It is the same bug with Bug #1258379 which has been resolved.
** Changed in: neutron
Status: In Progress = Fix Released
** Changed in: neutron
Status: Fix Released = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: neutron
Assignee: (unassigned) = shihanzhang (shihanzhang)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
** Also affects: cinder
Importance: Undecided
Status: New
** Changed in: cinder
Assignee: (unassigned) = shihanzhang (shihanzhang)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
So we need a new release - this is fixed in:
commit 02baef46968b816ac544b037297273ff6a4e8e1b
but until a new release is done, anyone running trunk Neutron will have
the metadata agent fail.
And neutron itself is missing a versioned dep on the fixed client (but
obviously
Public bug reported:
While creating volume, the return value says that volume creation time
is dd-mm-yyThh:mm:ss.s, but while listing volumes at a later point
of time, it changes to dd-mm-yyThh:mm:ss.0
Doesn't look like a big issue though, but nevertheless shouldn't happen.
I'd say the
Public bug reported:
During upload, if the Auth token is expired, the xenapi glance plugin in Nova
unnecessarily uploads the chunks and fails at the end.
Instead, we could have a fail fast mechanism using the
100-continue handshake. Only if the client receives a 100 continue
from glance, it
** Also affects: taskflow
Importance: Undecided
Status: New
** Also affects: manila
Importance: Undecided
Status: New
** Also affects: murano
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering
Public bug reported:
When the LDAP assignment driver is used and the use_dumb_member
configuration option is enabled, the dumb member is listed when listing
the role assignments. This can be seen by running the live LDAP tests,
as the test_list_role_assignments_unfiltered test will fail due to
18 matches
Mail list logo
