subject:"\[openstack\-dev\] \[openstack\-infra\] \[CI\] \[tempest\] Tempest tests failing with SSH timeout."

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-21 Thread Asselin, Ramy

Why do you want to stop those downloads? The purpose is to setup your VM so 
that it has the latest code in the git repos and that each project has any 
custom refs, such as the patch under test.

Also, this is a different problem than the subject, so should be a new thread.

Ramy

From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Tuesday, July 21, 2015 2:15 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: openstack-in...@lists.openstack.org
Subject: Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests 
failing with SSH timeout.

Also, can't we stop downloading all those projects and let them include them in 
the DevStack using the ENABLED_SERVICES parameter, like we usually do while 
installing devstack.

On Tue, Jul 21, 2015 at 11:18 AM, Abhishek Shrivastava 
mailto:abhis...@cloudbyte.com>> wrote:
Hi Ramy,


  *   The project list is mentioned in the "devstack-vm-gate-wrap" script[1].
  *   Downloaded using "functions.sh" script using "setup workspace" function[2]
[1] 
https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate-wrap.sh#L35
[2] 
https://github.com/openstack-infra/devstack-gate/blob/master/functions.sh#L416

On Mon, Jul 20, 2015 at 7:14 PM, Asselin, Ramy 
mailto:ramy.asse...@hp.com>> wrote:
Is this to optimize the performance of the job? Can you provide a link to where 
the downloading is occurring that you’d like to restrict?

From: Abhishek Shrivastava 
[mailto:abhis...@cloudbyte.com<mailto:abhis...@cloudbyte.com>]
Sent: Sunday, July 19, 2015 10:53 PM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests 
failing with SSH timeout.

This is ok for the services it will install, but how can we also restrict the 
downloading of all the projects(i.e; downloading only required projects) ?

On Sun, Jul 19, 2015 at 11:39 PM, Asselin, Ramy 
mailto:ramy.asse...@hp.com>> wrote:
There are two ways that I know of to customize what services are run:

1.  Setup your own feature matrix [1]

2.  Override enabled services [2]

Option 2 is probably what you’re looking for.

[1] 
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate-wrap.sh#n152
[2] 
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate.sh#n76

From: Abhishek Shrivastava 
[mailto:abhis...@cloudbyte.com<mailto:abhis...@cloudbyte.com>]
Sent: Sunday, July 19, 2015 10:37 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. 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 
mailto:ramy.asse...@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:abhis...@cloudbyte.com<mailto:abhis...@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 
mailto:ramy.asse...@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:abhis...@cloudbyte.com<mailto:abhis...@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_volum

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-21 Thread Abhishek Shrivastava

Also, can't we stop downloading all those projects and let them include
them in the DevStack using the ENABLED_SERVICES parameter, like we usually
do while installing devstack.

On Tue, Jul 21, 2015 at 11:18 AM, Abhishek Shrivastava <
abhis...@cloudbyte.com> wrote:

> Hi Ramy,
>
>
>- The project list is mentioned in the "*devstack-vm-gate-wrap*"
>script[1].
>- Downloaded using "*functions.sh*" script using "*setup workspace*"
>function[2]
>
> [1]
> https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate-wrap.sh#L35
> [2]
> https://github.com/openstack-infra/devstack-gate/blob/master/functions.sh#L416
>
> On Mon, Jul 20, 2015 at 7:14 PM, Asselin, Ramy 
> wrote:
>
>>  Is this to optimize the performance of the job? Can you provide a link
>> to where the downloading is occurring that you’d like to restrict?
>>
>>
>>
>> *From:* Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
>> *Sent:* Sunday, July 19, 2015 10:53 PM
>>
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest
>> tests failing with SSH timeout.
>>
>>
>>
>> This is ok for the services it will install, but how can we also restrict
>> the downloading of all the projects(i.e; downloading only required
>> projects) ?
>>
>>
>>
>> On Sun, Jul 19, 2015 at 11:39 PM, Asselin, Ramy 
>> wrote:
>>
>>  There are two ways that I know of to customize what services are run:
>>
>> 1.  Setup your own feature matrix [1]
>>
>> 2.  Override enabled services [2]
>>
>>
>>
>> Option 2 is probably what you’re looking for.
>>
>>
>>
>> [1]
>> http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate-wrap.sh#n152
>>
>> [2]
>> http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate.sh#n76
>>
>>
>>
>> *From:* Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
>> *Sent:* Sunday, July 19, 2015 10:37 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. 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 
>> 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:abhis...@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 
>> 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:abhis...@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 S

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-20 Thread Abhishek Shrivastava

Hi Ramy,


   - The project list is mentioned in the "*devstack-vm-gate-wrap*"
   script[1].
   - Downloaded using "*functions.sh*" script using "*setup workspace*"
   function[2]

[1]
https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate-wrap.sh#L35
[2]
https://github.com/openstack-infra/devstack-gate/blob/master/functions.sh#L416

On Mon, Jul 20, 2015 at 7:14 PM, Asselin, Ramy  wrote:

>  Is this to optimize the performance of the job? Can you provide a link
> to where the downloading is occurring that you’d like to restrict?
>
>
>
> *From:* Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
> *Sent:* Sunday, July 19, 2015 10:53 PM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest
> tests failing with SSH timeout.
>
>
>
> This is ok for the services it will install, but how can we also restrict
> the downloading of all the projects(i.e; downloading only required
> projects) ?
>
>
>
> On Sun, Jul 19, 2015 at 11:39 PM, Asselin, Ramy 
> wrote:
>
>  There are two ways that I know of to customize what services are run:
>
> 1.  Setup your own feature matrix [1]
>
> 2.  Override enabled services [2]
>
>
>
> Option 2 is probably what you’re looking for.
>
>
>
> [1]
> http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate-wrap.sh#n152
>
> [2]
> http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate.sh#n76
>
>
>
> *From:* Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
> *Sent:* Sunday, July 19, 2015 10:37 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. 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 
> 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:abhis...@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 
> 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:abhis...@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.scenari

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-20 Thread Asselin, Ramy

Is this to optimize the performance of the job? Can you provide a link to where 
the downloading is occurring that you’d like to restrict?

From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Sunday, July 19, 2015 10:53 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests 
failing with SSH timeout.

This is ok for the services it will install, but how can we also restrict the 
downloading of all the projects(i.e; downloading only required projects) ?

On Sun, Jul 19, 2015 at 11:39 PM, Asselin, Ramy 
mailto:ramy.asse...@hp.com>> wrote:
There are two ways that I know of to customize what services are run:

1.  Setup your own feature matrix [1]

2.  Override enabled services [2]

Option 2 is probably what you’re looking for.

[1] 
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate-wrap.sh#n152
[2] 
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate.sh#n76

From: Abhishek Shrivastava 
[mailto:abhis...@cloudbyte.com<mailto:abhis...@cloudbyte.com>]
Sent: Sunday, July 19, 2015 10:37 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. 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 
mailto:ramy.asse...@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:abhis...@cloudbyte.com<mailto:abhis...@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 
mailto:ramy.asse...@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:abhis...@cloudbyte.com<mailto:abhis...@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/t

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-19 Thread Abhishek Shrivastava

This is ok for the services it will install, but how can we also restrict
the downloading of all the projects(i.e; downloading only required
projects) ?

On Sun, Jul 19, 2015 at 11:39 PM, Asselin, Ramy  wrote:

>  There are two ways that I know of to customize what services are run:
>
>  1.  Setup your own feature matrix [1]
>
> 2.  Override enabled services [2]
>
>
>
> Option 2 is probably what you’re looking for.
>
>
>
> [1]
> http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate-wrap.sh#n152
>
> [2]
> http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate.sh#n76
>
>
>
> *From:* Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
> *Sent:* Sunday, July 19, 2015 10:37 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. 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 
> 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:abhis...@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 
> 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:abhis...@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_co

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-19 Thread Asselin, Ramy

There are two ways that I know of to customize what services are run:

1.  Setup your own feature matrix [1]

2.  Override enabled services [2]

Option 2 is probably what you’re looking for.

[1] 
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate-wrap.sh#n152
[2] 
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate.sh#n76

From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Sunday, July 19, 2015 10:37 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. 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 
mailto:ramy.asse...@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:abhis...@cloudbyte.com<mailto:abhis...@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 
mailto:ramy.asse...@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:abhis...@cloudbyte.com<mailto:abhis...@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 ERR

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-19 Thread Abhishek Shrivastava

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  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:abhis...@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 
> 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:abhis...@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.

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-19 Thread Asselin, Ramy

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:abhis...@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 
mailto:ramy.asse...@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:abhis...@cloudbyte.com<mailto:abhis...@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<http://tempest_lib.common.re>



Because of these every job is failing, so if someone can help me regarding this 
please do reply.

--
[https://docs.google.com/uc?export=download&id=0Byq0j7ZjFlFKV3ZCWnlMRXBCcU0&revid=0Byq0j7ZjFlFKa2V5VjdBSjIwUGx6bUROS2IrenNwc0kzd2IwPQ]
Thanks & Regards,
Abhishek
Cloudbyte Inc.<http://www.cloudbyte.com>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
[https://docs.google.com/uc?export=download&id=0Byq0j7ZjFlFKV3ZCWnlMRXBCcU0&revid=0Byq0j7ZjFlFKa2V5VjdBSjIwUGx6bUROS2IrenNwc0kzd2IwPQ]
Thanks & Regards,
Abhishek
Cloudbyte Inc.<http://www.cloudbyte.com&

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-19 Thread Abhishek Shrivastava

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  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:abhis...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-18 Thread Asselin, Ramy

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:abhis...@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<http://tempest_lib.common.re>



Because of these every job is failing, so if someone can help me regarding this 
please do reply.

--
[https://docs.google.com/uc?export=download&id=0Byq0j7ZjFlFKV3ZCWnlMRXBCcU0&revid=0Byq0j7ZjFlFKa2V5VjdBSjIwUGx6bUROS2IrenNwc0kzd2IwPQ]
Thanks & Regards,
Abhishek
Cloudbyte Inc.<http://www.cloudbyte.com>
__
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-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

2015-07-17 Thread Abhishek Shrivastava

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. *
__
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

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

Re: [openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

[openstack-dev] [openstack-infra] [CI] [tempest] Tempest tests failing with SSH timeout.

11 matches

Site Navigation

Mail list logo

Footer information