-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debug Instance Changes #112
Comments
have you tried |
should be one or more of these https://github.com/ngine-io/ansible-collection-cloudstack/blob/master/plugins/modules/cs_instance.py#L856 |
well... this is what happened. I modified instances by hand.... Now the warnings just vanished. It feels like there is some kind of state kept somewhere. I will try to watch closely next time this use case takes place. |
did you use the dynamic inventory? |
Yes, I have dynamic inventory. The Plugin:
how would this affect the issue? somewhere there seems to be some state, or mark that the instance has changed, or pending changes to apply or something. |
so, the only thing that can cache is the inventory, even though I think we don't implemented it https://github.com/ngine-io/ansible-collection-cloudstack/blob/master/plugins/inventory/instance.py#L246 |
then there is facts caching but that should not be involved. |
Ok, I will review a bit more. Once I had troubles with fact caching.... but not sure what about. :) |
I don't believe my playbook is attempting any changes on some instances: yet I get this message on some:
Is there any way I can debug which changes is Ansible trying to apply?
The text was updated successfully, but these errors were encountered: