Skip to content

Fix controller install when container was removed manually - #104

Open
AryanP123 wants to merge 1 commit into
skupperproject:mainfrom
AryanP123:fix-controller-recreate-after-rm
Open

Fix controller install when container was removed manually#104
AryanP123 wants to merge 1 commit into
skupperproject:mainfrom
AryanP123:fix-controller-recreate-after-rm

Conversation

@AryanP123

Copy link
Copy Markdown
Contributor

Fixes #96

skupper.v2.controller install now recreates the container when the systemd service exists but the container was removed (e.g. podman rm -f).
Skips install only when the container is already present
Added unit test coverage for the service-exists / container-missing case

@AryanP123
AryanP123 requested review from fgiorgetti and hash-d June 16, 2026 18:54
Comment thread plugins/modules/controller.py Outdated
self.module.debug("skupper-controller service exists but container is missing")
self.create_container()
self.start_service()
return True

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It assumes that the existing service that was left behing is still valid.
I'd recommend calling just module_utils.system.delete_service() and let rest of the updated method runs, instead of returning.

Fixes skupperproject#96

Signed-off-by: Aryan Puttur <putturaryan@gmail.com>
@AryanP123
AryanP123 force-pushed the fix-controller-recreate-after-rm branch from 4a991c9 to 659fee8 Compare June 17, 2026 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Controller container not restarted after manual kill + skupper.v2.controller with action install

2 participants