if you look into http://logs.openstack.org/48/59948/4/check/check-
tempest-dsvm-neutron-pg-isolated/dab4997/logs/screen-q-lbaas.txt.gz will
see some tracebacks, it's probably an error in neutron.
Note that I get it from http://logs.openstack.org/48/59948/4/check
/check-tempest-dsvm-neutron-pg-isol
** Project changed: tempest => 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/1270470
Title:
nova.servicegroup.drivers.db error in n-cpu log after successful
temp
** Project changed: tempest => 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/1270384
Title:
threadgroup error in n-cond logs after successful tempest run
Status i
** Changed in: nova
Status: Confirmed => Invalid
** Changed in: nova
Importance: Low => Undecided
** Changed in: nova
Assignee: Giampaolo Lauria (lauria) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
Two points to 'won't fix':
- Currently createserverext doesn't add any functionality to the API.
- Due to the first point this api entry point will probably be removed on nova
APIv3
So no need to worry about it's api samples.
** Changed in: nova
Status: Confirmed => Won't Fix
--
You rec
*** This bug is a duplicate of bug 1182754 ***
https://bugs.launchpad.net/bugs/1182754
** This bug is no longer a duplicate of bug 1182164
IP tests fail with "Got compute fault"
** This bug has been marked a duplicate of bug 1182754
Tempest fails against wrong data types when using postg
Marking as invalid since we didn't port that action to start using os-
servers-password
** Changed in: nova
Status: Confirmed => Invalid
** Changed in: nova
Importance: Medium => Undecided
** Changed in: nova
Assignee: Mauro Sergio Martins Rodrigues (maurosr) =&g
This is unit test not tempest' tests.
** Changed in: tempest
Status: New => Invalid
** 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)
** Changed in: tempest
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.launchpad.net/bugs/1319023
Title:
TestDashboardBasicOps.test_basic_scenario fails
Considering lianhao-lu's logs I dive into n-cpu logs and this called my
attention:
2014-07-31 07:52:42.023 25463 WARNING nova.compute.manager [-]
[instance: 1300d7c9-d35d-46ef-a680-bf295cfdef01] Instance shutdown by
itself. Calling the stop API. (at
http://logs.openstack.org/89/108389/2/check/chec
The underlying reason seems to be on glance's side:
http://logs.openstack.org/79/103379/2/check/check-tempest-dsvm-full/9983737/logs/screen-g-reg.txt.gz#_2014-07-06_18_26_04_913
specifically:
2014-07-06 18:26:04.913 24609 TRACE glance.registry.api.v1.images DBDeadlock:
(OperationalError) (1213, '
** Changed in: tempest
Status: New => Invalid
--
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/1371298
Title:
libvirt: AMI-based Linux instances /dev/console unusab
I can't point out what is causing this, anyway, there are several tracebacks
available in
http://logs.openstack.org/98/81098/2/check/check-tempest-dsvm-neutron-pg/df24b97/logs/screen-q-lbaas.txt.gz
seems to me that one of the ballancers had a problem, although it passed
the connection check, so m
Thanks for your investigation!
Can you provide more information about your setup? And the logs of your
run?
So currently I have no deploy with multiple nodes, so I ask: does it
happen all the time?
** Changed in: tempest
Status: New => Incomplete
** Also affects: nova
Importance: Un
** Changed in: tempest
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1262529
Title:
Floating IP takes too long to update in nova and even longer for
does it still happen?
adding neutron to affected projects.
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: tempest
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
*** This bug is a duplicate of bug 1252177 ***
https://bugs.launchpad.net/bugs/1252177
** This bug has been marked a duplicate of bug 1252177
The argument availability_zone of create aggregate should be optional
--
You received this bug notification because you are a member of Yahoo!
Engi
17 matches
Mail list logo