NODE_FAILURES when running tripleo-ci-centos-9-scenario010-standalone on opendev

Bug #1990269 reported by Ronelle Landy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Critical
Unassigned

Bug Description

There are NODE_FAILURE errors showing up on tripleo-ci-centos-9-scenario010-standalone
since 09/17:

https://zuul.openstack.org/builds?job_name=tripleo-ci-centos-9-scenario010-standalone+&skip=0

There are no logs so had to tell what is happening.

This job uses nodeset: single-centos-9-node-nested-virt - so assumption is that it's the nest-virt nodeset

https://zuul.openstack.org/builds?job_name=tripleo-ci-centos-8-scenario010-standalone+&skip=0 -looked ok until 09/15.

Ronelle Landy (rlandy)
Changed in tripleo:
milestone: none → zed-1
importance: Undecided → Critical
status: New → Triaged
tags: added: promotion-blocker
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to tripleo-ci (master)

Related fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/tripleo-ci/+/858528

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tripleo-ci (master)

Change abandoned by "amolkahat <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/tripleo-ci/+/858528
Reason: Not needed.

Revision history for this message
Amol Kahat (amolkahat) wrote :

Fix merged: https://review.opendev.org/c/openstack/project-config/+/858523

We are no longer seeing this issue. Closing bug.

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.