systemctl stop should not fail the apply of the paunch command, when it attempts to stop & remove a container to be recreated again
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Incomplete
|
Medium
|
Unassigned |
Bug Description
While testing https:/
Deleting container (changed config_data): mysql
Stopping and disabling systemd service for tripleo_mysql
(waits for 60 seconds here...)
Job for tripleo_
systemctl failed
^^ although, the container has been removed in the end, that failure was undesired for the paunch, when it attempts to re-apply a config change and meets an unresponsive container. Perhaps, the exception should be caught and suppressed in paunch for that a particular case.
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → stein-3 |
description: | updated |
tags: | added: containers idempotency |
summary: |
- systemctl stop should not fail the apply of the paunch command + systemctl stop should not fail the apply of the paunch command, when it + attempts to stop & remove a container to be recreated again |
description: | updated |
Changed in tripleo: | |
milestone: | stein-3 → train-1 |
Changed in tripleo: | |
milestone: | train-1 → train-2 |
Changed in tripleo: | |
milestone: | train-2 → train-3 |
Changed in tripleo: | |
milestone: | train-3 → ussuri-1 |
Changed in tripleo: | |
milestone: | ussuri-1 → ussuri-2 |
Changed in tripleo: | |
milestone: | ussuri-2 → ussuri-3 |
Changed in tripleo: | |
status: | Triaged → Incomplete |
Changed in tripleo: | |
milestone: | ussuri-3 → ussuri-rc3 |
Changed in tripleo: | |
milestone: | ussuri-rc3 → victoria-1 |
Changed in tripleo: | |
milestone: | victoria-1 → victoria-3 |