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

2012-09-28 Thread David Kranz
I will do that. I found out why the test wasn't running at all. The gate job is run for smoke and everything like this: sudo -H -u stack NOSE_XUNIT_FILE=nosetests-smoke.xml nosetests --with-xunit -sv --nologcapture --attr=type=smoke tempest sudo -H -u stack NOSE_XUNIT_FILE=nosetests-full.xml no

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

2012-09-28 Thread Jay Pipes
That's because I forgot to decorate the base SmokeTest with the @attr(type="smoke") decorator :( Feel like doing that? -jay On 09/28/2012 01:05 PM, David Kranz wrote: > Thanks, Jay. But this now confirms that test_server_basic_ops is not > running in the gating job. But it does run when I do 'n

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

2012-09-28 Thread David Kranz
Thanks, Jay. But this now confirms that test_server_basic_ops is not running in the gating job. But it does run when I do 'nosetests -v tempest' in my local environment. How could this be? -David Nothing in the gate log, but this in my local: test_001_create_keypair (tempest.tests.compute.t

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

2012-09-28 Thread Jay Pipes
Approved and merged. On 09/28/2012 11:51 AM, David Kranz wrote: > This was the problem (trivial) https://review.openstack.org/#/c/13840/. > Some one please review. > I am not sure when the behavior changed. > > -David > > On 9/25/2012 10:59 AM, Dolph Mathews wrote: >> That generally pops up wh

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

2012-09-28 Thread David Kranz
This was the problem (trivial) https://review.openstack.org/#/c/13840/. Some one please review. I am not sure when the behavior changed. -David On 9/25/2012 10:59 AM, Dolph Mathews wrote: That generally pops up when you're bypassing authentication using --endpoint & --token (no authenticatio

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

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: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 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

[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