rvalle commented on issue #4393: URL: https://github.com/apache/cloudstack/issues/4393#issuecomment-706669108
@weizhouapache thanks for pointing out. I tried to deploy an ACS test cluster from scratch without touching these files: ``` TASK [privazio.vdc.cloudstack-node : Install Cloudstack agent packages in Debian derivatives] *** changed: [compute2] changed: [compute1] TASK [privazio.vdc.cloudstack-node : Configure Cloudstack node firewall rules] *** changed: [compute1] changed: [compute2] TASK [privazio.vdc.cloudstack-node : Configure qemu] *************************** skipping: [compute1] skipping: [compute2] TASK [privazio.vdc.cloudstack-node : Configure libvirtd] *********************** skipping: [compute1] skipping: [compute2] TASK [privazio.vdc.cloudstack-node : Configure libvirtd defaults] ************** skipping: [compute1] skipping: [compute2] TASK [privazio.vdc.cloudstack-node : Start Cloudstack node services] *********** ok: [compute1] => (item=libvirtd) ok: [compute2] => (item=libvirtd) ``` And it turns out the cluster is fully functional.  I guess the installation documentation is out of date, at least for Ubuntu, with initial libvirt configuration fully performed by ACS. @andrijapanicsb helped me before with another similar issue related to Firewall rules, where the documentation lists all the required rules but some rules for the link-local came from somewhere else... when placing the firewall under configuration management a similar problem came up. ---------------------------------------------------------------- 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]
