GitHub user tatay188 added a comment to the discussion: CloudStack 4.20 UI
Unable to add KVM-Host on VXLAN Logic structure - Errors
**### 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
**### 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:
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
Once 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
Now the System VMs agent-state shows green
But still the System Vms' Interface name are not populated, should it be
populated ? what is the normal status for this?
Please let me know.
Tata Y.
GitHub link:
https://github.com/apache/cloudstack/discussions/10679#discussioncomment-12779040
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
