Ask Your Question

Charles's profile - activity

2019-04-14 16:34:15 -0500 received badge  Notable Question (source)
2019-04-14 16:34:15 -0500 received badge  Popular Question (source)
2019-02-07 03:24:56 -0500 asked a question Select a specific identity endpoint


I have an openstack (queen version) configured with three endpoints for the service keystone/identity ( public, admin, internal ).

I'am using python-openstackclient (3.17.0) to access the id of the service placement: =>'placement').id

My code is accessing openstack from a computer that have only access to the public url and my code use either admin or internal:

2019-02-07 08:17:40,786 [17705] DEBUG    urllib3.connectionpool: Starting new HTTP connection (1):
2019-02-07 08:19:50,288 [17705] WARNING Failed to contact the endpoint at for discovery. Fallback to using that endpoint as the base url.
2019-02-07 08:19:50,288 [17705] DEBUG    keystoneauth.session: REQ: curl -g -i --insecure -X GET -H "Accept: application/json" -H "User-Agent: python-keystoneclient" -H "X-Auth-Token: {SHA256}9a6c42ffqsdfqsdfqbh5464535d2026234a5553413dfqsdfdgdfqdgq9c5216febd35192727141"
2019-02-07 08:19:50,292 [17705] DEBUG    urllib3.connectionpool: Starting new HTTP connection (2):
2019-02-07 08:22:01,360 [17705] ERROR Exception on /v1/compute_resources/capacities/query [POST]

The keystone user I am using is only member.

Is it possible to force my code to use the public admin instead of the internal/admin ?

Best regards.


I did some digging in the source code of python-keystoneclient.

In this file: vi releasenotes/notes/ksc_2.1.0-739ded9c4c3f8aaa.yaml [bug 1457702 <>_] Change default endpoint to public for keystone v3.

That's what I need. And when I compared the commit witch my version of python-keystoneclient

I realized that the line: kwargs.setdefault('interface', 'public') has disappeared.

With a git blame on the file, I have discovered some other lines about endpoints that are not around anymore.

I read this post :

And setting the default endpoint for a user could be a solution. But I found no cli command in my openstack-client to do so.

This post is also around 2015, so my guess is that things have evolved but I have no idea why and how to solve my problem.

2017-06-10 10:56:54 -0500 received badge  Taxonomist
2017-01-17 13:12:14 -0500 received badge  Self-Learner (source)
2017-01-17 13:12:14 -0500 received badge  Teacher (source)
2017-01-17 13:04:31 -0500 received badge  Nice Question (source)
2017-01-12 08:16:55 -0500 received badge  Famous Question (source)
2017-01-12 02:05:46 -0500 received badge  Enthusiast
2017-01-11 21:08:07 -0500 received badge  Student (source)
2017-01-11 07:26:14 -0500 received badge  Scholar (source)
2017-01-11 07:26:08 -0500 answered a question Why my vm is not responding to ARP request

Hi Guys,

I didn't really found the solution, I went deep down, at kvm/qemu level, checked the logs, compare kvm-qemu process with a working plateform, nothing ! It's not my field, maybe I didn't see the obvious.

By despair, I ran a 'rpm -qa | grep openstack', and realized that I was using an old version of openstack (liberty) with a brand new version of packstack.

So instead of liberty I installed newton and everything went smoothly.

Like Luis I have already installed liberty some month ago on the same type of vm, and by default I had a cirros image created and no difficulty to create a cirros vm.

By chance I saw this message in my console:

[ xxxx] microcode: CPU0 update to revision 0x38 failed
[ xxxx] microcode: CPU1 update to revision 0x38 failed
[ xxxx] microcode: CPU2 update to revision 0x38 failed
[ xxxx] microcode: CPU3 update to revision 0x38 failed

Coincidence ? Maybe ... I have no other clue, I'm running out of time so I will simply switch to newton.

Thanks for you help. Charles.

2017-01-09 07:54:33 -0500 commented question Why my vm is not responding to ARP request

One last thing

# virsh list --all
 ID    Nom                            √Čtat
 2     instance-00000010              en cours d'exécution

My instance never enters the state "runnig"

2017-01-09 07:37:39 -0500 commented question Why my vm is not responding to ARP request

At least I have solved my problem to add comment in this post ;-p.

Yes I did that too, apparently this part seems ok. What bugs me it's that I am not able find any clue to the origin of the problem. I've checked libvirt logs as well and no errors too.

2017-01-08 20:54:45 -0500 received badge  Notable Question (source)
2017-01-06 08:35:42 -0500 received badge  Popular Question (source)
2017-01-06 06:54:41 -0500 received badge  Editor (source)
2017-01-04 07:05:04 -0500 asked a question Why my vm is not responding to ARP request

Hi guys,

Here is a quick descritpion of my setup.

A CentOS7 VM and liberty distro, I used packstack and my config is "all-in-one". I've created a router, an external network and an internal network.

I've created a cirros image, and a test vm.

I've added the security rules for ping and ssh.

When I ping my vm with it's internal adress ( provided dynamically at creation ), I've got no answer either from my default namespace or from the router namespace.

With tcpdump, I monitored the tap interface and I see arp request, but the vm doesn't answer.

> nova list tells me the instance is ACTIVE and running.

And if I use virsh screenshot I have:

SeaBIOS (versio xxxxxxx)
Machine UUID xxxxxxxxxx
iPXE ( 00.03.0 C980 PCI2.10 PnP PMM

console.log is empty and my vm seems to be stuck in the boot step, but nova list and logs tell me that everything is fine.

I found a post on the net describing the same problem and the guy said that its image wasn't created correcly.

But I followed basic steps:

> wget
> glance image-create --name "cirros-0.3.4-x86_64" --file cirros-0.3.4-x86_64-disk.img --disk-format qcow2 --container-format bare --visibility public --progress
> nova boot --flavor m1.tiny --image cirros-0.3.4-x86_64 --key-name tapaas-key --nic net-id=cc615845-dc51-41e7-b470-10e00c4b5518 vm-cirros-0.3.4-x86_64

I tried we other version of cirros and other images. But it's the same. At first I've created a floating ip and if I ping this address, it is correctly translated in the internal address, because I see the ARP request.

I'm running out of ideas.

So If someone could help me, I'd be thankful.




I am editing my post because I cannot add comments or an answer for this thread, I send an email two days ago to AskOpestack team but so far no answer.

First thank you for your help and here my answer to your comments.

Yes I agree with you this is more a boot instance problem than a network problem. I tried to load the image with VirtualBox, but it failed at boot it was not recognize as a valid image I used this command:

VBoxManage convertfromraw --format VDI vdisk_raw.img vdisk.vdi

I tried glance image-download and diff ... same image. I tried other versions of cirros images, but with the same result. I have access to VNC console and I've got the same message as in the screenshoot ( stuck with the iPxe message ).


I've tested all the images I've downloaded, all checksums are ok.

As for the file format, I downloaded qcow2 because of the following comment on this page get image

"If your deployment uses QEMU or KVM, we recommend using the images in qcow2 format. The most recent 64-bit qcow2 image as of this writing is cirros-0.3.4-x86_64-disk.img."

I have ... (more)