yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #30897
[Bug 1439273] [NEW] check-tempest-dsvm-full-ceph failing on test_volume_boot_pattern scenario after 3/30
Public bug reported:
https://review.openstack.org/#/c/165616/ enabled the
test_volume_boot_pattern scenario test in tempest on 3/30 after this
change to devstack https://review.openstack.org/#/c/165281/ for the
underlying lvm lockup bug.
Once the test was enabled again, the check-tempest-dsvm-full-ceph job
started failing hard again:
http://logstash.openstack.org/#eyJzZWFyY2giOiJidWlsZF9uYW1lOlwiY2hlY2stdGVtcGVzdC1kc3ZtLWZ1bGwtY2VwaFwiIG1lc3NhZ2U6XCJ0ZXN0X3ZvbHVtZV9ib290X3BhdHRlcm5cIiBBTkQgbWVzc2FnZTpcIkZBSUxFRFwiIEFORCB0YWdzOlwiY29uc29sZVwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDI3OTAxODkzODUyfQ==
There are errors in the n-cpu and g-api logs:
http://logs.openstack.org/53/169753/2/check/check-tempest-dsvm-full-
ceph/07dcae0/logs/screen-n-cpu.txt.gz?level=TRACE
http://logs.openstack.org/53/169753/2/check/check-tempest-dsvm-full-
ceph/07dcae0/logs/screen-g-api.txt.gz?level=TRACE
The n-cpu failures might be red herrings on a failed teardown of the
instance b/c it didn't setup correctly given the g-api errors where it
can't find the image.
Note that nova/cinder/glance are all configured in this job to use
rbd/ceph backends.
** Affects: glance
Importance: Undecided
Status: New
** Affects: nova
Importance: Undecided
Status: New
** Tags: ceph
** Also affects: glance
Importance: Undecided
Status: New
** Tags added: ceph
--
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/1439273
Title:
check-tempest-dsvm-full-ceph failing on test_volume_boot_pattern
scenario after 3/30
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Status in OpenStack Compute (Nova):
New
Bug description:
https://review.openstack.org/#/c/165616/ enabled the
test_volume_boot_pattern scenario test in tempest on 3/30 after this
change to devstack https://review.openstack.org/#/c/165281/ for the
underlying lvm lockup bug.
Once the test was enabled again, the check-tempest-dsvm-full-ceph job
started failing hard again:
http://logstash.openstack.org/#eyJzZWFyY2giOiJidWlsZF9uYW1lOlwiY2hlY2stdGVtcGVzdC1kc3ZtLWZ1bGwtY2VwaFwiIG1lc3NhZ2U6XCJ0ZXN0X3ZvbHVtZV9ib290X3BhdHRlcm5cIiBBTkQgbWVzc2FnZTpcIkZBSUxFRFwiIEFORCB0YWdzOlwiY29uc29sZVwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDI3OTAxODkzODUyfQ==
There are errors in the n-cpu and g-api logs:
http://logs.openstack.org/53/169753/2/check/check-tempest-dsvm-full-
ceph/07dcae0/logs/screen-n-cpu.txt.gz?level=TRACE
http://logs.openstack.org/53/169753/2/check/check-tempest-dsvm-full-
ceph/07dcae0/logs/screen-g-api.txt.gz?level=TRACE
The n-cpu failures might be red herrings on a failed teardown of the
instance b/c it didn't setup correctly given the g-api errors where it
can't find the image.
Note that nova/cinder/glance are all configured in this job to use
rbd/ceph backends.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1439273/+subscriptions
Follow ups
References