Skip to content
This repository has been archived by the owner on Oct 30, 2018. It is now read-only.

lxc_container: logging is not applied to any action except container creation #2691

Closed
odyssey4me opened this issue Aug 7, 2016 · 8 comments

Comments

@odyssey4me
Copy link

ISSUE TYPE
  • Bug Report
COMPONENT NAME

lxc_container

ANSIBLE VERSION
ansible 2.1.1.0
  config file =
  configured module search path = Default w/o overrides
CONFIGURATION

None

OS / ENVIRONMENT

N/A

SUMMARY

The container_log and container_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 and container_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

@ansibot
Copy link

ansibot commented Aug 7, 2016

@cloudnull ping, this issue is waiting for your response.
click here for bot help

@ansibot
Copy link

ansibot commented Sep 11, 2016

@cloudnull, ping. This issue is still waiting on your response.
click here for bot help

@ansibot
Copy link

ansibot commented Oct 6, 2016

@cloudnull, ping. This issue is still waiting on your response.
click here for bot help

2 similar comments
@ansibot
Copy link

ansibot commented Oct 22, 2016

@cloudnull, ping. This issue is still waiting on your response.
click here for bot help

@ansibot
Copy link

ansibot commented Nov 6, 2016

@cloudnull, ping. This issue is still waiting on your response.
click here for bot help

@ansibot
Copy link

ansibot commented Nov 22, 2016

@cloudnull, ping. This issue is still waiting on your response.
click here for bot help

@ansibot
Copy link

ansibot commented Dec 6, 2016

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.

@ansibot
Copy link

ansibot commented Sep 11, 2017

This issue was migrated to ansible/ansible#29345

@ansibot ansibot closed this as completed Sep 11, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants