Re: [openstack-dev] [third-party] [CI] The dsvm-tempest-full job failed

2015-08-31 Thread Abhishek Shrivastava 
Hi Xianshan ,

So after starting nodepool you have configured the slave in Jenkins or it
was done automatically?

On Mon, Aug 31, 2015 at 1:15 PM, Xie, Xianshan  wrote:

> Hi, all,
>
>   I`m trying to run the job "dsvm-tempest-full" in a slave node which
> built and managed by the nodepool.
>
> But I got the following error messages:
>
> --
>
> 14:45:48 + timeout -s 9 174m
> /opt/stack/new/devstack-gate/devstack-vm-gate.sh
>
> 14:45:48 timeout: failed to run command
> ‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or
> directory
>
>
>
> ...
>
> 14:45:48 + echo 'ERROR: the main setup script run by this job failed -
> exit code: 127'
>
> 14:45:48 ERROR: the main setup script run by this job failed - exit code:
> 127
>
> ...
>
> 14:45:52 No hosts matched
>
> 14:45:52 + exit 127
>
> 14:45:52 Build step 'Execute shell' marked build as failure
>
> 14:45:53 Finished: FAILURE
>
> --
>
> I have no idea what caused this issue.
>
> And furthermore, it seems no more chances to find the detailed
> information about this error,
>
> because the slave node was deleted soon by the nodepool automatically,
> after this job finished.
>
> Is there a setting for the nodepool to prevent the used node being
> deleted?
>
>
>
> I have posted the full console log (which displayed in the Jenkins server)
> on the paste server:
>
> http://paste.openstack.org/show/434487/
>
>
>
> Cloud you give me some guidances to work this out?
>
> Thanks in advance.
>
>
>
>
>
> Xiexs
>
> __
> 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. *
__
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] [third-party] [CI] The dsvm-tempest-full job failed

2015-08-31 Thread Xie, Xianshan 
Hi, all,
  I`m trying to run the job "dsvm-tempest-full" in a slave node which built and 
managed by the nodepool.
But I got the following error messages:
--
14:45:48 + timeout -s 9 174m /opt/stack/new/devstack-gate/devstack-vm-gate.sh
14:45:48 timeout: failed to run command 
‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or directory

...
14:45:48 + echo 'ERROR: the main setup script run by this job failed - exit 
code: 127'
14:45:48 ERROR: the main setup script run by this job failed - exit code: 127
...
14:45:52 No hosts matched
14:45:52 + exit 127
14:45:52 Build step 'Execute shell' marked build as failure
14:45:53 Finished: FAILURE
--
I have no idea what caused this issue.
And furthermore, it seems no more chances to find the detailed information 
about this error,
because the slave node was deleted soon by the nodepool automatically, after 
this job finished.
Is there a setting for the nodepool to prevent the used node being deleted?

I have posted the full console log (which displayed in the Jenkins server) on 
the paste server:
http://paste.openstack.org/show/434487/

Cloud you give me some guidances to work this out?
Thanks in advance.


Xiexs
__
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] [third-party] [CI] The dsvm-tempest-full job failed

2015-08-31 Thread Xie, Xianshan 
Hi, Abhishek,
   Yes.
   Now, our nodepool can launch slave nodes and add them into Jenkins server 
automatically.
   But unfortunately  there are still same errors.


Xiexs

From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Monday, August 31, 2015 4:07 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [third-party] [CI] The dsvm-tempest-full job failed

Hi Xianshan ,

So after starting nodepool you have configured the slave in Jenkins or it was 
done automatically?

On Mon, Aug 31, 2015 at 1:15 PM, Xie, Xianshan 
<xi...@cn.fujitsu.com<mailto:xi...@cn.fujitsu.com>> wrote:
Hi, all,
  I`m trying to run the job "dsvm-tempest-full" in a slave node which built and 
managed by the nodepool.
But I got the following error messages:
--
14:45:48 + timeout -s 9 174m /opt/stack/new/devstack-gate/devstack-vm-gate.sh
14:45:48 timeout: failed to run command 
‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or directory

...
14:45:48 + echo 'ERROR: the main setup script run by this job failed - exit 
code: 127'
14:45:48 ERROR: the main setup script run by this job failed - exit code: 127
...
14:45:52 No hosts matched
14:45:52 + exit 127
14:45:52 Build step 'Execute shell' marked build as failure
14:45:53 Finished: FAILURE
--
I have no idea what caused this issue.
And furthermore, it seems no more chances to find the detailed information 
about this error,
because the slave node was deleted soon by the nodepool automatically, after 
this job finished.
Is there a setting for the nodepool to prevent the used node being deleted?

I have posted the full console log (which displayed in the Jenkins server) on 
the paste server:
http://paste.openstack.org/show/434487/

Cloud you give me some guidances to work this out?
Thanks in advance.


Xiexs

__
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



--
[图像已被发件人删除。]
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] [third-party] [CI] The dsvm-tempest-full job failed

2015-08-31 Thread Asselin, Ramy 
Hi Xiexs,

After the jobs starts and the nodepool node is marked “used’ use the nodepool 
hold  command.
This will prevent it from being deleted until you do so manually.

Ramy

From: Xie, Xianshan [mailto:xi...@cn.fujitsu.com]
Sent: Monday, August 31, 2015 12:46 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [third-party] [CI] The dsvm-tempest-full job failed

Hi, all,
  I`m trying to run the job "dsvm-tempest-full" in a slave node which built and 
managed by the nodepool.
But I got the following error messages:
--
14:45:48 + timeout -s 9 174m /opt/stack/new/devstack-gate/devstack-vm-gate.sh
14:45:48 timeout: failed to run command 
‘/opt/stack/new/devstack-gate/devstack-vm-gate.sh’: No such file or directory

...
14:45:48 + echo 'ERROR: the main setup script run by this job failed - exit 
code: 127'
14:45:48 ERROR: the main setup script run by this job failed - exit code: 127
...
14:45:52 No hosts matched
14:45:52 + exit 127
14:45:52 Build step 'Execute shell' marked build as failure
14:45:53 Finished: FAILURE
--
I have no idea what caused this issue.
And furthermore, it seems no more chances to find the detailed information 
about this error,
because the slave node was deleted soon by the nodepool automatically, after 
this job finished.
Is there a setting for the nodepool to prevent the used node being deleted?

I have posted the full console log (which displayed in the Jenkins server) on 
the paste server:
http://paste.openstack.org/show/434487/

Cloud you give me some guidances to work this out?
Thanks in advance.


Xiexs
__
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