You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users would like to have control to restart a specific node from the launchpad config, set the prune values appropriately, and run launchpad apply to remove the host. After running launchpad apply, the node that was "reset" still has ucp containers running it. The manager nodes no longer consider the removed host to be in the swarm, but the host still thinks it is a part of a swarm and so keeps all the containers running.
Currently there is a procedure to manually remove the node to leave the swarm, remove all the containers stop running, and then manually clean up the docker installation of images and volumes to prepare for a fresh install, however this procedure is time-consuming and not applicable to the frequent resets required by the users.
The text was updated successfully, but these errors were encountered:
For external folks, the IDEA process is an internal Mirantis steering process, which can be used to change course for a piece of software. The feature request here goes outside the current definition of the launchpad tool/product, and therefore requires steering to decide if the product definition should be changed to include such features, warranting the allocation of resources for it.
Users would like to have control to restart a specific node from the launchpad config, set the prune values appropriately, and run
launchpad apply
to remove the host. After running launchpad apply, the node that was "reset" still has ucp containers running it. The manager nodes no longer consider the removed host to be in the swarm, but the host still thinks it is a part of a swarm and so keeps all the containers running.Currently there is a procedure to manually remove the node to leave the swarm, remove all the containers stop running, and then manually clean up the docker installation of images and volumes to prepare for a fresh install, however this procedure is time-consuming and not applicable to the frequent resets required by the users.
The text was updated successfully, but these errors were encountered: