-
Notifications
You must be signed in to change notification settings - Fork 107
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
Need further output from "check" mode #690
Comments
The check mode (or dry run mode) does not actually apply any changes to the system. It only simulates the changes and reports what would be changed if the playbook were run without check mode. |
The role uses its backend (provider) initscripts and NetworkManager to configure the user-specified routes, if the backend reports any issue, then the error will be populated and logged by the role. And the check mode is for testing and verifying the playbooks, it helps ensure that the playbooks are idempotent and changes are predictable. |
Thanks for the update. We'd like to see the routes being added (or removed) using check mode. Is there a way of doing this? We use the network role extensively for managing routes, bonding, vlan tagging, ethtool setting etc. Right now we can see that eno2 "is-modified", however we can't see what is actually changed. For example the pending change below could be a static route, or modified ethtool parameter etc. Is there a way of confirming what's actually being modified on eno2?
|
As per the previous comment : I would find a more granular audit function very useful. |
Thanks for the response. Ansible nmcli module supports the |
Yes, would it be possible to introduce diff_mode into the network role? |
@ts97783 Let me try it out, by the way, the patch is welcome if you want to support the |
Hi,
Is there a way to see the intended changes using "check" mode?
The below play will add route 200.52.100.128/26 via 10.140.4.129 (this is the desired outcome).
Running the play shows the below.
We see "update connection eno2" but we're unable to gather any further information on the expected change.
Is there any method that would show the route to be added using "check" mode?
How does the role determine that a route needs to be added? I suspect we could simply add a "debug" to that specific task to view the intended outcome?
The text was updated successfully, but these errors were encountered: