Ask Your Question

Revision history [back]

Sounds like keystone V2 now is affected in the same way as keystone V3 was since release RDO MItaka.
See :
https://bugzilla.redhat.com/show_bug.cgi?id=1330289
https://review.openstack.org/#/c/318762/
I would try back port patch and try with V2 in case of failure, option been tested was to switch to V3 via generated answer file and manage as in :-
http://bderzhavets.blogspot.com/2016/05/backport-upstream-commits-to-stable-rdo.html

 Another option generated answer file and run packstack --answer-file=./generated-answer.txt. Check status of cinder services after crash, if they are up and running, then disable cinder set up  via answer file and rerun.  Both ways worked for me with Keystone V3 been set up generated-answer.txt

Sounds like keystone V2 now is affected in the same way as keystone V3 was since release RDO MItaka.
See :
https://bugzilla.redhat.com/show_bug.cgi?id=1330289
https://review.openstack.org/#/c/318762/
I would try back port patch and try with V2 in case of failure, option been tested was to switch to V3 via generated answer file and manage as in :-
http://bderzhavets.blogspot.com/2016/05/backport-upstream-commits-to-stable-rdo.html
If instructions above appears to be hard to reproduce I am posting ugly hack bellow which worked for me nicely.

 Another option generated generate answer file and run packstack --answer-file=./generated-answer.txt. Check status of cinder services after crash, if they are up and running, then disable cinder set up  via answer file and rerun.  Both ways worked for me with Keystone V3 been set up generated-answer.txt

Sounds like keystone V2 now is affected in the same way as keystone V3 was since release RDO MItaka.
See :
https://bugzilla.redhat.com/show_bug.cgi?id=1330289
https://review.openstack.org/#/c/318762/
I would try back port patch and try with V2 in case of failure, option been tested was to switch to V3 via generated answer file and manage as in :-
http://bderzhavets.blogspot.com/2016/05/backport-upstream-commits-to-stable-rdo.html
If instructions above appears to be hard to reproduce I am posting ugly hack bellow which worked for me nicely.

 Another option generate answer file and run packstack --answer-file=./generated-answer.txt. Check status of cinder services after crash, if they are up and running, then disable cinder set up  via answer file and rerun.  Both ways worked for me with Keystone V3 been set up in generated-answer.txt

Sounds like keystone V2 now is affected in the same way as keystone V3 was since release RDO MItaka.

Run packstack --gen-answer-file=answer.txt and check for default keystone version
My concern is it still V2 either they switched to V3. My answer itself follows bellow.

See : :-
https://bugzilla.redhat.com/show_bug.cgi?id=1330289
https://review.openstack.org/#/c/318762/
I would try back port patch and try with V2 in case of failure, option been tested was to switch to V3 via generated answer file and manage as in :-
http://bderzhavets.blogspot.com/2016/05/backport-upstream-commits-to-stable-rdo.html
If instructions above appears to be hard to reproduce I am posting ugly hack bellow which worked for me nicely.

 Another option generate answer file and run packstack --answer-file=./generated-answer.txt. Check status of cinder services after crash, if they are up and running, then disable cinder set up  via answer file and rerun.  Both ways worked for me with Keystone V3 been set up in generated-answer.txt

UPDATE 19:51 MSK 08/07/16
Try before install :-

 pip install osc-lib

END UPDATE
Sounds like keystone V2 now is affected in the same way as keystone V3 was since release RDO MItaka.

Run packstack --gen-answer-file=answer.txt and check for default keystone version
My concern is it still V2 either they switched to V3. My answer itself follows bellow.

See :-
https://bugzilla.redhat.com/show_bug.cgi?id=1330289
https://review.openstack.org/#/c/318762/
I would try back port patch and try with V2 in case of failure, option been tested was to switch to V3 via generated answer file and manage as in :-
http://bderzhavets.blogspot.com/2016/05/backport-upstream-commits-to-stable-rdo.html
If instructions above appears to be hard to reproduce I am posting ugly hack bellow which worked for me nicely.

 Another option generate answer file and run packstack --answer-file=./generated-answer.txt. Check status of cinder services after crash, if they are up and running, then disable cinder set up  via answer file and rerun.  Both ways worked for me with Keystone V3 been set up in generated-answer.txt