Skip to content

Add host process results in incorrect libvirtd settings for Ubuntu VERSION="24.04.1 LTS (Noble Numbat)" #9802

@ffslcschools

Description

@ffslcschools
ISSUE TYPE
  • Bug Report
COMPONENT NAME
Host agent processing script.
CLOUDSTACK VERSION
CloudStack 4.19.1.1
CONFIGURATION

Advanced networking

OS / ENVIRONMENT

PRETTY_NAME="Ubuntu 24.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.1 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

SUMMARY

When adding a kvm host to Cloudstack, the agent configuration automatically adds the option libvirtd_opts='-l' to /etc/default/libvirtd. This creates failures for live migrations between cluster hosts. Documentation here https://docs.cloudstack.apache.org/en/latest/installguide/hypervisor/kvm.html is correct, stating that Ubuntu 20.04 and newer should use the option LIBVIRTD_ARGS="--listen".
The documentation is confusing in that it seems to tell you to make these changes manually, but the host provisioning process modifies all of the files referenced.

STEPS TO REPRODUCE

Simply adding a host via the web interface will do this at least when the host os version is Ubuntu 24.04.1 LTS.


EXPECTED RESULTS
The proper existing settings to be uncommented or at least added to the end of the config files as the documentation states.
ACTUAL RESULTS

Agent configuration process automatically adds the option libvirtd_opts='-l' to /etc/default/libvirtd when the os version is newer than 20.04.


Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions