ovb-fake-caserver job failing, timing out creating the Compute resource

Bug #1684630 reported by Juan Antonio Osorio Robles
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Juan Antonio Osorio Robles

Bug Description

As of April 19, the job started failing with timeouts on the Compute resource, such as the following:

2017-04-20 09:31:12.140949 | 2017-04-20 09:31:08Z [overcloud.Compute.0]: CREATE_FAILED CREATE aborted
2017-04-20 09:31:12.141019 | 2017-04-20 09:31:08Z [overcloud.Compute]: UPDATE_FAILED Operation cancelled
2017-04-20 09:31:12.141039 |
2017-04-20 09:31:12.141069 | Stack overcloud CREATE_FAILED
2017-04-20 09:31:12.141117 |
2017-04-20 09:31:44.305580 | overcloud.Compute.0:
2017-04-20 09:31:44.305945 | resource_type: OS::TripleO::Compute
2017-04-20 09:31:44.306033 | physical_resource_id: 4bffbdbb-0dfe-4683-95a5-066e3eac5e89
2017-04-20 09:31:44.306116 | status: CREATE_FAILED
2017-04-20 09:31:44.306216 | status_reason: |
2017-04-20 09:31:44.306290 | CREATE aborted

It seems that the NetworkDeployment stalled. And there are no logs for the compute node (only for the controller).

Revision history for this message
Juan Antonio Osorio Robles (juan-osorio-robles) wrote :
Changed in tripleo:
status: New → Triaged
importance: Undecided → High
milestone: none → pike-2
Changed in tripleo:
assignee: nobody → Juan Antonio Osorio Robles (juan-osorio-robles)
Revision history for this message
Juan Antonio Osorio Robles (juan-osorio-robles) wrote :

This was fixed by this commit https://review.openstack.org/#/c/458596/

The issue was that the net-iso configuration had changed on CI, when changing that, the original commit didn't fix it for the fakeha-caserver job.

Changed in tripleo:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.