Hey, Felipe
Sorry for the late reply, but are you working with the KVM hypervisor?
When updating the traffic labels in the zone, ACS does not automatically
update the `agent.properties` file in the hosts. If I am not mistaken,
during the system VM deployment on a KVM hypervisor, ACS will utilize
the device specified in this file, specifically the configurations
`private.network.device`, `guest.network.device` and
`public.network.device`. Can you check the `agent.properties` and verify
if these configurations are set with the correct values?
Best regards,
Bryan
On 08/08/2024 15:50, Felipe Polanco wrote:
Hi,
I'm setting up a lab environment with 1-host 1 management server in
Cloudstack.
I'm facing issues with the system VMs not starting, I fixed multiple issues
but this one got me:
Process [59640] for command
[/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh -v 100
-p -b br-100 -o add ] encountered the error: [ls: cannot access
'/sys/class/net//brif/': No such file or directoryCommand line is not
complete. Try option "help"ls: cannot access '/sys/class/net//brif/': No
such file or directoryFailed to add vlan: br-100.100 to ].
I want to use VLAN 100 in my network but at no point Cloudstack asked me
from which interface, I tried adding that manually under "update
traffic labels" but still that made no difference.
That script is failing because the parent interface from which the VLAN
subinterface has to be created cannot be found, yet I don't see where to
specify it.
Any ideas?
