Maintenance not messaging over cluster-host network

Bug #1835268 reported by Eric MacDonald
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
Medium
Eric MacDonald

Bug Description

Maintenance is not resolving the cluster-host ip addresses properly for both the mtcAgent and mtcClient processes. The cluster-host network is used as a messaging backup path between controller and subordinate hosts under a number of failure modes.

Severity: Minor - only corner case failure mode handling is affected.

Steps to Reproduce:
-------------------
Provision a system with a cluster-host network. mtcClient should be sending periodic mtcAlive messages to the active controller over both management and cluster-host networks.

Expected Behavior
------------------
computes send mtcAlive messages to active controller over a provisioned cluster-host network.

Actual Behavior
---------------
No periodic mtcAlive messages are received on the active controller cluster-host network.

Reproducibility
---------------
Reproducible

System Configuration
--------------------
System with provisioned cluster-host network.

Branch/Pull Time/Commit
-----------------------
All since rename of infra to cluster-host network.

Last Pass
---------
This hasn't worked since the cluster network was introduced

Timestamp/Logs
--------------
Not required. Issue is missing messages not error logs.

Changed in starlingx:
assignee: nobody → Eric MacDonald (rocksolidmtce)
Revision history for this message
Ghada Khalil (gkhalil) wrote :

Marking as stx.2.0 gating as this impacts fault detection/handling of the cluster network interface

description: updated
Changed in starlingx:
importance: Undecided → Medium
status: New → Triaged
tags: added: stx.2.0 stx.metal
Changed in starlingx:
status: Triaged → In Progress
Revision history for this message
Eric MacDonald (rocksolidmtce) wrote :
Revision history for this message
Ghada Khalil (gkhalil) wrote :

Marking as Fix Released.
This was not updated automatically as the wrong bug was specified in the commit msg (835268 instead of 1835268)

Dariush Eslimi (deslimi)
Changed in starlingx:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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