What that is actually say is that rackd itself is only 25% connected. All other services that the rackd manages is working fine, and rackd itself is working its just in a degraded state as its missing a couple of connections to the regiond. The rackd should automatically fix this issue and reconnect to the other regiond processes, and it should not cause any issues with operation.
Since this is a connection issue from the rackd to the regiond we could say what regiond processes you are not connected to instead of a precentage. Something like:
rackd -- degraded -- missing connections to my-region:2143, my-region:2144, my-region:2145
or it could be just the regiond name
rackd -- degraded -- missing 2 connections to my-region and other-region
What that is actually say is that rackd itself is only 25% connected. All other services that the rackd manages is working fine, and rackd itself is working its just in a degraded state as its missing a couple of connections to the regiond. The rackd should automatically fix this issue and reconnect to the other regiond processes, and it should not cause any issues with operation.
Since this is a connection issue from the rackd to the regiond we could say what regiond processes you are not connected to instead of a precentage. Something like:
rackd -- degraded -- missing connections to my-region:2143, my-region:2144, my-region:2145
or it could be just the regiond name
rackd -- degraded -- missing 2 connections to my-region and other-region