add cluster_user_trust option in magnum.conf
Bug #1996237 reported by
Narinder Gupta
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Charm Guide |
Fix Released
|
Undecided
|
Felipe Reyes | ||
OpenStack Magnum Charm |
Fix Committed
|
High
|
Felipe Reyes | ||
2023.1 |
Fix Committed
|
Undecided
|
Unassigned | ||
Ussuri |
Fix Committed
|
Undecided
|
Unassigned | ||
Victoria |
Fix Committed
|
Undecided
|
Unassigned | ||
Wallaby |
Fix Committed
|
Undecided
|
Unassigned | ||
Xena |
Fix Committed
|
Undecided
|
Unassigned | ||
Yoga |
Fix Committed
|
Undecided
|
Unassigned | ||
Zed |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
TCS want to add cloud provider into the magnum defined cluster using the label cloud_provider_
To have cloud_provider_
CVE References
Changed in charm-magnum: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in charm-magnum: | |
importance: | Wishlist → High |
assignee: | nobody → Felipe Reyes (freyes) |
Changed in charm-guide: | |
assignee: | nobody → Felipe Reyes (freyes) |
To post a comment you must log in.
I have triaged this as on the surface its as simple as enabling a configuration option. However, it should be noted that there are additional considerations for this and the configuration does present the potential of secrets leaking per the documentation (CVE-2016-7404). Thus, it should be clearly spelled out the consequences of enabling such an options.