Thanks for bringing this up Jean-Francois, One of our devs has addressed this and with the following PR it’s now fixed. It turned out a constraint was violated when deploying a VM in a project. This will likely get merged in 4.11.1.0 https://github.com/apache/cloudstack/pull/2420
Please let keep us posted if you find any further issues. Regards, Boris. On 19 Jan 2018, at 17:57, Nux! <n...@li.nux.ro<mailto:n...@li.nux.ro>> wrote: Hi, Might be worth sending this to dev@ as well, especially now that we are doing testing for 4.11. HTH -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro<http://www.nux.ro> boris.stoya...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue ----- Original Message ----- From: "Jean-Francois Nadeau" <the.jfnad...@gmail.com> To: "users" <users@cloudstack.apache.org> Sent: Wednesday, 17 January, 2018 21:09:19 Subject: New L2 nework types are not shared Hi all, I'm testing 4.11-rc1 and the new L2 network type feature as shown at http://www.shapeblue.com/layer-2-networks-in-cloudstack/ I want to use this as a replacement to a shared network offering with no DHCP which works to support an external DHCP server but still required to fill some CIDR information. I thought the intent was that L2 network type was to replace the previous approach when required to integrate an existing network. If I attempt to provision a VM in a project as the root admin using the L2 network I get denied... apparently because they are not shared and I can't make them public. ('HTTP 531 response from CloudStack', <Response [531]>, {u'errorcode': 531, u'uuidList': [], u'cserrorcode': 4365, u'errortext': u'Unable to use network with id= 7712102b-bbdf-4c54-bdbf-9fddfa16de46, permission denied'}) Provisioning in the root project works just fine.... but really I want to use L2 networks in user projects even if only the admin can do so. Thoughts ?