Cleaning error handler not always called during heartbeats

Bug #1485667 reported by Josh Gachnang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic
Fix Released
Medium
Josh Gachnang

Bug Description

If a node is in cleaning and an error occurs during the heartbeat handler, the cleaning_error_handler is not always called (e.g. if Ironic cannot reach the agent). This means the network is not torn down properly and the clean_step is not reset. There are some specific checks in the heartbeat handler, but in the general case the node is just put into CLEANFAIL.

Tags: agent
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ironic (master)

Fix proposed to branch: master
Review: https://review.openstack.org/213769

Changed in ironic:
assignee: nobody → Josh Gachnang (joshnang)
status: New → In Progress
Dmitry Tantsur (divius)
Changed in ironic:
importance: Undecided → Medium
tags: added: agent
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ironic (master)

Reviewed: https://review.openstack.org/213769
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=d1ba1861a862ed49bd301b987ffe1a0b5b6851be
Submitter: Jenkins
Branch: master

commit d1ba1861a862ed49bd301b987ffe1a0b5b6851be
Author: Josh Gachnang <email address hidden>
Date: Mon Aug 17 09:06:06 2015 -0700

    Clean up cleaning error handling on heartbeats

    If a node is in cleaning and an error occurs during the heartbeat
    handler, the cleaning_error_handler is not always called (e.g. if
    Ironic cannot reach the agent). This means the network
    is not torn down properly and the clean_step is not reset. Fix the
    error message that is set in last_error when an error occurs during
    cleaning.

    Change-Id: I22af61b641a49b48b36c8e57750d8db8a9b8cc94
    Closes-Bug: #1485667

Changed in ironic:
status: In Progress → Fix Committed
Changed in ironic:
milestone: none → 4.1.0
status: Fix Committed → 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.