Hudratronium opened a new issue #4754:
URL: https://github.com/apache/cloudstack/issues/4754
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and master branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
* Enhancement Request
##### COMPONENT NAME
<!--
Cloudstack Agent
-->
~~~
~~~
##### CLOUDSTACK VERSION
<!--
4.15
-->
~~~
~~~
##### CONFIGURATION
<!--
Host to add: CentOS8
-->
##### OS / ENVIRONMENT
<!--
CentOS8 / Hypervisor KVM / libvirt 6.0.0
-->
##### SUMMARY
When adding a Host to a cluster, during the process a "configuration" of the
libvirtd takes place.
`management server log:
2021-03-05 01:38:37,166 DEBUG [c.c.u.s.SSHCmdHelper]
(qtp2012330741-326:ctx-969e2771 ctx-a592cc3c) (logid:55839319) SSH command:
cloudstack-setup-agent -m 192.168.163.139 -z 5 -p 4 -c 4 -g
902eefa4-f4bc-3c75-8a1c-c57bc3798f18 -a -s --pubNic=cloudbr0 --prvNic=cloudbr0
--guestNic=cloudbr0 --hypervisor=kvm
SSH command output:Starting to configure your system:
Configure SElinux ... [OK]
Configure Network ... [OK]
Configure Libvirt ... [Failed]
Configuration failed for service Libvirt
Try to restore your system:
Restore SElinux ... [OK]
Restore Network ... [OK]
Restore Libvirt ... [Failed]`
The problem is, that during this configuration the parameter
`LIBVIRTD_ARGS=-l` is written into /etc/sysconfig/libvirtd.
At least for me, this breaks the whole set-up as the libvirtd will stop
after relaoding.
Also therer are several other parameter, witch aren't needed when
configuring libvirt usind systemd. These seem at least having not this effect
on the libvirtd.
##### STEPS TO REPRODUCE
<!--
1. Configure a CentOS 8 machine according to the guides, besides the
libvirt-configuration. Theseare configured accordingly to the official libvirt
docs [https://libvirt.org/daemons.html](url)
2. Add the CentOS8 Host to a cluster
-->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
Host would be added to the cluster.
##### ACTUAL RESULTS
<!-- What actually happened? -->
Host wasn't added to the cluster; libvirtd won't come up anymore so the
cloud-stack agent is also down as long as libvirtd is repaired.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
