When two Kieservers pods or more are bootstrapped on a HA environment, the following error could show up in the logs:
This error could be safely ignored since the ConfigMap will be created and the pods will work normally.
The proposed change is to add a new catch in this part of the code to handle this exception as a warn that can be safely ignored.
In 7.4.0 a "Known Issue" should be documented alerting users that this error message can be safely ignored explaining that is a simple racing condition to create the configmap used by Kieservers during runtime. The configmap will be created and the pods will work as expected.