Also seeing this on the customer deployment (bionic/ussuri). 'opentstack volume backup create' of is stuck in 'creating' state (using the current revision of cinder-backup charm):
$ openstack volume backup show 02e77e70-c502-4de9-8487-7aa1b42e4a98 +-----------------------+--------------------------------------+ | Field | Value | +-----------------------+--------------------------------------+ | availability_zone | None | | container | None | | created_at | 2020-10-08T17:10:11.000000 | | data_timestamp | 2020-10-08T17:10:11.000000 | | description | None | | fail_reason | None | | has_dependent_backups | False | | id | 02e77e70-c502-4de9-8487-7aa1b42e4a98 | | is_incremental | False | | name | test-volume-2-backup | | object_count | 0 | | size | 6 | | snapshot_id | None | | status | creating | | updated_at | 2020-10-08T17:10:11.000000 | | volume_id | 96f2d720-e6cb-46af-8b64-cf8d69aafcef | +-----------------------+--------------------------------------+ ubuntu@infra1:~/deployment/cpe-deployments$ date Thu Oct 8 23:03:32 UTC 2020
It's definitely not the timeout.
Also seeing this on the customer deployment (bionic/ussuri). 'opentstack volume backup create' of is stuck in 'creating' state (using the current revision of cinder-backup charm):
$ openstack volume backup show 02e77e70- c502-4de9- 8487-7aa1b42e4a 98 ------- ------- ---+--- ------- ------- ------- ------- ------- + ------- ------- ---+--- ------- ------- ------- ------- ------- + 08T17:10: 11.000000 | 08T17:10: 11.000000 | backups | False | c502-4de9- 8487-7aa1b42e4a 98 | 2-backup | 08T17:10: 11.000000 | e6cb-46af- 8b64-cf8d69aafc ef | ------- ------- ---+--- ------- ------- ------- ------- ------- + infra1: ~/deployment/ cpe-deployments $ date
+------
| Field | Value |
+------
| availability_zone | None |
| container | None |
| created_at | 2020-10-
| data_timestamp | 2020-10-
| description | None |
| fail_reason | None |
| has_dependent_
| id | 02e77e70-
| is_incremental | False |
| name | test-volume-
| object_count | 0 |
| size | 6 |
| snapshot_id | None |
| status | creating |
| updated_at | 2020-10-
| volume_id | 96f2d720-
+------
ubuntu@
Thu Oct 8 23:03:32 UTC 2020
It's definitely not the timeout.