-
Notifications
You must be signed in to change notification settings - Fork 1.5k
lxc_container: logging is not applied to any action except container creation #2691
Comments
@cloudnull ping, this issue is waiting for your response. |
@cloudnull, ping. This issue is still waiting on your response. |
@cloudnull, ping. This issue is still waiting on your response. |
2 similar comments
@cloudnull, ping. This issue is still waiting on your response. |
@cloudnull, ping. This issue is still waiting on your response. |
@cloudnull, ping. This issue is still waiting on your response. |
This repository has been locked. All new issues and pull requests should be filed in https://github.com/ansible/ansible Please read through the repomerge page in the dev guide. The guide contains links to tools which automatically move your issue or pull request to the ansible/ansible repo. |
This issue was migrated to ansible/ansible#29345 |
ISSUE TYPE
COMPONENT NAME
lxc_container
ANSIBLE VERSION
CONFIGURATION
None
OS / ENVIRONMENT
N/A
SUMMARY
The
container_log
andcontainer_log_level
parameters are only ever used for the container creation. It is never applied to the changes of state, to the command execution or to any other actions taken against the container.STEPS TO REPRODUCE
The details steps to demonstrate the bug are in https://gist.github.com/odyssey4me/dc94e44d96d94e36bf11c0b8faa0c7ee
EXPECTED RESULTS
I expect that the
container_log
andcontainer_log_level
parameters are applied to every state change and every command execution. Any state changes introduced by container_config changes should also be logged if the parameters are provided.The detailed actual results and expected results are demonstrated in https://gist.github.com/odyssey4me/dc94e44d96d94e36bf11c0b8faa0c7ee
ACTUAL RESULTS
The detailed actual results and expected results are demonstrated in https://gist.github.com/odyssey4me/dc94e44d96d94e36bf11c0b8faa0c7ee
The text was updated successfully, but these errors were encountered: