OpenStack Cinder-backup Charm

cinder-backup charm func test failing w/ volume creation error

Bug #1796171 reported by Ryan Beisner on 2018-10-04

This bug report is a duplicate of: Bug #1798917: [SRU] Cinder backup of a volume is in error state with fail_reason: data must be bytes. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Cinder-backup Charm	New	High	Unassigned	OpenStack Cinder-backup Charm 18.11

Bug Description

cinder-backup charm func test is failing on volume creation error

test_410_cinder_vol_create_backup_delete_restore_pool_inspect DEBUG: Checking ceph cinder pool original samples...
DEBUG:runner:2018-10-04 09:22:02,980 get_ceph_pool_sample DEBUG: Ceph cinder-ceph pool (ID 1): 2 objects, 1 kb used
DEBUG:runner:2018-10-04 09:22:02,981 create_cinder_volume DEBUG: Creating cinder volume...
DEBUG:runner:2018-10-04 09:22:03,380 resource_reaches_status DEBUG: Volume status wait status check: 0 [creating:available] 48c1b06c-4b65-4ca7-9acb-1d3c25573efc
DEBUG:runner:2018-10-04 09:22:07,499 resource_reaches_status DEBUG: Volume status wait: expected, actual status = available, available
DEBUG:runner:2018-10-04 09:22:07,503 create_cinder_volume DEBUG: Validating volume attributes...
DEBUG:runner:2018-10-04 09:22:08,035 create_cinder_volume DEBUG: Volume attributes - name:demo-vol id:48c1b06c-4b65-4ca7-9acb-1d3c25573efc stat:available boot:false size:1
DEBUG:runner:2018-10-04 09:22:08,349 resource_reaches_status DEBUG: Backup status wait status check: 0 [creating:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:22:12,398 resource_reaches_status DEBUG: Backup status wait status check: 1 [creating:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:22:16,471 resource_reaches_status DEBUG: Backup status wait status check: 2 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:22:20,526 resource_reaches_status DEBUG: Backup status wait status check: 3 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:22:24,582 resource_reaches_status DEBUG: Backup status wait status check: 4 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:22:28,630 resource_reaches_status DEBUG: Backup status wait status check: 5 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:22:32,698 resource_reaches_status DEBUG: Backup status wait status check: 6 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:22:36,749 resource_reaches_status DEBUG: Backup status wait status check: 7 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:22:40,805 resource_reaches_status DEBUG: Backup status wait status check: 8 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:22:44,878 resource_reaches_status DEBUG: Backup status wait status check: 9 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:22:48,929 resource_reaches_status DEBUG: Backup status wait status check: 10 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:22:53,013 resource_reaches_status DEBUG: Backup status wait status check: 11 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:22:57,068 resource_reaches_status DEBUG: Backup status wait status check: 12 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:23:01,131 resource_reaches_status DEBUG: Backup status wait status check: 13 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:23:05,190 resource_reaches_status DEBUG: Backup status wait status check: 14 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:23:09,253 resource_reaches_status DEBUG: Backup status wait status check: 15 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:23:13,305 resource_reaches_status DEBUG: Backup status wait status check: 16 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:23:17,368 resource_reaches_status DEBUG: Backup status wait status check: 17 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:23:21,564 resource_reaches_status DEBUG: Backup status wait status check: 18 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:23:25,630 resource_reaches_status DEBUG: Backup status wait status check: 19 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:23:29,693 resource_reaches_status DEBUG: Backup status wait status check: 20 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:23:33,758 resource_reaches_status DEBUG: Backup status wait status check: 21 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:23:37,819 resource_reaches_status DEBUG: Backup status wait status check: 22 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:23:41,879 resource_reaches_status DEBUG: Backup status wait status check: 23 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:23:45,930 resource_reaches_status DEBUG: Backup status wait status check: 24 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:23:49,987 resource_reaches_status DEBUG: Backup status wait status check: 25 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:23:54,064 resource_reaches_status DEBUG: Backup status wait status check: 26 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:23:58,124 resource_reaches_status DEBUG: Backup status wait status check: 27 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:24:02,306 resource_reaches_status DEBUG: Backup status wait status check: 28 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:24:06,362 resource_reaches_status DEBUG: Backup status wait status check: 29 [error:available] a95333f6-85c3-47c5-a56a-26604487a382
DEBUG:runner:2018-10-04 09:24:10,425 resource_reaches_status DEBUG: Backup status wait: expected, actual status = error, available
DEBUG:runner:2018-10-04 09:24:10,429 resource_reaches_status DEBUG: a95333f6-85c3-47c5-a56a-26604487a382 never reached expected status: available
DEBUG:runner:Cinder backup failed to reach expected state.
DEBUG:runner:Exit Code: 1

https://openstack-ci-reports.ubuntu.com/artifacts/test_charm_pipeline/openstack/charm-cinder-backup/607641/1/6227/consoleText.test_charm_amulet_smoke_8059.txt

See original description

Tags:

Ryan Beisner (1chb1n) on 2018-10-04

Changed in charm-cinder-backup:
milestone:	none → 18.11
importance:	Undecided → High
summary:	- cinder-backup charm func test failing w/ errorred volume creation + cinder-backup charm func test failing w/ volume creation error
description:	updated

Revision history for this message

Liam Young (gnuoy) wrote on 2018-10-05:

This looks like a bug in cinder. Bug #1777397 looks very similar.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #1798917 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.