DC system bootstrap failing because of RabbitMQ having timeout issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Samuel Presa Toledo |
Bug Description
Brief Description
-----------------
[1] describes a 10s timeout behavior running "rabbitmqctl wait". Analyzing
the rabbit logs from a Distributed Cloud system that was presenting rabbit
startup issues, it looks the startup time for rabbit was taking around
8.5s. Based on the 10s timeout behavior issue from [1], the rabbit service
stop working after reboot controller-0 from a DC system triggered by
deployment manager execution.
This was observed in some DC Systems.
1 - https:/
Severity
--------
<Critical: System/Feature is not usable due to the defect>
Steps to Reproduce
------------------
sm-unmanage service rabbit
sm-manage service rabbit
sm-restart service rabbit
Expected Behavior
------------------
DC system installed successfully
Actual Behavior
----------------
When DC system needs to be rebooted, the rabbit service is not initialized correctly.
Reproducibility
---------------
Intermittent
Issue ocurred in some DC systems 100% of times. In other DC systems this does not happen at all
System Configuration
-------
DC System
Timestamp/Logs
--------------
2022-10-
Test Activity
-------------
Regression
Workaround
----------
Run sm-unmanage service rabbit
Wait until the processes related to rabbit processes are gone or kill them (ps aux | grep rabbit)
Run sm-manage service rabbit
tags: | added: stx.8.0 stx.config |
Changed in starlingx: | |
assignee: | nobody → Samuel Presa Toledo (spresato) |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. opendev. org/c/starlingx /config- files/+ /863427
Review: https:/