top-level namespace methods cause collisions
Bug #1429096 reported by
Michael Renner
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-heat |
Fix Released
|
Critical
|
Emilien Macchi | ||
puppet-neutron |
Fix Released
|
Critical
|
Emilien Macchi |
Bug Description
When using puppet-neutron in combination with puppet-heat this causes a collision with methods in the top-level namespace.
See
These providers should probably be moved to https:/
Changed in puppet-neutron: | |
importance: | Undecided → Critical |
Changed in puppet-heat: | |
status: | New → In Progress |
Changed in puppet-heat: | |
milestone: | none → 6.0.0 |
Changed in puppet-neutron: | |
milestone: | none → 6.0.0 |
Changed in puppet-neutron: | |
status: | Fix Committed → Fix Released |
Changed in puppet-heat: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
That bug leads to being unable to use heat::keystone: :domain and neutron: :server: :notifications because both provider have different definitions which causes such things:
Error: /Stage[ main]/Neutron: :Server: :Notifications/ Nova_admin_ tenant_ id_setter[ nova_admin_ tenant_ id]: Could not evaluate: Received error response from Keystone server at http:// x.x.x.x: 35357/v2. 0/tenants: Unauthorized