On 04/25/2017 05:31 AM, Anil Belur wrote:
> Hi Lori,
> 
> This is possibly happening because sometimes stacks are not getting removed 
> efficiently on RS, I have cleared up stale nodes
> on rackspace earlier today.

Can we automate this "clearing up stale nodes" somehow, and run it 
periodically? I am pretty
sure the answer is no, as I vaguely remember Thanh telling me that before. But, 
it would
sure help hide these problems from us.

> This is issue on RS side and nothing we could do other than retriggering the 
> job. 

does RackSpace have some work item to fix these issues? We do pay for their 
product and
this is an ongoing problem.

> I have retriggered the job now which is going through (but unstable due to 
> test case failures.)
> https://jenkins.opendaylight.org/releng/view/01-Recent/job/lispflowmapping-csit-3node-msmr-all-carbon/214/
>  

Thanks Anil for the support and being one of our RackSpace middle persons :)

JamO


> Thanks,
> Anil
> 
> 
> 
> On Tue, Apr 25, 2017 at 4:12 PM, Lori Jakab <[email protected] 
> <mailto:[email protected]>> wrote:
> 
>     Hi,
> 
>     I see the following failures quite often. Is it a known issue, are the 
> root causes know, can we do anything about them?
> 
>     *03:04:21* Trying up to 3 times to create 
> releng-lispflowmapping-csit-3node-msmr-only-boron-255.
>     *03:04:29* 
> +---------------------+-------------------------------------------------------+
>     *03:04:29* | Field               | Value                                  
>                |
>     *03:04:29* 
> +---------------------+-------------------------------------------------------+
>     *03:04:29* | id                  | cbb5fb3f-9136-4593-8b54-f0af1df72574   
>                |
>     *03:04:29* | stack_name          | 
> releng-lispflowmapping-csit-3node-msmr-only-boron-255 |
>     *03:04:29* | description         | No description                         
>                |
>     *03:04:29* | creation_time       | 2017-04-25T00:04:29                    
>                |
>     *03:04:29* | updated_time        | None                                   
>                |
>     *03:04:29* | stack_status        | CREATE_IN_PROGRESS                     
>                |
>     *03:04:29* | stack_status_reason | Stack CREATE started                   
>                |
>     *03:04:29* 
> +---------------------+-------------------------------------------------------+
>     *03:04:29* 1: Waiting for 10 minutes to create 
> releng-lispflowmapping-csit-3node-msmr-only-boron-255.
>     *03:05:34* 1: CREATE_IN_PROGRESS
>     *03:05:34* Waiting to initialize infrastructure.
>     *03:06:39* 2: CREATE_IN_PROGRESS
>     *03:06:39* Waiting to initialize infrastructure.
>     *03:07:44* 3: CREATE_IN_PROGRESS
>     *03:07:44* Waiting to initialize infrastructure.
>     *03:08:48* 4: CREATE_IN_PROGRESS
>     *03:08:48* Waiting to initialize infrastructure.
>     *03:09:53* 5: CREATE_IN_PROGRESS
>     *03:09:53* Waiting to initialize infrastructure.
>     *03:10:57* 6: CREATE_IN_PROGRESS
>     *03:10:57* Waiting to initialize infrastructure.
>     *03:12:00* 7: CREATE_IN_PROGRESS
>     *03:12:00* Waiting to initialize infrastructure.
>     *03:13:04* 8: CREATE_IN_PROGRESS
>     *03:13:04* Waiting to initialize infrastructure.
>     *03:14:07* 9: CREATE_IN_PROGRESS
>     *03:14:07* Waiting to initialize infrastructure.
>     *03:15:09* 10: CREATE_FAILED
>     *03:15:09* ERROR: Failed to initialize infrastructure. Deleting stack and 
> possibly retrying to create...
> 
> 
>     -Lori
> 
> 
>     _______________________________________________
>     release mailing list
>     [email protected] <mailto:[email protected]>
>     https://lists.opendaylight.org/mailman/listinfo/release 
> <https://lists.opendaylight.org/mailman/listinfo/release>
> 
> 
> 
> 
> _______________________________________________
> release mailing list
> [email protected]
> https://lists.opendaylight.org/mailman/listinfo/release
> 
_______________________________________________
infrastructure mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/infrastructure

Reply via email to