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
When running a play that includes network configuration to change the LMI management address, and that includes roles that call the "Commit Changes" handler, the appliance becomes unresponsive.
The source of this problem is the order of the handlers.
"Commit Changes" is listed before "Commit Changes and Restart" , so is executed first, resulting in loss of connection. If the order is reversed, it would work.
Is there a reason against swapping the order ? I would think that if you have the need for a "Commit Changes and Restart", you'd want to have that executed always over a simple "Commit Changes" ?
The text was updated successfully, but these errors were encountered:
When running a play that includes network configuration to change the LMI management address, and that includes roles that call the "Commit Changes" handler, the appliance becomes unresponsive.
The source of this problem is the order of the handlers.
"Commit Changes" is listed before "Commit Changes and Restart" , so is executed first, resulting in loss of connection. If the order is reversed, it would work.
Is there a reason against swapping the order ? I would think that if you have the need for a "Commit Changes and Restart", you'd want to have that executed always over a simple "Commit Changes" ?
The text was updated successfully, but these errors were encountered: