Yes, that is the reason. When creating the zone, the network label remained unchanged (even though I provided the appropriate names). Is it possible to update it without deleting the zone?
Piotr -----Original Message----- From: Wei ZHOU <ustcweiz...@gmail.com> Sent: Thursday, July 11, 2024 10:40 AM To: users@cloudstack.apache.org Subject: Re: Missing bridge/device network configuration In addition to what Rohit said, it looks like there are some bridges already created. you can update the traffic label of physical networks to guest0 , public0 or ceph0. The default traffic labels are cloudbr0/cloudbr1 which might not be what you plan to use. -Wei On Thu, Jul 11, 2024 at 10:22 AM Rohit Yadav <rohit.ya...@shapeblue.com> wrote: > > Piotr, > > I see you don't have a cloudbr0 or similar bridge which is default. If you > want to use custom bridge, then you need to configure your zone's physical > network's traffic type with such traffic labels before adding the KVM host. > > You can cross-check this against the KVM host (where it failed) > agent.properties file, where in it has private/public/guest network device > which isn't setup on your KVM host. > > References: > https://docs.cloudstack.apache.org/en/4.19.0.2/installguide/configurat > ion.html#id4 > https://docs.cloudstack.apache.org/en/4.19.0.2/adminguide/troubleshoot > ing.html#trouble-shooting-steps > https://www.shapeblue.com/networking-kvm-for-cloudstack/ > > > > Regards. > > > > > ________________________________ > From: Piotr Pisz <pi...@piszki.pl> > Sent: Thursday, July 11, 2024 12:29 > To: users@cloudstack.apache.org <users@cloudstack.apache.org> > Subject: Missing bridge/device network configuration > > Hi, > > I'm trying to add a host with ubuntu22 and a network generated by netplan, > unfortunately I have the problem as below, have I missed something? > > SSH command output:Starting to configure your system: > Configure Host ... [OK] > Configure Apparmor ... [OK] > Configure Network ... [Failed] > Missing bridge/device network configuration, need to add your network > configuration into /etc/network/interfaces at first Try to restore your > system: > Restore Host ... [OK] > Restore Apparmor ... [OK] > Restore Network ... [OK] > > Agetn setup.log: > > DEBUG:root:execute:uname -r > DEBUG:root:execute:uname -m > DEBUG:root:execute:hostname -f > DEBUG:root:execute:kvm-ok > DEBUG:root:execute:awk '/MemTotal/ { printf "%.3f \n", $2/1024 }' > /proc/meminfo DEBUG:root:execute:ip a | grep "^\w" | grep -iv "^lo" | > wc -l DEBUG:root:execute:service apparmor status > DEBUG:root:execute:apparmor_status |grep libvirt DEBUG:root:Failed to > execute: > DEBUG:root:cloudbr0 is not a network device, is it down? > DEBUG:root:execute:sudo /usr/sbin/service network-manager status > DEBUG:root:Failed to execute:Unit network-manager.service could not be found. > DEBUG:root:execute:route -n|awk '/^0.0.0.0/ {print $2,$8}' > DEBUG:root:execute:ifconfig host0 > DEBUG:root:Found default network device:host0 > DEBUG:root:execute:ifconfig host0.101 DEBUG:root:execute:sudo > update-rc.d -f apparmor remove DEBUG:root:execute:sudo update-rc.d -f > apparmor defaults DEBUG:root:execute:sudo /usr/sbin/service apparmor > status DEBUG:root:execute:sudo /usr/sbin/service apparmor start > DEBUG:root:execute:sudo /usr/sbin/service apparmor status > DEBUG:root:execute:sudo /usr/sbin/service apparmor start > DEBUG:root:execute:sudo update-rc.d -f network-manager remove > DEBUG:root:execute:sudo update-rc.d -f network-manager defaults > DEBUG:root:Failed to execute:update-rc.d: error: unable to read > /etc/init.d/network-manager DEBUG:root:execute:sudo /usr/sbin/service > network-manager status DEBUG:root:Failed to execute:Unit > network-manager.service could not be found. > DEBUG:root:execute:sudo /usr/sbin/service network-manager start > DEBUG:root:Failed to execute:Failed to start network-manager.service: Unit > network-manager.service not found. > DEBUG:root:execute:sudo /usr/sbin/service network-manager status > DEBUG:root:Failed to execute:Unit network-manager.service could not be found. > DEBUG:root:execute:sudo /usr/sbin/service network-manager start > DEBUG:root:Failed to execute:Failed to start network-manager.service: Unit > network-manager.service not found. > DEBUG:root:execute:/etc/init.d/networking stop DEBUG:root:Failed to > execute:/bin/sh: 1: /etc/init.d/networking: not found > DEBUG:root:execute:/etc/init.d/networking start DEBUG:root:Failed to > execute:/bin/sh: 1: /etc/init.d/networking: not found > > Bridges and netplan config: > > root@sdc ~# brctl show > bridge name bridge id STP enabled interfaces > ceph0 8000.963d69ccc23e no ceph0.102 > docker0 8000.02428faeaa58 no > guest0 8000.dab6e62ba668 no guest0.103 > host0 8000.32335383ebbb no host0.101 > public0 8000.aa725a4be728 no public0.227 > virbr0 8000.525400a74ecc yes > > network: > version: 2 > renderer: networkd > bonds: > bond0: > interfaces: > - eno49 > - eno50 > parameters: > lacp-rate: fast > mode: 802.3ad > transmit-hash-policy: layer3+4 > mtu: 9000 > ethernets: > eno1: {} > eno2: {} > eno3: {} > eno4: {} > eno49: > mtu: 9000 > eno50: > mtu: 9000 > vlans: > host0.101: > dhcp4: no > id: 101 > link: bond0 > mtu: 9000 > ceph0.102: > dhcp4: no > id: 102 > link: bond0 > mtu: 9000 > guest0.103: > dhcp4: no > id: 103 > link: bond0 > mtu: 9000 > public0.227: > dhcp4: no > id: 227 > link: bond0 > mtu: 9000 > bridges: > host0: > addresses: > - 10.10.101.13/24 > nameservers: > addresses: > - 8.8.8.8 > routes: > - to: default > via: 10.10.101.254 > interfaces: > - host0.101 > ceph0: > addresses: > - 10.10.102.13/24 > interfaces: > - ceph0.102 > guest0: > interfaces: > - guest0.103 > public0: > interfaces: > - public0.227 >
