nova::api::validate command fails in clean installation

Bug #1853070 reported by Zachary Boerner
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet-nova
Won't Fix
Low
Unassigned

Bug Description

I think this is a bug in the validation...

When you set the nova::api::validate option to true, then the module tries to run a flavor-list command using the nova user in the services project. However, because there is no listed domain, OpenStack tries to use the "default" domain. Because most of the puppet-* projects in the OpenStack domain use "Default" as their domain, this command fails with a 401 since keystone hasn't authenticated the user.

This is the command that is composed:
nova --os-auth-url <auth_url> --os-project-name services --os-username nova --os-password <password> flavor-list

I tested it with:
nova --os-auth-url <auth_url> --os-project-domain-name Default --os-user-domain-name Default --os-project-name services --os-username nova --os-password <password> flavor-list

and it succeeded.

Changed in puppet-nova:
status: New → Triaged
Revision history for this message
Takashi Kajinami (kajinamit) wrote :

Because we've decided to remove service validations in our modules, I'll close this as WON'T FIX.

Changed in puppet-nova:
importance: Undecided → Wishlist
importance: Wishlist → Low
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.