OpenStack v3 service catalog empty

[Holger Protzek]

Hello, 

I am getting following error:

packer build template.json 

openstack output will be in this color.

Build 'openstack' errored: Error initializing compute client: No suitable endpoint could be found in the service catalog.

==> Some builds didn't complete successfully and had errors:

--> openstack: Error initializing compute client: No suitable endpoint could be found in the service catalog.

==> Builds finished but no artifacts were created.

Packer template:

{
  "builders": [
    {
      "type": "openstack",
      "image_name": "server-image",
      "flavor": "l",
      "source_image_name": "ubuntu_16.04",
      "ssh_username": "ubuntu",
      "domain_name": "Default"
    }
  ]
}

Authentication with OpenStack works find, but what I have seen so far, is that gophercloud gets an empty service catalog from OpenStack.

catalog, err := result.ExtractServiceCatalog()

Any idea if this is a permission or configuration problem with the OpenStack setup?

Kind regards,

Holger

[Holger Protzek]

Debugging this with a test case:

catalog, err := result.ExtractServiceCatalog()

if err != nil {

return err

}

returns for catalog

len:0, cap:0

without an error.

[Rickard von Essen]

can you get the service catalog with the cli with the same creds?

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/00cc308c-62f2-4962-a1d0-35b0cfaee1f9%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Holger Protzek]

We found the problem. We had to associate a default project to the service account, because the gophercloud api is trying to get a token without specifying a project in the request.