Thanks very much, Kevin. After removing that line that disables tempest, things are looking a lot saner [1]. There are still other detailed things wrong with the config, and failures to look at, but I think I know how to attack those now.
(I also realized, from your help, that networking-calico/devstack/settings is incorrectly confusing two things: (a) What is a minimal complete devstack configuration, to demonstrate networking-calico function? and (b) What are the changes to devstack configuration that should be made if someone decides to do 'enable_plugin networking-calico'? So I'll also see about de-confusing that.) Neil [1] http://logs.openstack.org/63/339263/6/experimental/gate-tempest-dsvm-networking-calico-nv/3639cd8/console.html On Fri, Oct 21, 2016 at 8:06 AM Kevin Benton <ke...@benton.pub> wrote: > Left a comment on your patch. Looks like you have tempest disabled in your > devstack settings file. > > On Thu, Oct 20, 2016 at 4:34 AM, Neil Jerram <n...@tigera.io> wrote: > > I'm trying to set up a dsvm gate job for networking-calico [1] - which I > think means > - using DevStack to set up a single combined controller/compute node, with > networking-calico settings and plugin [2] > - using Tempest to run some tests on that; ideally including some > networking-related tests :-) > > Unfortunately it doesn't run well yet [3][4]: I see tests failing because > of something to do with credentials, and that also seem unrelated to > networking, and I'm not sure if any networking-related tests are running. > > I've tried comparing against the similar job for networking-ovn [5][6]. > Before the point where Tempest starts reporting success/failure of > individual tests, the only notable difference I see is that the > networking-calico output has: > > sed: can't read /opt/stack/new/tempest/etc/tempest.conf: No such file or > directory > Running tempest with a custom regex filter > all create: /opt/stack/new/tempest/.tox/tempest > all installdeps: setuptools, -r/opt/stack/new/tempest/requirements.txt > all develop-inst: /opt/stack/new/tempest > > where the networking-ovn output only has: > > Running tempest with a custom regex filter > all develop-inst-noop: /opt/stack/new/tempest > > Is that significant? > > Then the next, very obvious, difference is that the networking-calico > output seems to have the results of individual tests all jumbled up - like > output from multiple threads without a lock: > > ${PYTHON:-python} -m subunit.run discover -t ${OS_TOP_LEVEL:-./} > ${OS_TEST_PATH:-./tempest/test_discover} --load-list /tmp/tmpGuFAar > 2016-10-19 17:43:01.981 30902 INFO tempest [-] Using tempest config file > /etc/tempest/tempest.conf > 2016-10-19 17:43:02.005 30904 INFO tempest [-] Using tempest confi20g1 > 6file -/10e-19tc/te mp1e7s:4t3:/te02.030m 3pe0s908t INFO. tceonf > mpest [-] Using tempest config file /etc/tempest/tempest.co20n1f6 > -10-19 17:43:02.059 30906 INFO tempest [-] Using tempest config file > /etc/tempest/tempest.conf > {0} setUpClass > (tempest.api.baremetal.admin.test_api_discovery.TestApiDiscovery) ... > SKIPPED: TestApiDiscovery skipped as Ironic is not available > 2016-10-19 17:43:02.373 30902 INFO tempest.test [-] <class > 'tempest.lib.exceptions.InvalidCredentials'> raised in > AgentsAdminTestJSON.setUpClass. Invoking tearDownClass. > {3} setUpClass (tempest.api.baremetal.admin.test_nodes.TestNodes) ... > SKIPPED: TestNodes skipped as Ironic is not available > {2} setUpClass (tempest.api.baremetal.admin.test_drivers.TestDrivers) ... > SKIPPED: TestDrivers skipped as Ironic is not available > {2} setUpClass > (tempest.api.baremetal.admin.test_ports_negative.TestPortsNegative) ... > SKIPPED: TestPortsNegative skipped as Ironic is not available > 20{3} setUpClass > (tempest.api.baremetal.admin.test_nodestates.TestNodeStates) ... SKIPPED: > TestNodeStates skipped as Ironic is not available > 16{0} setUpClass > (tempest.api.compute.admin.test_agents.AgentsAdminTestJSON) [0.000000s] ... > FAILED > 2{3} setUpClass (tempest.api.baremetal.admin.test_ports.TestPorts) ... > SKIPPED: TestPorts skipped as Ironic is not available > 021-106-1-016190- -111097:- 147:13:9403:2. 104728.32 :4{1} setUpClass > (tempest.api.baremetal.admin.test_chassis.TestChassis) ... SKIPPED: > TestChassis skipped as Ironic is not available > 23:3020.41356 7-9 0931300006 INFO tempest.test [-] <class > 'tempest.lib.exceptions.InvalidCre908 INFO- t19de 90empe17st.:4tes3:0tn22 > t. [i3-8aIN]l6 FOs t'30em90<p>4 IN class resFa't.O teitesmpstt > eedst.teste[ -mp] [- in]e< s cBtl<.aarlisb.ecmetexalceptions.Invs > 'temNodesAdminTestJSON.setUpCalpesidCredentitlaa.lliss 'teb.eassxce. > Inlspmtvoki'>on ras.piieInng vassliedtdC i.lrn > Agitgeber.aeergaxDcdteoepesntAdtiwmioniannlCsN'el>sga .asrItsan.iiv > > whereas the networking-ovn output looks neat: > > ${PYTHON:-python} -m subunit.run discover -t ${OS_TOP_LEVEL:-./} > ${OS_TEST_PATH:-./tempest/test_discover} --load-list /tmp/tmpl_uSDt > {0} setUpClass > (tempest.api.baremetal.admin.test_nodestates.TestNodeStates) ... SKIPPED: > TestNodeStates skipped as Ironic is not available > {2} setUpClass > (tempest.api.baremetal.admin.test_api_discovery.TestApiDiscovery) ... > SKIPPED: TestApiDiscovery skipped as Ironic is not available > {2} setUpClass (tempest.api.baremetal.admin.test_ports.TestPorts) ... > SKIPPED: TestPorts skipped as Ironic is not available > {3} setUpClass (tempest.api.baremetal.admin.test_chassis.TestChassis) ... > SKIPPED: TestChassis skipped as Ironic is not available > {1} setUpClass (tempest.api.baremetal.admin.test_drivers.TestDrivers) ... > SKIPPED: TestDrivers skipped as Ironic is not available > {1} setUpClass (tempest.api.baremetal.admin.test_nodes.TestNodes) ... > SKIPPED: TestNodes skipped as Ironic is not available > {1} setUpClass > (tempest.api.baremetal.admin.test_ports_negative.TestPortsNegative) ... > SKIPPED: TestPortsNegative skipped as Ironic is not available > {1} setUpClass > (tempest.api.compute.admin.test_baremetal_nodes.BaremetalNodesAdminTestJSON) > ... SKIPPED: BaremetalNodesAdminTestJSON skipped as Ironic is not available > {1} > tempest.api.compute.admin.test_flavors.FlavorsAdminTestJSON.test_create_flavor_using_string_ram > [0.232261s] ... ok > {1} > tempest.api.compute.admin.test_flavors.FlavorsAdminTestJSON.test_create_flavor_verify_entry_in_list_details > [0.101537s] ... ok > {1} > tempest.api.compute.admin.test_flavors.FlavorsAdminTestJSON.test_create_flavor_with_int_id > [0.081664s] ... ok > {1} > tempest.api.compute.admin.test_flavors.FlavorsAdminTestJSON.test_create_flavor_with_none_id > [0.079674s] ... ok > {1} > tempest.api.compute.admin.test_flavors.FlavorsAdminTestJSON.test_create_flavor_with_uuid_id > [0.075899s] ... ok > {1} > tempest.api.compute.admin.test_flavors.FlavorsAdminTestJSON.test_create_list_flavor_without_extra_data > [0.409597s] ... ok > > I would appreciate any help as regards what I'm doing wrong here. > > Thanks, > Neil > > [1] > http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/networking-calico.yaml > [2] > http://git.openstack.org/cgit/openstack/networking-calico/tree/devstack > [3] https://review.openstack.org/#/c/339263/ > [4] > http://logs.openstack.org/63/339263/5/experimental/gate-tempest-dsvm-networking-calico-nv/8d47b1c/console.html > [5] > http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/networking-ovn.yaml > [6] > http://logs.openstack.org/16/386016/1/check/gate-tempest-dsvm-networking-ovn/4e3924f/console.html.gz > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev