Re: [openstack-dev] Hyper-V Nova CI Infrastructure

2015-03-02 Thread Anita Kuno 
On 03/01/2015 09:13 PM, kwon-ho lee wrote:
> Hello, OpenStack dev members,
> 
> Is there any problem on "Hyper-V Nova CI Infrastructure"?
> 
> I don't know why i failed my petch set.
> 
> My first patch set was succeeded , and then i changed the commit message,
> then failed on Hyper-V test.
> 
> Could you tell me the reason?
> 
> Here is my test result links.
> http://64.119.130.115/156126/4/
> 
> Thanks
> Kwonho
> 
> 
> 
> __
> 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
> 
Thank you for asking the question Kwonho.

I investigated this system and talked with one of the operators. The
system is offline now, you can track the status of the system on their
third party system wikipage:
https://wiki.openstack.org/wiki/ThirdPartySystems/Hyper-V_CI

Thank you,
Anita.

__
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] Hyper-V Nova CI Infrastructure

2014-02-03 Thread Monty Taylor 

On 01/29/2014 11:10 PM, Matt Riedemann wrote:



On Monday, January 27, 2014 7:17:27 AM, Alessandro Pilotti wrote:

On 25 Jan 2014, at 16:51 , Matt Riedemann 
wrote:




On 1/24/2014 3:41 PM, Peter Pouliot wrote:

Hello OpenStack Community,

I am excited at this opportunity to make the community aware that the
Hyper-V CI infrastructure

is now up and running.  Let’s first start with some housekeeping
details.  Our Tempest logs are

publically available here: http://64.119.130.115. You will see them
show
up in any

Nova Gerrit commit from this moment on.



So now some questions. :)

I saw this failed on one of my nova patches [1].  It says the build
succeeded but that the tests failed.  I talked with Alessandro about
this yesterday and he said that's working as designed, something with
how the scoring works with zuul?


I spoke with clarkb on infra, since we were also very puzzled by this
behaviour. I’ve been told that when the job is non voting, it’s always
reported as succeeded, which makes sense, although sligltly misleading.
The message in the Gerrit comment is clearly stating: "Test run failed
in ..m ..s (non-voting)”, so this should be fair enough. It’d be great
to have a way to get rid of the “Build succeded” message above.


The problem I'm having is figuring out why it failed.  I looked at
the compute logs but didn't find any errors.  Can someone help me
figure out what went wrong here?



The reason for the failure of this job can be found here:

http://64.119.130.115/69047/1/devstack_logs/screen-n-api.log.gz

Please search for "(1054, "Unknown column 'instances.locked_by' in
'field list'")"

In this case the job failed when "nova service-list” got called to
verify wether the compute nodes have been properly added to the
devstack instance in the overcloud.

During the weekend we added also a console.log to help in simplifying
debugging, especially in the rare cases in which the job fails before
getting to run tempest:

http://64.119.130.115/69047/1/console.log.gz


Let me know if this helps in tracking down your issue!

Alessandro



[1] https://review.openstack.org/#/c/69047/1

--

Thanks,

Matt Riedemann


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



Alex, thanks, figured it out and yes, the console log is helpful, and
the fail was a real bug in my patch which changed how the 180 migration
was doing something which later broke another migration running against
your MySQL backend - so nice catch.


WOOT! I can't even tell you how excited I am that we're catching real 
bugs here. (honestly, if we weren't then all of this extra work we've 
put people through would be kinda depressing)



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Hyper-V Nova CI Infrastructure

2014-02-03 Thread Alessandro Pilotti 

On 02 Feb 2014, at 23:10 , Alessandro Pilotti  
wrote:

> 
> On 02 Feb 2014, at 23:01 , Michael Still  wrote:
> 
>> It seems like there were a lot of failing Hyper-V CI jobs for nova
>> yesterday. Is there some systemic problem or did all those patches
>> really fail? An example: https://review.openstack.org/#/c/66291/
>> 
> 
> 
> We’re awere of this issue and looking into it. The issue happens in devstack 
> before the Hyper-V compute nodes are added and before tempests starts.
> 
> I’ll post an update as soon as we get it sorted out.
> 

Fixed the issue. The reason was related to the following devstack patch which 
now binds by default the keystone
private port 35357 to $SERVICE_HOST. Our config was errornously using the 
private port instead of the public one
in OS_AUTH_URL to connect to 127.0.0.1, hence the sudded failures. 

https://github.com/openstack-dev/devstack/commit/6c57fbab26e40af5c5b19b46fb3da39341f34dab

Alessandro


> 
> Thanks,
> 
> Alessandro
> 
> 
>> Michael
>> 
>> On Mon, Feb 3, 2014 at 7:21 AM, Alessandro Pilotti
>>  wrote:
>>> Hi Michael,
>>> 
>>> 
>>> On 02 Feb 2014, at 06:19 , Michael Still  wrote:
>>> 
 I saw another case of the "build succeeded" message for a failure just
 now... https://review.openstack.org/#/c/59101/ has a rebase failure
 but was marked as successful.
 
 Is this another case of hyper-v not being voting and therefore being a
 bit confusing? The text of the comment clearly indicates this is a
 failure at least.
 
>>> 
>>> Yes, all the Hyper-V CI messages start with "build succeded", while the 
>>> next lines show the actual job result.
>>> I asked on infra about how to get rid of that message, but from what I got 
>>> from the chat it is not possible as long as the CI is non voting 
>>> independently from the return status of the single jobs.
>>> 
>>> Alessandro
>>> 
>>> 
 Thanks,
 Michael
 
 On Tue, Jan 28, 2014 at 12:17 AM, Alessandro Pilotti
  wrote:
> On 25 Jan 2014, at 16:51 , Matt Riedemann  
> wrote:
> 
>> 
>> 
>> On 1/24/2014 3:41 PM, Peter Pouliot wrote:
>>> Hello OpenStack Community,
>>> 
>>> I am excited at this opportunity to make the community aware that the
>>> Hyper-V CI infrastructure
>>> 
>>> is now up and running.  Let's first start with some housekeeping
>>> details.  Our Tempest logs are
>>> 
>>> publically available here: http://64.119.130.115. You will see them show
>>> up in any
>>> 
>>> Nova Gerrit commit from this moment on.
>>> 
>> 
>> So now some questions. :)
>> 
>> I saw this failed on one of my nova patches [1].  It says the build 
>> succeeded but that the tests failed.  I talked with Alessandro about 
>> this yesterday and he said that's working as designed, something with 
>> how the scoring works with zuul?
> 
> I spoke with clarkb on infra, since we were also very puzzled by this 
> behaviour. I've been told that when the job is non voting, it's always 
> reported as succeeded, which makes sense, although sligltly misleading.
> The message in the Gerrit comment is clearly stating: "Test run failed in 
> ..m ..s (non-voting)", so this should be fair enough. It'd be great to 
> have a way to get rid of the "Build succeded" message above.
> 
>> The problem I'm having is figuring out why it failed.  I looked at the 
>> compute logs but didn't find any errors.  Can someone help me figure out 
>> what went wrong here?
>> 
> 
> The reason for the failure of this job can be found here:
> 
> http://64.119.130.115/69047/1/devstack_logs/screen-n-api.log.gz
> 
> Please search for "(1054, "Unknown column 'instances.locked_by' in 'field 
> list'")"
> 
> In this case the job failed when "nova service-list" got called to verify 
> wether the compute nodes have been properly added to the devstack 
> instance in the overcloud.
> 
> During the weekend we added also a console.log to help in simplifying 
> debugging, especially in the rare cases in which the job fails before 
> getting to run tempest:
> 
> http://64.119.130.115/69047/1/console.log.gz
> 
> 
> Let me know if this helps in tracking down your issue!
> 
> Alessandro
> 
> 
>> [1] https://review.openstack.org/#/c/69047/1
>> 
>> --
>> 
>> Thanks,
>> 
>> Matt Riedemann
>> 
>> 
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
 
 
 --
 Rackspace Australia

Re: [openstack-dev] Hyper-V Nova CI Infrastructure

2014-02-02 Thread Alessandro Pilotti 

On 02 Feb 2014, at 23:01 , Michael Still  wrote:

> It seems like there were a lot of failing Hyper-V CI jobs for nova
> yesterday. Is there some systemic problem or did all those patches
> really fail? An example: https://review.openstack.org/#/c/66291/
> 


We’re awere of this issue and looking into it. The issue happens in devstack 
before the Hyper-V compute nodes are added and before tempests starts.

I’ll post an update as soon as we get it sorted out.


Thanks,

Alessandro


> Michael
> 
> On Mon, Feb 3, 2014 at 7:21 AM, Alessandro Pilotti
>  wrote:
>> Hi Michael,
>> 
>> 
>> On 02 Feb 2014, at 06:19 , Michael Still  wrote:
>> 
>>> I saw another case of the "build succeeded" message for a failure just
>>> now... https://review.openstack.org/#/c/59101/ has a rebase failure
>>> but was marked as successful.
>>> 
>>> Is this another case of hyper-v not being voting and therefore being a
>>> bit confusing? The text of the comment clearly indicates this is a
>>> failure at least.
>>> 
>> 
>> Yes, all the Hyper-V CI messages start with "build succeded", while the next 
>> lines show the actual job result.
>> I asked on infra about how to get rid of that message, but from what I got 
>> from the chat it is not possible as long as the CI is non voting 
>> independently from the return status of the single jobs.
>> 
>> Alessandro
>> 
>> 
>>> Thanks,
>>> Michael
>>> 
>>> On Tue, Jan 28, 2014 at 12:17 AM, Alessandro Pilotti
>>>  wrote:
 On 25 Jan 2014, at 16:51 , Matt Riedemann  
 wrote:
 
> 
> 
> On 1/24/2014 3:41 PM, Peter Pouliot wrote:
>> Hello OpenStack Community,
>> 
>> I am excited at this opportunity to make the community aware that the
>> Hyper-V CI infrastructure
>> 
>> is now up and running.  Let's first start with some housekeeping
>> details.  Our Tempest logs are
>> 
>> publically available here: http://64.119.130.115. You will see them show
>> up in any
>> 
>> Nova Gerrit commit from this moment on.
>> 
> 
> So now some questions. :)
> 
> I saw this failed on one of my nova patches [1].  It says the build 
> succeeded but that the tests failed.  I talked with Alessandro about this 
> yesterday and he said that's working as designed, something with how the 
> scoring works with zuul?
 
 I spoke with clarkb on infra, since we were also very puzzled by this 
 behaviour. I've been told that when the job is non voting, it's always 
 reported as succeeded, which makes sense, although sligltly misleading.
 The message in the Gerrit comment is clearly stating: "Test run failed in 
 ..m ..s (non-voting)", so this should be fair enough. It'd be great to 
 have a way to get rid of the "Build succeded" message above.
 
> The problem I'm having is figuring out why it failed.  I looked at the 
> compute logs but didn't find any errors.  Can someone help me figure out 
> what went wrong here?
> 
 
 The reason for the failure of this job can be found here:
 
 http://64.119.130.115/69047/1/devstack_logs/screen-n-api.log.gz
 
 Please search for "(1054, "Unknown column 'instances.locked_by' in 'field 
 list'")"
 
 In this case the job failed when "nova service-list" got called to verify 
 wether the compute nodes have been properly added to the devstack instance 
 in the overcloud.
 
 During the weekend we added also a console.log to help in simplifying 
 debugging, especially in the rare cases in which the job fails before 
 getting to run tempest:
 
 http://64.119.130.115/69047/1/console.log.gz
 
 
 Let me know if this helps in tracking down your issue!
 
 Alessandro
 
 
> [1] https://review.openstack.org/#/c/69047/1
> 
> --
> 
> Thanks,
> 
> Matt Riedemann
> 
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> 
>>> 
>>> 
>>> --
>>> Rackspace Australia
>>> 
>>> ___
>>> OpenStack-dev mailing list
>>> OpenStack-dev@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> 
>> 
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> -- 
> Rackspace Australia
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___

Re: [openstack-dev] Hyper-V Nova CI Infrastructure

2014-02-02 Thread Michael Still 
It seems like there were a lot of failing Hyper-V CI jobs for nova
yesterday. Is there some systemic problem or did all those patches
really fail? An example: https://review.openstack.org/#/c/66291/

Michael

On Mon, Feb 3, 2014 at 7:21 AM, Alessandro Pilotti
 wrote:
> Hi Michael,
>
>
> On 02 Feb 2014, at 06:19 , Michael Still  wrote:
>
>> I saw another case of the "build succeeded" message for a failure just
>> now... https://review.openstack.org/#/c/59101/ has a rebase failure
>> but was marked as successful.
>>
>> Is this another case of hyper-v not being voting and therefore being a
>> bit confusing? The text of the comment clearly indicates this is a
>> failure at least.
>>
>
> Yes, all the Hyper-V CI messages start with "build succeded", while the next 
> lines show the actual job result.
> I asked on infra about how to get rid of that message, but from what I got 
> from the chat it is not possible as long as the CI is non voting 
> independently from the return status of the single jobs.
>
> Alessandro
>
>
>> Thanks,
>> Michael
>>
>> On Tue, Jan 28, 2014 at 12:17 AM, Alessandro Pilotti
>>  wrote:
>>> On 25 Jan 2014, at 16:51 , Matt Riedemann  
>>> wrote:
>>>


 On 1/24/2014 3:41 PM, Peter Pouliot wrote:
> Hello OpenStack Community,
>
> I am excited at this opportunity to make the community aware that the
> Hyper-V CI infrastructure
>
> is now up and running.  Let's first start with some housekeeping
> details.  Our Tempest logs are
>
> publically available here: http://64.119.130.115. You will see them show
> up in any
>
> Nova Gerrit commit from this moment on.
> 

 So now some questions. :)

 I saw this failed on one of my nova patches [1].  It says the build 
 succeeded but that the tests failed.  I talked with Alessandro about this 
 yesterday and he said that's working as designed, something with how the 
 scoring works with zuul?
>>>
>>> I spoke with clarkb on infra, since we were also very puzzled by this 
>>> behaviour. I've been told that when the job is non voting, it's always 
>>> reported as succeeded, which makes sense, although sligltly misleading.
>>> The message in the Gerrit comment is clearly stating: "Test run failed in 
>>> ..m ..s (non-voting)", so this should be fair enough. It'd be great to have 
>>> a way to get rid of the "Build succeded" message above.
>>>
 The problem I'm having is figuring out why it failed.  I looked at the 
 compute logs but didn't find any errors.  Can someone help me figure out 
 what went wrong here?

>>>
>>> The reason for the failure of this job can be found here:
>>>
>>> http://64.119.130.115/69047/1/devstack_logs/screen-n-api.log.gz
>>>
>>> Please search for "(1054, "Unknown column 'instances.locked_by' in 'field 
>>> list'")"
>>>
>>> In this case the job failed when "nova service-list" got called to verify 
>>> wether the compute nodes have been properly added to the devstack instance 
>>> in the overcloud.
>>>
>>> During the weekend we added also a console.log to help in simplifying 
>>> debugging, especially in the rare cases in which the job fails before 
>>> getting to run tempest:
>>>
>>> http://64.119.130.115/69047/1/console.log.gz
>>>
>>>
>>> Let me know if this helps in tracking down your issue!
>>>
>>> Alessandro
>>>
>>>
 [1] https://review.openstack.org/#/c/69047/1

 --

 Thanks,

 Matt Riedemann


 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>> ___
>>> OpenStack-dev mailing list
>>> OpenStack-dev@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>> --
>> Rackspace Australia
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Rackspace Australia

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Hyper-V Nova CI Infrastructure

2014-02-02 Thread Alessandro Pilotti 
Hi Michael,


On 02 Feb 2014, at 06:19 , Michael Still  wrote:

> I saw another case of the "build succeeded" message for a failure just
> now... https://review.openstack.org/#/c/59101/ has a rebase failure
> but was marked as successful.
> 
> Is this another case of hyper-v not being voting and therefore being a
> bit confusing? The text of the comment clearly indicates this is a
> failure at least.
> 

Yes, all the Hyper-V CI messages start with “build succeded”, while the next 
lines show the actual job result.
I asked on infra about how to get rid of that message, but from what I got from 
the chat it is not possible as long as the CI is non voting independently from 
the return status of the single jobs.

Alessandro


> Thanks,
> Michael
> 
> On Tue, Jan 28, 2014 at 12:17 AM, Alessandro Pilotti
>  wrote:
>> On 25 Jan 2014, at 16:51 , Matt Riedemann  wrote:
>> 
>>> 
>>> 
>>> On 1/24/2014 3:41 PM, Peter Pouliot wrote:
 Hello OpenStack Community,
 
 I am excited at this opportunity to make the community aware that the
 Hyper-V CI infrastructure
 
 is now up and running.  Let's first start with some housekeeping
 details.  Our Tempest logs are
 
 publically available here: http://64.119.130.115. You will see them show
 up in any
 
 Nova Gerrit commit from this moment on.
 
>>> 
>>> So now some questions. :)
>>> 
>>> I saw this failed on one of my nova patches [1].  It says the build 
>>> succeeded but that the tests failed.  I talked with Alessandro about this 
>>> yesterday and he said that's working as designed, something with how the 
>>> scoring works with zuul?
>> 
>> I spoke with clarkb on infra, since we were also very puzzled by this 
>> behaviour. I've been told that when the job is non voting, it's always 
>> reported as succeeded, which makes sense, although sligltly misleading.
>> The message in the Gerrit comment is clearly stating: "Test run failed in 
>> ..m ..s (non-voting)", so this should be fair enough. It'd be great to have 
>> a way to get rid of the "Build succeded" message above.
>> 
>>> The problem I'm having is figuring out why it failed.  I looked at the 
>>> compute logs but didn't find any errors.  Can someone help me figure out 
>>> what went wrong here?
>>> 
>> 
>> The reason for the failure of this job can be found here:
>> 
>> http://64.119.130.115/69047/1/devstack_logs/screen-n-api.log.gz
>> 
>> Please search for "(1054, "Unknown column 'instances.locked_by' in 'field 
>> list'")"
>> 
>> In this case the job failed when "nova service-list" got called to verify 
>> wether the compute nodes have been properly added to the devstack instance 
>> in the overcloud.
>> 
>> During the weekend we added also a console.log to help in simplifying 
>> debugging, especially in the rare cases in which the job fails before 
>> getting to run tempest:
>> 
>> http://64.119.130.115/69047/1/console.log.gz
>> 
>> 
>> Let me know if this helps in tracking down your issue!
>> 
>> Alessandro
>> 
>> 
>>> [1] https://review.openstack.org/#/c/69047/1
>>> 
>>> --
>>> 
>>> Thanks,
>>> 
>>> Matt Riedemann
>>> 
>>> 
>>> ___
>>> OpenStack-dev mailing list
>>> OpenStack-dev@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> 
>> 
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> -- 
> Rackspace Australia
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Hyper-V Nova CI Infrastructure

2014-02-01 Thread Michael Still 
I saw another case of the "build succeeded" message for a failure just
now... https://review.openstack.org/#/c/59101/ has a rebase failure
but was marked as successful.

Is this another case of hyper-v not being voting and therefore being a
bit confusing? The text of the comment clearly indicates this is a
failure at least.

Thanks,
Michael

On Tue, Jan 28, 2014 at 12:17 AM, Alessandro Pilotti
 wrote:
