shuan1026 opened a new pull request, #56: URL: https://github.com/apache/ozone-helm-charts/pull/56
## What changes were proposed in this pull request? Scaling up OM replicas with `om.persistence.enabled=true` left the new OM pod stuck in `Init:0/1` CrashLoopBackOff, and `helm upgrade --wait` timed out. The `om-bootstrap` init container invoked non-existent `ozone admin om --bootstrap`. Using the correct `ozone om --bootstrap` is not enough on its own: that command keeps running as the OM daemon, so it never completes inside an init container; `checkConfigBeforeBootstrap` also requires existing OMs to already know the new node, which only happens after a config-checksum rolling restart that StatefulSet OrderedReady blocks while the new pod stays in Init. This patch removes the init container and runs bootstrap from the om container startup path instead: * Wrapper as container `args` (image entrypoint kept for `envtoconf` / `ENSURE_OM_INITIALIZED`) * Backgrounds `ozone om --set ozone.om.nodes.<id>=… --bootstrap`, polls `ozone admin om roles`, then writes the `bootstrapped` marker and `wait`s on the daemon * Retries in-script so the pod stays Ready and the rolling update of peers can proceed * ConfigMap render condition aligned with the wrapper gate (`not om.command`) ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-16172 ## How was this patch tested? * `helm template`: fresh install keeps `args: [ozone, om]` and does not render the bootstrap ConfigMap * kind: `om.replicas` 3→2→3 with persistence enabled for om/scm/datanode; new OM joins the ring (`ozone admin om roles`); PVC UID unchanged; `/data/data/bootstrapped` present * Delete the scaled-up OM pod: restart takes the marker path (`already bootstrapped`) with no second bootstrap attempt -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
