Placment API client doesn't honor insecure nor cafile parameters
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | OpenStack Compute (nova) |
Medium
|
Sean Dague | ||
| | Ocata |
Medium
|
Sean Dague | ||
Bug Description
The connection to the Placement API from Nova doesn't allow to specify an insecure nor a cafile parameter. This could be a problem if those are used in the Keystone or Neutron clients, for example, then it is expected to use them in the Placement client, too.
| Changed in nova: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| tags: | added: api placement |
| Changed in nova: | |
| assignee: | nobody → György Szombathelyi (gyurco) |
| status: | Confirmed → In Progress |
| Sylvain Bauza (sylvain-bauza) wrote : | #1 |
Fix proposed to branch: stable/ocata
Review: https:/
Fix proposed to branch: master
Review: https:/
| Changed in nova: | |
| assignee: | György Szombathelyi (gyurco) → Sean Dague (sdague) |
Fix proposed to branch: stable/ocata
Review: https:/
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit a377fc5988e9a60
Author: Gyorgy Szombathelyi <email address hidden>
Date: Tue Feb 21 15:04:13 2017 +0100
Use the keystone session loader in the placement reporting
Using load_session_
session settings like cafile and insecure, to make use of non-system TLS
certificates (or disable certificate checks at all). Also client
certificates and timeout values can be specified, too.
Closes-Bug: #1666936
Change-Id: I510a2683958fc8
| Changed in nova: | |
| status: | In Progress → Fix Released |
| OpenStack Infra (hudson-openstack) wrote : | #6 |
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit adbf28f8194f901
Author: Sean Dague <email address hidden>
Date: Wed Feb 22 16:43:51 2017 -0500
Allow nova-status to work with custom ca for placement
Change-Id: I9f8b840f5a99d1
Closes-Bug: #1666936
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: stable/ocata
commit 2bb632ac888703e
Author: Gyorgy Szombathelyi <email address hidden>
Date: Tue Feb 21 15:04:13 2017 +0100
Use the keystone session loader in the placement reporting
Using load_session_
session settings like cafile and insecure, to make use of non-system TLS
certificates (or disable certificate checks at all). Also client
certificates and timeout values can be specified, too.
Closes-Bug: #1666936
Change-Id: I510a2683958fc8
(cherry picked from commit a377fc5988e9a60
| OpenStack Infra (hudson-openstack) wrote : | #8 |
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: stable/ocata
commit b9335a49e6386ff
Author: Sean Dague <email address hidden>
Date: Wed Feb 22 16:43:51 2017 -0500
Allow nova-status to work with custom ca for placement
Change-Id: I9f8b840f5a99d1
Closes-Bug: #1666936
(cherry picked from commit adbf28f8194f901
This issue was fixed in the openstack/nova 15.0.1 release.
This issue was fixed in the openstack/nova 16.0.0.0b1 development milestone.
| Tom Carroll (h-thomas-carroll) wrote : | #13 |
Is it possible to get this patch backported to Newton?
Patch is up https:/