> On 25 Jan 2014, at 16:51 , Matt Riedemann  wrote:
>
>>
>>
>> On 1/24/2014 3:41 PM, Peter Pouliot wrote:
>>> Hello OpenStack Community,
>>>
>>> I am excited at this opportunity to make the community aware that the
>>> Hyper-V CI infrastructure
>>>
>>> is now up and running.  Let's first start with some housekeeping
>>> details.  Our Tempest logs are
>>>
>>> publically available here: http://64.119.130.115. You will see them show
>>> up in any
>>>
>>> Nova Gerrit commit from this moment on.
>>> 
>>
>> So now some questions. :)
>>
>> I saw this failed on one of my nova patches [1].  It says the build 
>> succeeded but that the tests failed.  I talked with Alessandro about this 
>> yesterday and he said that's working as designed, something with how the 
>> scoring works with zuul?
>
> I spoke with clarkb on infra, since we were also very puzzled by this 
> behaviour. I've been told that when the job is non voting, it's always 
> reported as succeeded, which makes sense, although sligltly misleading.
> The message in the Gerrit comment is clearly stating: "Test run failed in ..m 
> ..s (non-voting)", so this should be fair enough. It'd be great to have a way 
> to get rid of the "Build succeded" message above.
>
>> The problem I'm having is figuring out why it failed.  I looked at the 
>> compute logs but didn't find any errors.  Can someone help me figure out 
>> what went wrong here?
>>
>
> The reason for the failure of this job can be found here:
>
> http://64.119.130.115/69047/1/devstack_logs/screen-n-api.log.gz
>
> Please search for "(1054, "Unknown column 'instances.locked_by' in 'field 
> list'")"
>
> In this case the job failed when "nova service-list" got called to verify 
> wether the compute nodes have been properly added to the devstack instance in 
> the overcloud.
>
> During the weekend we added also a console.log to help in simplifying 
> debugging, especially in the rare cases in which the job fails before getting 
> to run tempest:
>
> http://64.119.130.115/69047/1/console.log.gz
>
>
> Let me know if this helps in tracking down your issue!
>
> Alessandro
>
>
>> [1] https://review.openstack.org/#/c/69047/1
>>
>> --
>>
>> Thanks,
>>
>> Matt Riedemann
>>
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Rackspace Australia

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Hyper-V Nova CI Infrastructure

2014-01-29 Thread Matt Riedemann 



On Monday, January 27, 2014 7:17:27 AM, Alessandro Pilotti wrote:

On 25 Jan 2014, at 16:51 , Matt Riedemann  wrote:




On 1/24/2014 3:41 PM, Peter Pouliot wrote:

Hello OpenStack Community,

I am excited at this opportunity to make the community aware that the
Hyper-V CI infrastructure

is now up and running.  Let’s first start with some housekeeping
details.  Our Tempest logs are

publically available here: http://64.119.130.115. You will see them show
up in any

Nova Gerrit commit from this moment on.



So now some questions. :)

I saw this failed on one of my nova patches [1].  It says the build succeeded 
but that the tests failed.  I talked with Alessandro about this yesterday and 
he said that's working as designed, something with how the scoring works with 
zuul?


I spoke with clarkb on infra, since we were also very puzzled by this 
behaviour. I’ve been told that when the job is non voting, it’s always reported 
as succeeded, which makes sense, although sligltly misleading.
The message in the Gerrit comment is clearly stating: "Test run failed in ..m 
..s (non-voting)”, so this should be fair enough. It’d be great to have a way to get 
rid of the “Build succeded” message above.


The problem I'm having is figuring out why it failed.  I looked at the compute 
logs but didn't find any errors.  Can someone help me figure out what went 
wrong here?



The reason for the failure of this job can be found here:

http://64.119.130.115/69047/1/devstack_logs/screen-n-api.log.gz

Please search for "(1054, "Unknown column 'instances.locked_by' in 'field 
list'")"

In this case the job failed when "nova service-list” got called to verify 
wether the compute nodes have been properly added to the devstack instance in the 
overcloud.

During the weekend we added also a console.log to help in simplifying 
debugging, especially in the rare cases in which the job fails before getting 
to run tempest:

http://64.119.130.115/69047/1/console.log.gz


Let me know if this helps in tracking down your issue!

Alessandro



[1] https://review.openstack.org/#/c/69047/1

--

Thanks,

Matt Riedemann


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



Alex, thanks, figured it out and yes, the console log is helpful, and 
the fail was a real bug in my patch which changed how the 180 migration 
was doing something which later broke another migration running against 
your MySQL backend - so nice catch.


--

Thanks,

Matt Riedemann


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Hyper-V Nova CI Infrastructure

2014-01-27 Thread Alessandro Pilotti 
On 25 Jan 2014, at 16:51 , Matt Riedemann  wrote:

> 
> 
> On 1/24/2014 3:41 PM, Peter Pouliot wrote:
>> Hello OpenStack Community,
>> 
>> I am excited at this opportunity to make the community aware that the
>> Hyper-V CI infrastructure
>> 
>> is now up and running.  Let’s first start with some housekeeping
>> details.  Our Tempest logs are
>> 
>> publically available here: http://64.119.130.115. You will see them show
>> up in any
>> 
>> Nova Gerrit commit from this moment on.
>> 
> 
> So now some questions. :)
> 
> I saw this failed on one of my nova patches [1].  It says the build succeeded 
> but that the tests failed.  I talked with Alessandro about this yesterday and 
> he said that's working as designed, something with how the scoring works with 
> zuul?  

I spoke with clarkb on infra, since we were also very puzzled by this 
behaviour. I’ve been told that when the job is non voting, it’s always reported 
as succeeded, which makes sense, although sligltly misleading. 
The message in the Gerrit comment is clearly stating: "Test run failed in ..m 
..s (non-voting)”, so this should be fair enough. It’d be great to have a way 
to get rid of the “Build succeded” message above.

> The problem I'm having is figuring out why it failed.  I looked at the 
> compute logs but didn't find any errors.  Can someone help me figure out what 
> went wrong here?
> 

The reason for the failure of this job can be found here:

http://64.119.130.115/69047/1/devstack_logs/screen-n-api.log.gz

Please search for "(1054, "Unknown column 'instances.locked_by' in 'field 
list'")"

In this case the job failed when "nova service-list” got called to verify 
wether the compute nodes have been properly added to the devstack instance in 
the overcloud. 

During the weekend we added also a console.log to help in simplifying 
debugging, especially in the rare cases in which the job fails before getting 
to run tempest:

http://64.119.130.115/69047/1/console.log.gz


Let me know if this helps in tracking down your issue!

Alessandro


> [1] https://review.openstack.org/#/c/69047/1
> 
> -- 
> 
> Thanks,
> 
> Matt Riedemann
> 
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Hyper-V Nova CI Infrastructure

2014-01-27 Thread Alessandro Pilotti 

On 25 Jan 2014, at 00:25 , Russell Bryant  wrote:

> On 01/24/2014 04:41 PM, Peter Pouliot wrote:
>> Hello OpenStack Community,
>> 
>> 
>> 
>> I am excited at this opportunity to make the community aware that the
>> Hyper-V CI infrastructure
>> 
>> is now up and running.  Let’s first start with some housekeeping
>> details.  Our Tempest logs are
>> 
>> publically available here:  http://64.119.130.115. You will see them
>> show up in any
>> 
>> Nova Gerrit commit from this moment on.
> 
> Congratulations!!
> 
> Thank you all for your hard work on this.  I know it wasn't easy.  This
> is huge progress and will help make Hyper-V support, as well OpenStack
> overall in general, better.
> 
> I also really appreciate the openness with the tooling you used to make
> this all work.
> 
> Really, excellent work.
> 

Thanks Russell! :-) 


> -- 
> Russell Bryant
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Hyper-V Nova CI Infrastructure

2014-01-25 Thread Matt Riedemann 



On 1/24/2014 3:41 PM, Peter Pouliot wrote:

Hello OpenStack Community,

I am excited at this opportunity to make the community aware that the
Hyper-V CI infrastructure

is now up and running.  Let’s first start with some housekeeping
details.  Our Tempest logs are

publically available here: http://64.119.130.115. You will see them show
up in any

Nova Gerrit commit from this moment on.

Additionally if anyone is interested, all of the infrastructure and
automation

work can be found in the following locations:

http://github.com/openstack-hyper-v

http://github.com/cloudbase

Furthermore I would like to take a moment thank the team that made this
moment possible.

This is our first step, and as such was an incredible learning process
for everyone involved.

We were able to accomplish something that most thought couldn’t be done.

I would personally like to take some time thank those individuals whose
tireless effort helped get us to this stage.

Alessandro Pilotti 

Hashir Abdi 

Octavian Ciuhandu 

Nick Meier 

Gabriel Samfira 

Tim Rogers 

Claudiu Neșa 

Vijay Tripathy mailto:vij...@microsoft.com>>

Thank you for the time and effort you put forth to get us to this
milestone. Without each

