Migrating a volume, which is in-use, between different cinder backends triggers the error novaclient.exceptions.EndpointNotFound
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Undecided
|
NidhiMittalHada |
Bug Description
While migrate a volume, which is attached to an instance, from one backend to another will trigger an erros as below:
2017-02-17 01:03:09.676 1540246 INFO cinder.
2017-02-17 01:03:13.512 1540270 ERROR cinder.
2017-02-17 01:03:13.512 1540270 ERROR cinder.
2017-02-17 01:03:13.512 1540270 ERROR cinder.
2017-02-17 01:03:13.512 1540270 ERROR cinder.
2017-02-17 01:03:13.512 1540270 ERROR cinder.
2017-02-17 01:03:13.512 1540270 ERROR cinder.
2017-02-17 01:03:13.512 1540270 ERROR cinder.
2017-02-17 01:03:13.512 1540270 ERROR cinder.
2017-02-17 01:03:13.512 1540270 ERROR cinder.
2017-02-17 01:03:13.512 1540270 ERROR cinder.
2017-02-17 01:03:13.512 1540270 ERROR cinder.
2017-02-17 01:03:13.512 1540270 ERROR cinder.
2017-02-17 01:03:13.515 1540270 DEBUG oslo_messaging.
summary: |
- Migrate a volume, which is in use, between different cinder backends - trigger error novaclient.exceptions.EndpointNotFound + Migrating a volume, which is in-use, between different cinder backends + triggers the error novaclient.exceptions.EndpointNotFound |
Changed in cinder: | |
assignee: | nobody → NidhiMittalHada (nidhimittal19) |
Retype in-use volume also triggers the same issue. This has been verified with Canonical Ocata release.