Actions
Bug #64902
opencephadm: public_network config check does not pick up changes in public_network unless the module restarts
% Done:
0%
Source:
Tags:
backport_processed
Backport:
squid, reef, quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Description
This causes a bit of a workflow issue with responding to the health warning. A user will see the warning, and potentially change/add to the public_network list as a result. However, the config check will continue to use the old public_network list and the warning will persist even though the user has solved the problem. They would have to either restart the cephadm module or do a failover/restart the active mgr to get the warning to go away, which is not intuitive.
Updated by Adam King about 1 month ago
- Status changed from In Progress to Pending Backport
Updated by Backport Bot about 1 month ago
- Copied to Backport #64992: quincy: cephadm: public_network config check does not pick up changes in public_network unless the module restarts added
Updated by Backport Bot about 1 month ago
- Copied to Backport #64993: squid: cephadm: public_network config check does not pick up changes in public_network unless the module restarts added
Updated by Backport Bot about 1 month ago
- Copied to Backport #64994: reef: cephadm: public_network config check does not pick up changes in public_network unless the module restarts added
Actions