Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[release-4.7] Bug 1960103: Pause MCP before draining/rebooting node #504

Merged
merged 3 commits into from
May 21, 2021
Merged

[release-4.7] Bug 1960103: Pause MCP before draining/rebooting node #504

merged 3 commits into from
May 21, 2021

Commits on May 13, 2021

  1. Pause MCP before draining/rebooting node 

    The config daemon instance on each node need to compete for the 'Draining' lock before
it can draining/rebooting a node.

After a config daemon instance gets the lock, it checks its MachineConfigPool conditions.
If the MCP is in ready state, it will pause the MCP then process, otherwise, it wait for
the MCP getting ready. The MCP will be resumed after the config daemon and release the
lock after the config dameon finishes its work.
    @pliurh
    pliurh committed May 13, 2021
    Configuration menu
    Copy the full SHA
    b09f058 View commit details
    Browse the repository at this point in the history

  2. Fix setup-envtest.sh source in Makefile

    @pliurh
    pliurh committed May 13, 2021
    Configuration menu
    Copy the full SHA
    fbdb84b View commit details
    Browse the repository at this point in the history

  3. Add machineconfiguration cluster rule to CSV manifest

    @pliurh
    pliurh committed May 13, 2021
    Configuration menu
    Copy the full SHA
    f879032 View commit details
    Browse the repository at this point in the history