after subcloud reboot it takes a long time for DC subcloud to go "in-sync"
Bug #1916784 reported by
Chris Friesen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Chris Friesen |
Bug Description
When a subcloud in distributed-cloud goes offline, dcmanager will report its sync status as "unknown" since we don't know what load it's running, whether it's patch-current, etc.
When it comes back online, it can take a long time for this "unknown" to resolve because some of the audits only run once an hour.
Accordingly, when a subcloud transitions from "offline" to "online" we should request that all of the various sub-audits be performed in order to get a current picture of that subcloud so that we can update the sync status in a reasonable timeframe.
Changed in starlingx: | |
assignee: | nobody → Chris Friesen (cbf123) |
Changed in starlingx: | |
status: | Fix Committed → Fix Released |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.5.0 |
To post a comment you must log in.
Fixed by https:/ /review. opendev. org/c/starlingx /distcloud/ +/777208