nova-api can't find KS-ODM/services
Bug #1473242 reported by
Steven Dake
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla |
Invalid
|
Critical
|
Unassigned | ||
Bug Description
[sdake@bigiron tools]$ sudo docker logs 97 | more
keystone is active @ http://
using existing tenant admin (c475c9ddf6de47
creating new user nova
database is active @ 192.168.1.100
created user nova (771202afde6d42
using existing role admin (c754264f61834a
removing role _member_ from user nova in tenant admin
adding role admin to user nova in tenant admin
Unable to establish connection to http://
| Changed in kolla: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| milestone: | none → liberty-2 |
Revision history for this message
| Sam Yaple (s8m) wrote | #1 |
| Changed in kolla: | |
| milestone: | liberty-2 → none |
| milestone: | none → liberty-3 |
Revision history for this message
| Steven Dake (sdake) wrote | #2 |
| Changed in kolla: | |
| status: | Triaged → Invalid |
| milestone: | liberty-3 → none |
To post a comment you must log in.
OS-KSADM is for keystone v2.0 only, you wont have that for keystone v3
Depending on how you created the endpoints, you may not have v2.0 endpoints. This was the "bug" I pointed out to OSAD. Basically, you need to explicitly create endpoints via v2.0 endpoint rather than letting the client decide.
https:/