[openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.
Abhishek Shrivastava
abhishek at cloudbyte.com
Sun Jul 19 17:37:20 UTC 2015
Hi Ramy,
Thanks for the suggestion. One more thing I need to ask, as I have have
setup one more CI so is there any way that we can decide that only required
projects should get downloaded and installed during devstack installation
dynamically. As I see no such things that can be done to devstack-gate
scripts so the following scenario can be achieved.
On Sun, Jul 19, 2015 at 8:38 PM, Asselin, Ramy <ramy.asselin at hp.com> wrote:
> Just the export I mentioned:
>
> export DEVSTACK_GATE_NEUTRON=1
>
> Devstack-gate scripts will do the right thing when it sees that set. You
> can see plenty of examples here [1].
>
>
>
> Ramy
>
>
>
> [1]
> http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/devstack-gate.yaml#n467
>
>
>
> *From:* Abhishek Shrivastava [mailto:abhishek at cloudbyte.com]
> *Sent:* Sunday, July 19, 2015 2:24 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest
> tests failing with SSH timeout.
>
>
>
> Hi Ramy,
>
>
>
> Thanks for the suggestion but since I am not including the neutron
> project, so downloading and including it will require any additional
> configuration in devstack-gate or not?
>
>
>
> On Sat, Jul 18, 2015 at 11:41 PM, Asselin, Ramy <ramy.asselin at hp.com>
> wrote:
>
> We ran into this issue as well. I never found the root cause, but I
> found a work-around: Use neutron-networking instead of the default
> nova-networking.
>
>
>
> If you’re using devstack-gate, it’s as simple as:
>
> export DEVSTACK_GATE_NEUTRON=1
>
>
>
> Then run the job as usual.
>
>
>
> Ramy
>
>
>
> *From:* Abhishek Shrivastava [mailto:abhishek at cloudbyte.com]
> *Sent:* Friday, July 17, 2015 9:15 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests
> failing with SSH timeout.
>
>
>
> Hi Folks,
>
>
>
> In my CI I see the following tempest tests failure for a past couple of
> days.
>
> · tempest.scenario.test_minimum_basic.TestMinimumBasicScenario.test_minimum_basic_scenario [361.274316s] ... FAILED
>
> · tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern [320.122458s] ... FAILED
>
> · tempest.scenario.test_volume_boot_pattern.TestVolumeBootPatternV2.test_volume_boot_pattern [317.399342s] ... FAILED
>
> · tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest.test_compute_with_volumes [257.858272s] ... FAILED
>
> The failure logs are always the same every time, i.e;
>
>
>
> *03:34:09* 2015-07-17 03:21:13,256 9505 ERROR [tempest.scenario.manager] (TestVolumeBootPattern:test_volume_boot_pattern) Initializing SSH connection to 172.24.5.1 failed. Error: Connection to the 172.24.5.1 via SSH timed out.
>
> *03:34:09* User: cirros, Password: None
>
> *03:34:09* 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager Traceback (most recent call last):
>
> *03:34:09* 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager File "tempest/scenario/manager.py", line 312, in get_remote_client
>
> *03:34:09* 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager linux_client.validate_authentication()
>
> *03:34:09* 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager File "tempest/common/utils/linux/remote_client.py", line 62, in validate_authentication
>
> *03:34:09* 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager self.ssh_client.test_connection_auth()
>
> *03:34:09* 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager File "/opt/stack/new/tempest/.tox/all/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py", line 151, in test_connection_auth
>
> *03:34:09* 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager connection = self._get_ssh_connection()
>
> *03:34:09* 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager File "/opt/stack/new/tempest/.tox/all/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py", line 87, in _get_ssh_connection
>
> *03:34:09* 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager password=self.password)
>
> *03:34:09* 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager SSHTimeout: Connection to the 172.24.5.1 via SSH timed out.
>
> *03:34:09* 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager User: cirros, Password: None
>
> *03:34:09* 2015-07-17 03:21:13.256 9505 ERROR tempest.scenario.manager
>
> *03:34:09* 2015-07-17 03:21:14,377 9505 INFO [tempest_lib.common.re
>
>
>
> Because of these every job is failing, so if someone can help me regarding this please do reply.
>
>
>
> --
>
> *Thanks & Regards,*
>
> *Abhishek*
>
> *Cloudbyte Inc. <http://www.cloudbyte.com>*
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
>
> --
>
> *Thanks & Regards,*
>
> *Abhishek*
>
> *Cloudbyte Inc. <http://www.cloudbyte.com>*
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
*Thanks & Regards,*
*Abhishek*
*Cloudbyte Inc. <http://www.cloudbyte.com>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150719/b4daed49/attachment.html>
More information about the OpenStack-dev
mailing list