[Openstack-qa-team] What is going on with test_server_*_ops?

2012-09-25 Thread David Kranz
I heard from some of my team members that test_server_basic_ops and test_server_advanced_ops were failing and I can reproduce it with current devstack/tempest. Looking at the code it seems that the keystone Client object does not have a service_catalog object like the error says. So why is this

Re: [Openstack-qa-team] What is going on with test_server_*_ops?

2012-09-25 Thread Jay Pipes
On 09/25/2012 09:38 AM, David Kranz wrote: > I heard from some of my team members that test_server_basic_ops and > test_server_advanced_ops were failing and I can reproduce it with > current devstack/tempest. > Looking at the code it seems that the keystone Client object does not > have a servic

Re: [Openstack-qa-team] What is going on with test_server_*_ops?

2012-09-25 Thread David Kranz
On 9/25/2012 10:35 AM, Jay Pipes wrote: On 09/25/2012 09:38 AM, David Kranz wrote: I heard from some of my team members that test_server_basic_ops and test_server_advanced_ops were failing and I can reproduce it with current devstack/tempest. Looking at the code it seems that the keystone Client

Re: [Openstack-qa-team] What is going on with test_server_*_ops?

2012-09-25 Thread Dolph Mathews
That generally pops up when you're bypassing authentication using --endpoint & --token (no authentication == no service catalog). Is it using old command line options to specify auth attributes, which were just removed in favor of --os-username, --os-password, etc? https://github.com/openstack/py

Re: [Openstack-qa-team] What is going on with test_server_*_ops?

2012-09-25 Thread David Kranz
On 9/25/2012 10:59 AM, Dolph Mathews wrote: That generally pops up when you're bypassing authentication using --endpoint & --token (no authentication == no service catalog). Is it using old command line options to specify auth attributes, which were just removed in favor of --os-username, --os