of you this would not have been possible. I look forward to continuing
the progress and evolving

the infrastructure to the next level.  Our job is not done, but we are
now on the right path.

Thank you all.

I would also at this time like to thank the OpenStack community for your
patience and guidance

through this process.   There are too many of you who helped, instructed
or guided us along the

way to list here.  I hope we can rely on your continued support going
forward as we progress

through this journey including CI testing for all the OpenStack projects
where Microsoft

technologies are involved.

Peter J. Pouliot CISSP

Sr. SDET OpenStack

Microsoft

New England Research & Development Center

1 Memorial Drive

Cambridge, MA 02142

P: 1.(857).4536436

E: ppoul...@microsoft.com 

IRC: primeministerp



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



So now some questions. :)

I saw this failed on one of my nova patches [1].  It says the build 
succeeded but that the tests failed.  I talked with Alessandro about 
this yesterday and he said that's working as designed, something with 
how the scoring works with zuul?  The problem I'm having is figuring out 
why it failed.  I looked at the compute logs but didn't find any errors. 
 Can someone help me figure out what went wrong here?


[1] https://review.openstack.org/#/c/69047/1

--

Thanks,

Matt Riedemann


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Hyper-V Nova CI Infrastructure

2014-01-24 Thread Russell Bryant 
On 01/24/2014 04:41 PM, Peter Pouliot wrote:
> Hello OpenStack Community,
> 
>  
> 
> I am excited at this opportunity to make the community aware that the
> Hyper-V CI infrastructure
> 
> is now up and running.  Let’s first start with some housekeeping
> details.  Our Tempest logs are
> 
> publically available here:  http://64.119.130.115. You will see them
> show up in any
> 
> Nova Gerrit commit from this moment on.

Congratulations!!

Thank you all for your hard work on this.  I know it wasn't easy.  This
is huge progress and will help make Hyper-V support, as well OpenStack
overall in general, better.

I also really appreciate the openness with the tooling you used to make
this all work.

Really, excellent work.

-- 
Russell Bryant

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Hyper-V Nova CI Infrastructure

2014-01-24 Thread Matt Riedemann 



On Friday, January 24, 2014 3:41:59 PM, Peter Pouliot wrote:

Hello OpenStack Community,

I am excited at this opportunity to make the community aware that the
Hyper-V CI infrastructure

is now up and running.  Let’s first start with some housekeeping
details.  Our Tempest logs are

publically available here: http://64.119.130.115. You will see them
show up in any

Nova Gerrit commit from this moment on.

Additionally if anyone is interested, all of the infrastructure and
automation

work can be found in the following locations:

http://github.com/openstack-hyper-v

http://github.com/cloudbase

Furthermore I would like to take a moment thank the team that made
this moment possible.

This is our first step, and as such was an incredible learning process
for everyone involved.

We were able to accomplish something that most thought couldn’t be done.

I would personally like to take some time thank those individuals
whose tireless effort helped get us to this stage.

Alessandro Pilotti 

Hashir Abdi 

Octavian Ciuhandu 

Nick Meier 

Gabriel Samfira 

Tim Rogers 

Claudiu Neșa 

Vijay Tripathy mailto:vij...@microsoft.com>>

Thank you for the time and effort you put forth to get us to this
milestone. Without each

of you this would not have been possible. I look forward to continuing
the progress and evolving

the infrastructure to the next level.  Our job is not done, but we are
now on the right path.

Thank you all.

I would also at this time like to thank the OpenStack community for
your patience and guidance

through this process.   There are too many of you who helped,
instructed or guided us along the

way to list here.  I hope we can rely on your continued support going
forward as we progress

through this journey including CI testing for all the OpenStack
projects where Microsoft

technologies are involved.

Peter J. Pouliot CISSP

Sr. SDET OpenStack

Microsoft

New England Research & Development Center

1 Memorial Drive

Cambridge, MA 02142

P: 1.(857).4536436

E: ppoul...@microsoft.com 

IRC: primeministerp



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Nice work, this is great to see.  Congratulations to the whole team 
that worked on making this happen!


--

Thanks,

Matt Riedemann


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev