Different endpoints shown for swift adminurl install and starter documents
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Book |
In Progress
|
Medium
|
eternaltyro | ||
openstack-manuals |
Fix Released
|
Medium
|
Tom Fifield |
Bug Description
Different swift adminurl endpoints are shown in the 2essex install documents.
http://
$ keystone --token 012345SECRET99T
--endpoint http://
endpoint-create \
--region RegionOne \
--service_
--publicurl 'http://
--adminurl 'http://
--internalurl 'http://
Also the 8888 port does not match the reported response in the document.
$ keystone endpoint-create --region myregion --service_id 96f35e1112b143e
--publicurl 'http://
--adminurl 'http://
--internalurl 'http://
I'm having problems with my swift install at then moment.
swift -v -V 2.0 -A http://
"There is no object-store endpoint on this auth server"
This occurs for both of these adminulr end point settings, so I am not sure which is correct.
Changed in openstack-manuals: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: swift |
Changed in openstackbook: | |
assignee: | nobody → koolhead17 (koolhead17) |
importance: | Undecided → High |
importance: | High → Medium |
Changed in openstackbook: | |
status: | New → In Progress |
Changed in openstackbook: | |
assignee: | koolhead17 (koolhead17) → Eternal Tyro (eternaltyro) |
https:/ /review. openstack. org/#/c/ 8901/ should fix openstack-manuals
for openstackbook, my guess is that all is needed is a port change to 8888