os-floating-ip assignFloatingIp documentation has incorrect inputs
Bug #1262868 reported by
Ken Perkins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-api-site |
Fix Released
|
Medium
|
Ken Perkins | ||
openstack-manuals |
Fix Released
|
Medium
|
Diane Fleming |
Bug Description
1. Open http://
2. Browse to the v2/{tenant_
Notice that the example json uses:
{
"pool": "nova"
}
And makes no mention of
{
addFloatingIp: {
address: '1.2.3.4'
}
}
Changed in openstack-api-site: | |
assignee: | nobody → Ken Perkins (ken-perkins) |
Changed in openstack-api-site: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in openstack-api-site: | |
status: | Triaged → In Progress |
Changed in openstack-api-site: | |
milestone: | none → icehouse |
Changed in openstack-api-site: | |
status: | In Progress → Fix Committed |
Changed in openstack-manuals: | |
status: | In Progress → Fix Committed |
Changed in openstack-api-site: | |
status: | Fix Committed → Fix Released |
Changed in openstack-manuals: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The Admin User Guide also needs to be updated to mention that the cloud operator must create a pool of floating IPs before you can add a floating IP to an instance.
http:// docs.openstack. org/user- guide-admin/ content/ manage_ ip_addresses. html