and have additionally added the certificates as described in #22.
However, I still cannot start instances with the "Create New Volume" slider enabled.
I can create volumes under Project -> Volumes just fine. But booting instances with an automatically created volume via the slider (see pic) fails with an error in the webui:
Error: Failed to perform requested operation on instance "asd", the instance has an error status: Please try again later [Error: Build of instance 3bd9a8d4-31b5-4516-90e6-bdca98f4b6ce aborted: Invalid input received: Invalid image identifier or unable to access requested image. (HTTP 400) (Request-ID: req-9f773f7d-be0c-48a3-9782-96bde6708f42)].
The error it fails on is the block device mapping step.
Any help would be appreciated. If you tell me where to look, I can provide log-output, screenshots etc.
For me the bug does not seem to be resolved.
I have followed this report, setting up Microstack with a Cinder Loop Device with
sudo microstack.init --auto --control --setup- loop-based- cinder- lvm-backend --loop- device- file-size 100
and have additionally added the certificates as described in #22.
However, I still cannot start instances with the "Create New Volume" slider enabled.
I can create volumes under Project -> Volumes just fine. But booting instances with an automatically created volume via the slider (see pic) fails with an error in the webui:
Error: Failed to perform requested operation on instance "asd", the instance has an error status: Please try again later [Error: Build of instance 3bd9a8d4- 31b5-4516- 90e6-bdca98f4b6 ce aborted: Invalid input received: Invalid image identifier or unable to access requested image. (HTTP 400) (Request-ID: req-9f773f7d- be0c-48a3- 9782-96bde6708f 42)].
The error it fails on is the block device mapping step.
Any help would be appreciated. If you tell me where to look, I can provide log-output, screenshots etc.