ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
OS / ENVIRONMENT
Ubuntu 18.04
SUMMARY
According to the documentation it is admins responsibility to configure libvirt and qemu, I have written Ansible playbooks to do so. However, I believe the agent is also configuring them, now ansible and cloudstack agent compete for changing those files.
STEPS TO REPRODUCE
- Read ACS Manual: Quickstart/Installation of KVM
- Write playbooks to automate configuration of KVM (libvirt, qemu, etc).
- Configure your cluster
- ACS Agent will alter the configuration
- Following Playbook runs will break the configured system (i.e. when adding a new host to the cluster).
EXPECTED RESULTS
The responsibility over configuration files should be clear, either the Administrator or ACS.
When responsibility is shared a conf.d directory pattern should be used.
So I expect that either my configuration is not overridden or that ACS will deal with the configuration.
ACTUAL RESULTS
Both my playbooks and ACS Agent keep fighting for control of KVM/Libvirt configuration files.
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
OS / ENVIRONMENT
Ubuntu 18.04
SUMMARY
According to the documentation it is admins responsibility to configure libvirt and qemu, I have written Ansible playbooks to do so. However, I believe the agent is also configuring them, now ansible and cloudstack agent compete for changing those files.
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS