You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Incidentally the specified IPs match the current system configuration, so no actual changes should be taking place anyway but it still fails. If you need any other info or logs from the system, please let me know.
Thank you for the report. Currently the role requires the type to be specified to support setting the IP addresses, it works when you add type: ethernet to the settings:
The error message could be improved, though. Making type: ethernet the default bears the risk of breaking configurations when the specified device is a bond device or something else.
Thank you for your rapid response. The change you suggested did indeed keep the error message from popping up. Unfortunately, whatever happened next caused me to lose connectivity to the server. I'll dig in and fix that; if the issue is unrelated to this role, then I will close the issue, otherwise I'll add relevant logs.
Hoping that I did not misunderstand a fundamental aspect of how this role works, I encountered the following issue:
TASK [network : Configure networking connection profiles] *********************************************************************************************************************************************************************************** fatal: [redacted]: FAILED! => {"changed": false, "msg": "fatal error: configuration error: connections[0].ip: property is not allowed for state 'up' and persistent_state 'present'"}
Relevant variables:
Incidentally the specified IPs match the current system configuration, so no actual changes should be taking place anyway but it still fails. If you need any other info or logs from the system, please let me know.
Fedora 28 Server, current master (a10e72b)
The text was updated successfully, but these errors were encountered: