Nicolas, Ansible will assure that the system is in the desired state in every run. All desired configurations are checked against the system (all hosts) and if something is off it will be corrected.
The issue here is who is responsible for those files? The administrator? ACS? My Playbooks currently template the whole file. It is also possible to write playbooks that check for specific lines in a file, but then it would be 3 sources of configuration for those files: ACS, Administrator and the OS distribution. Sharing the custody of this kind of files by many entities is a bad idea, however patterns like the conf.d/* help a lot. Rafael On Sat, 2020-10-10 02:01 PM, Nicolas Vazquez <[email protected]> wrote: > The agents modify the configuration file once the connection to a management > server is correct. > > I'm not sure what is the content of your playbooks but pressumably they > should be only configuring new hosts as described in this documentation: > http://docs.cloudstack.apache.org/en/4.14.0.0/installguide/hypervisor/kvm.html > and then addind the hosts through the CloudStack API without modifying any > file on the older hosts, is this correct? If not, can you please explain the > playbooks actions to check if somehow are iterating through the previously > added hosts? Also, can you replicate the issue if adding new hosts manually > (and older hosts in 'Up' state)? > > Regards, > Nicolas Vazquez > ________________________________ > From: [email protected] " target="_blank"><[email protected]> > Sent: Friday, October 9, 2020 2:11:56 PM > To: [email protected] " > target="_blank"><[email protected]> > Cc: [email protected] " > target="_blank"><[email protected]>; [email protected] " > target="_blank"><[email protected]> > Subject: Re: KVM hosts transitioned from "up" to "unsecured" > > I think the root cause of this is that ACS is managing the configuration of > LIbvirt/KVM but the documentation implies otherwise. > https://github.com/apache/cloudstack/issues/4393 > > Regards, > Rafael > > On Fri, 2020-10-09 06:20 PM, [email protected] wrote: > > Ok, > > > > here there seems to be some kind of problem. > > > > my playbooks are modifying this file, but so is (presumingly) the agent. > > > > I can see other files also changed: related to qemu and libvirt. > > > > Is the agent managing libvirt and qemu configuration? or does it need to be > > configured as described in the documentation? > > > > Regards, > > Rafael > > > > On Fri, 2020-10-09 01:47 PM, Rakesh v " target="_blank">" > > target="_blank"><[email protected]> wrote: > > > > > You might want to add libvirtd_opts="-l" In /etc/default/libvirt-bin > > > > > > Sent from my iPhone > > > > > > > [email protected] > http://www.shapeblue.com > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK > @shapeblue > > > > > On 09-Oct-2020, at 9:18 AM, [email protected] wrote: > > > > > > > > Hi! > > > > > > > > Yesterday I added more hosts to a cluster, and the ones that were there > > > > are now showing as "unsecured". > > > > > > > > Probably my installation playbook messed something up. > > > > > > > > Any idea what could have triggered such a thing to happen? > > > > > > > > anybody suffered this also? > > > > > > > > Rafael > > > > > >
