andrijapanicsb opened a new issue #3816: "restart required : yes" is never set to "no" after network/VPC restart URL: https://github.com/apache/cloudstack/issues/3816 <!-- Verify first that your issue/request is not already reported on GitHub. Also test if the latest release and master branch are affected too. Always add information AFTER of these HTML comments, but no need to delete the comments. --> ##### ISSUE TYPE <!-- Pick one below and delete the rest --> * Bug Report ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ https://github.com/apache/cloudstack/blob/master/server/src/main/java/com/cloud/network/vpc/VpcManagerImpl.java#L1719-L1764 ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ 4.13 ~~~ ##### CONFIGURATION/SUMMARY/ETC <!-- Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise --> When a network is showing as "Restart required: yes" in the GUI (field "restart_required"="1" in cloud.networks table) - there is no way to "fix" this (set it back to "no") Confirmed by manually setting "1" in the DB for multiple Shared, non-VPC Isolated networks and VPC Isolated networks. Restart (no cleanup) doesn't work Restart (with cleanup) doesn't work The only way seems to be to hack the DB to set The code provided above does set this for the VPC itself, not for it's networks.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
