[image] Use correct endpoint scheme for api to registry connection
Bug #1462388 reported by
Mark Vanderwiel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack + Chef |
Fix Released
|
Medium
|
Mark Vanderwiel | ||
Bug Description
The ['openstack'
both the API service AND it's connection to the registry. Need
to allow for folks that was the API service to be SSL, but the
internal connection to the registry non-ssl. Using the registry
internal endpoint scheme (http or https) works perfectly for this
task.
| Changed in openstack-chef: | |
| status: | New → In Progress |
| Changed in openstack-chef: | |
| assignee: | Mark Vanderwiel (vanderwl) → Ma Wen Cheng (mars914) |
| Changed in openstack-chef: | |
| assignee: | Ma Wen Cheng (mars914) → Mark Vanderwiel (vanderwl) |
| Changed in openstack-chef: | |
| importance: | Undecided → Medium |
| Changed in openstack-chef: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/cookbook-openstack-image ocata-eol | #1 |
To post a comment you must log in.
This issue was fixed in the openstack/