tatay188 commented on issue #10659: URL: https://github.com/apache/cloudstack/issues/10659#issuecomment-2789474036
I noticed the cludstack does not link the physical lo loopback interface when creating a vxlan using the script. ### Regarding the VXLAN i found the Cloudstack does not link the Interface Loopback to the VXLAN interface, I did manually and now it propagates the routes CLOUDSTACK ALONE DOES NOT ADD THE PARENT Loopback interface vxlan: vtysh -c 'show interface vxlan1000' Interface vxlan1000 is up, line protocol is up Link ups: 4 last: 2025/04/06 03:16:37.88 Link downs: 0 last: (never) vrf: default index 143 metric 0 mtu 9050 speed 0 txqlen 1000 flags: <UP,LOWER_UP,BROADCAST,RUNNING,MULTICAST> Type: Ethernet HWaddr: 7e:05:79:2f:33:7d Interface Type Vxlan Interface Slave Type Bridge VTEP IP: 10.23.133.14 VxLAN Id 1000 Access VLAN Id 1 Master interface: brvx-1000 protodown: off After I manually Link the parent Loopback interface: vtysh -c 'show interface vxlan1000' Interface vxlan1000 is up, line protocol is up Link ups: 0 last: (never) Link downs: 0 last: (never) vrf: default index 17 metric 0 mtu 9050 speed 0 txqlen 1000 flags: <UP,LOWER_UP,BROADCAST,RUNNING,MULTICAST> Type: Ethernet HWaddr: b6:9d:d9:66:b1:60 Interface Type Vxlan Interface Slave Type Bridge VTEP IP: 10.23.133.14 Link Interface lo VxLAN Id 1000 Access VLAN Id 1 Master interface: brvx-1000 protodown: off Parent interface: lo Is propagating the routes, and I can reach from the remote VTEP And even the Gray buttons for the system VMs are now green. It's a domino effect. regarding setup logs, I got a fail after I reboot, but maybe related to be using UBUNTU: ### On the AGENT side: Not sure if this is just related to Ubuntu systems: there is an error on the management server every time i reload it: DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management stop DEBUG:root:execute:sudo update-rc.d -f cloudstack-management remove DEBUG:root:execute:sudo update-rc.d -f cloudstack-management defaults DEBUG:root:Failed to execute:update-rc.d: ### error: unable to read /etc/init.d/cloudstack-management DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status DEBUG:root:Failed to execute:× cloudstack-management.service - CloudStack Management Server Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2025-04-02 13:13:48 UTC; 1 day 8h ago Main PID: 537731 (code=exited, status=143) CPU: 27min 54.476s Obviously there is no such file: Should I create One? ls -al /etc/init.d/ cryptdisks grub-common iwpmd nfs-common plymouth rng-tools-debian ufw apparmor cryptdisks-early hwclock.sh keyboard-setup.sh ntp plymouth-log rpcbind unattended-upgrades apport dbus ipmievd kmod open-iscsi procps rsync uuidd console-setup.sh dpdk irqbalance lvm2 openipmi quota ssh x11-common cron frr iscsid lvm2-lvmpolld openvswitch-switch ### On the management side, only when i restart the agent: Apr 03 18:41:23 kvmvcompatl2001 systemd[1]: Starting Uncomplicated firewall... Apr 03 18:41:23 kvmvcompatl2001 systemd[1]: Finished Uncomplicated firewall. Apr 03 23:30:14 kvmvcompatl2001 systemd[1]: Stopping Uncomplicated firewall... Apr 03 23:30:14 kvmvcompatl2001 ufw-init[56782]: Skip stopping firewall: ufw (not enabled) Apr 03 23:30:14 kvmvcompatl2001 systemd[1]: ufw.service: Deactivated successfully. Apr 03 23:30:14 kvmvcompatl2001 systemd[1]: Stopped Uncomplicated firewall. DEBUG:root:execute:sudo /usr/sbin/service ufw start DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent status DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent stop DEBUG:root:execute:sleep 30 DEBUG:root:execute:sudo update-rc.d -f cloudstack-agent remove DEBUG:root:execute:sudo update-rc.d -f cloudstack-agent defaults DEBUG:root:### Failed to execute:update-rc.d: error: unable to read /etc/init.d/cloudstack-agent DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent status DEBUG:root:Failed to execute:○ cloudstack-agent.service - CloudStack Agent Loaded: loaded (/lib/systemd/system/cloudstack-agent.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Thu 2025-04-03 23:30:17 UTC; 31s ago Docs: http://www.cloudstack.org/ Main PID: 56558 (code=exited, status=1/FAILURE) CPU: 14.716s Apr 03 23:30:17 kvmvcompatl2001 systemd[1]: Stopped CloudStack Agent. Apr 03 23:30:17 kvmvcompatl2001 systemd[1]: cloudstack-agent.service: Consumed 14.716s CPU time. DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent start Please let me know your thoughts. Thank you Tata Y. > On Apr 7, 2025, at 6:45 AM, Rohit Yadav ***@***.***> wrote: > > > rohityadavcloud > left a comment > (apache/cloudstack#10659) > @tatay188 can you try keeping the input as blank where you want to specify untagged vlan/vxlan? It may be possible that vxlan isn't supported for any network other than guest (cc @wido @weizhouapache ... others can advise) > > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you were mentioned. > > <https://github.com/tatay188> <https://github.com/wido> <https://github.com/weizhouapache> <https://github.com/apache/cloudstack/issues/10659#issuecomment-2782892886> <https://github.com/notifications/unsubscribe-auth/ACNEALMN6LNXLYICN7P2JIL2YJJOLAVCNFSM6AAAAAB2MWQERCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBSHA4TEOBYGY> > > rohityadavcloud > left a comment > (apache/cloudstack#10659) > <https://github.com/apache/cloudstack/issues/10659#issuecomment-2782892886> > @tatay188 <https://github.com/tatay188> can you try keeping the input as blank where you want to specify untagged vlan/vxlan? It may be possible that vxlan isn't supported for any network other than guest (cc @wido <https://github.com/wido> @weizhouapache <https://github.com/weizhouapache> ... others can advise) > > — > Reply to this email directly, view it on GitHub <https://github.com/apache/cloudstack/issues/10659#issuecomment-2782892886>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACNEALMN6LNXLYICN7P2JIL2YJJOLAVCNFSM6AAAAAB2MWQERCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBSHA4TEOBYGY>. > You are receiving this because you were mentioned. > -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
