Re: Issues with libvirt after upgrading to RockyLinux 8.5
Thank you. I thought about trying that. If I upgrade everything to Rocky, and I’m on 4.16, should I expect it to work? Will I have to re-add compute nodes to update the db with Rocky as the OS? I expect a lot of people might want to transition to Rocky since CentOS is going EOL after this month I believe. At this point, Rocky and CentOS are mostly the same thing. This complicates things a bit. Thanks -jeremy > On Thursday, Dec 16, 2021 at 1:09 AM, Andrija Panic (mailto:andrija.pa...@gmail.com)> wrote: > Can't add host: 192.168.30.54 with hostOS: Rocky into a cluster,in which > there are CentOS hosts added > > > Try changing the content of the /etc/*release file - to match the file of > the CentOS nodes - and then play with restarting agent, and observe if you > would hit the same error or not - I've seen this issue (RHEL inside CentOS > cluster, due to bad /etc/rhel-release file content), but I've not tested if > this "fix" works or not. > > Best, > > On Thu, 16 Dec 2021 at 08:39, Jeremy Hansen > wrote: > > > But if I convert all the hosts to Rocky and upgrade to 4.16, I should be > > ok? > > > > Thanks > > > > > > > > On Wednesday, Dec 15, 2021 at 11:17 PM, Slavka Peleva < > > slav...@storpool.com.INVALID> wrote: > > Sorry, I didn't pay attention to your CS version. After the upgrade, I > > think you will have the same problem. Because in the DB, there is > > information about host/hosts on this cluster that is/are with CentOS. > > > > Best regards, > > Slavka > > > > On Thu, Dec 16, 2021 at 8:49 AM Jeremy Hansen > > wrote: > > > > I noticed in the compatibility matrix that Rocky isn’t supported until > > 4.16.0.0. If I upgrade Cloudstack first, would this help or is it still > > going to complain about the centos/rocky mix? If I convert all my existing > > nodes to Rocky, which is the plan anyway, will this go away? Shouldn’t > > CentOS and Rocky be considered that same thing… sort of…? > > > > Thanks > > -jeremy > > > > > > > > > > On Wednesday, Dec 15, 2021 at 10:43 PM, Slavka Peleva < > > slav...@storpool.com.INVALID> wrote: > > Hi Jeremy, > > > > It will help if you have another cluster for Rocky Linux. Hosts need to be > > of the same OS, it's not possible to mix OSes in the same cluster. > > > > Best regards, > > Slavka > > > > On Thu, Dec 16, 2021 at 4:08 AM Jeremy Hansen > > wrote: > > > > Any tips on how I would troubleshoot this? I’ve tried downgrading libvirt > > and qemu and ca-certificates to the same version as the other functional > > nodes. That didn’t seem to help. This is obviously an ssl issue but I > > don’t really know what to do about it. > > > > 2021-12-15 18:04:14,438 INFO [cloud.agent.AgentShell] (main:null) > > (logid:) Agent started > > 2021-12-15 18:04:14,444 INFO [cloud.agent.AgentShell] (main:null) > > (logid:) Implementation Version is 4.15.0.0 > > 2021-12-15 18:04:14,447 INFO [cloud.agent.AgentShell] (main:null) > > (logid:) agent.properties found at /etc/cloudstack/agent/agent.properties > > 2021-12-15 18:04:14,466 INFO [cloud.agent.AgentShell] (main:null) > > (logid:) Defaulting to using properties file for storage > > 2021-12-15 18:04:14,467 INFO [cloud.agent.AgentShell] (main:null) > > (logid:) Defaulting to the constant time backoff algorithm > > 2021-12-15 18:04:14,471 INFO [cloud.utils.LogUtils] (main:null) (logid:) > > log4j configuration found at /etc/cloudstack/agent/log4j-cloud.xml > > 2021-12-15 18:04:14,485 INFO [cloud.agent.AgentShell] (main:null) > > (logid:) Using default Java settings for IPv6 preference for agent > > connection > > 2021-12-15 18:04:14,592 INFO [cloud.agent.Agent] (main:null) (logid:) id > > is 0 > > 2021-12-15 18:04:14,606 ERROR [kvm.resource.LibvirtComputingResource] > > (main:null) (logid:) uefi properties file not found due to: Unable to find > > file uefi.properties. > > 2021-12-15 18:04:14,663 INFO [kvm.resource.LibvirtConnection] (main:null) > > (logid:) No existing libvirtd connection found. Opening a new one > > 2021-12-15 18:04:14,890 INFO [kvm.resource.LibvirtComputingResource] > > (main:null) (logid:) No libvirt.vif.driver specified. Defaults to > > BridgeVifDriver. > > 2021-12-15 18:04:15,086 INFO [kvm.resource.LibvirtComputingResource] > > (main:null) (logid:) iscsi session clean up is disabled > > 2021-12-15 18:04:15,129 INFO [cloud.agent.Agent] (main:null) (logid:) > > Agent [id = 0 : type = LibvirtComputingResource : zone = 1 : pod = 1 : > > workers = 5 : host = 192.168.30.59 : port = 8250 > > 2021-12-15 18:04:15,139 INFO [utils.nio.NioClient] (main:null) (logid:) > > Connecting to 192.168.30.59:8250 > > 2021-12-15 18:04:15,153 INFO [utils.nio.Link] (main:null) (logid:) Conf > > file found: /etc/cloudstack/agent/agent.properties > > 2021-12-15 18:04:15,919 INFO [utils.nio.NioClient] (main:null) (logid:) > > SSL: Handshake done > > 2021-12-15 18:04:15,920 INFO [utils.nio.NioClient] (main:null) (logid:) > > Connected to 192.168.30.59:8250 > > 2021-12-15 18:04:16,057 INFO [kvm.storage.LibvirtStorageAdaptor] > >
Re: Issues with libvirt after upgrading to RockyLinux 8.5
Can't add host: 192.168.30.54 with hostOS: Rocky into a cluster,in which there are CentOS hosts added Try changing the content of the /etc/*release file - to match the file of the CentOS nodes - and then play with restarting agent, and observe if you would hit the same error or not - I've seen this issue (RHEL inside CentOS cluster, due to bad /etc/rhel-release file content), but I've not tested if this "fix" works or not. Best, On Thu, 16 Dec 2021 at 08:39, Jeremy Hansen wrote: > But if I convert all the hosts to Rocky and upgrade to 4.16, I should be > ok? > > Thanks > > > > On Wednesday, Dec 15, 2021 at 11:17 PM, Slavka Peleva < > slav...@storpool.com.INVALID> wrote: > Sorry, I didn't pay attention to your CS version. After the upgrade, I > think you will have the same problem. Because in the DB, there is > information about host/hosts on this cluster that is/are with CentOS. > > Best regards, > Slavka > > On Thu, Dec 16, 2021 at 8:49 AM Jeremy Hansen > wrote: > > I noticed in the compatibility matrix that Rocky isn’t supported until > 4.16.0.0. If I upgrade Cloudstack first, would this help or is it still > going to complain about the centos/rocky mix? If I convert all my existing > nodes to Rocky, which is the plan anyway, will this go away? Shouldn’t > CentOS and Rocky be considered that same thing… sort of…? > > Thanks > -jeremy > > > > > On Wednesday, Dec 15, 2021 at 10:43 PM, Slavka Peleva < > slav...@storpool.com.INVALID> wrote: > Hi Jeremy, > > It will help if you have another cluster for Rocky Linux. Hosts need to be > of the same OS, it's not possible to mix OSes in the same cluster. > > Best regards, > Slavka > > On Thu, Dec 16, 2021 at 4:08 AM Jeremy Hansen > wrote: > > Any tips on how I would troubleshoot this? I’ve tried downgrading libvirt > and qemu and ca-certificates to the same version as the other functional > nodes. That didn’t seem to help. This is obviously an ssl issue but I > don’t really know what to do about it. > > 2021-12-15 18:04:14,438 INFO [cloud.agent.AgentShell] (main:null) > (logid:) Agent started > 2021-12-15 18:04:14,444 INFO [cloud.agent.AgentShell] (main:null) > (logid:) Implementation Version is 4.15.0.0 > 2021-12-15 18:04:14,447 INFO [cloud.agent.AgentShell] (main:null) > (logid:) agent.properties found at /etc/cloudstack/agent/agent.properties > 2021-12-15 18:04:14,466 INFO [cloud.agent.AgentShell] (main:null) > (logid:) Defaulting to using properties file for storage > 2021-12-15 18:04:14,467 INFO [cloud.agent.AgentShell] (main:null) > (logid:) Defaulting to the constant time backoff algorithm > 2021-12-15 18:04:14,471 INFO [cloud.utils.LogUtils] (main:null) (logid:) > log4j configuration found at /etc/cloudstack/agent/log4j-cloud.xml > 2021-12-15 18:04:14,485 INFO [cloud.agent.AgentShell] (main:null) > (logid:) Using default Java settings for IPv6 preference for agent > connection > 2021-12-15 18:04:14,592 INFO [cloud.agent.Agent] (main:null) (logid:) id > is 0 > 2021-12-15 18:04:14,606 ERROR [kvm.resource.LibvirtComputingResource] > (main:null) (logid:) uefi properties file not found due to: Unable to find > file uefi.properties. > 2021-12-15 18:04:14,663 INFO [kvm.resource.LibvirtConnection] (main:null) > (logid:) No existing libvirtd connection found. Opening a new one > 2021-12-15 18:04:14,890 INFO [kvm.resource.LibvirtComputingResource] > (main:null) (logid:) No libvirt.vif.driver specified. Defaults to > BridgeVifDriver. > 2021-12-15 18:04:15,086 INFO [kvm.resource.LibvirtComputingResource] > (main:null) (logid:) iscsi session clean up is disabled > 2021-12-15 18:04:15,129 INFO [cloud.agent.Agent] (main:null) (logid:) > Agent [id = 0 : type = LibvirtComputingResource : zone = 1 : pod = 1 : > workers = 5 : host = 192.168.30.59 : port = 8250 > 2021-12-15 18:04:15,139 INFO [utils.nio.NioClient] (main:null) (logid:) > Connecting to 192.168.30.59:8250 > 2021-12-15 18:04:15,153 INFO [utils.nio.Link] (main:null) (logid:) Conf > file found: /etc/cloudstack/agent/agent.properties > 2021-12-15 18:04:15,919 INFO [utils.nio.NioClient] (main:null) (logid:) > SSL: Handshake done > 2021-12-15 18:04:15,920 INFO [utils.nio.NioClient] (main:null) (logid:) > Connected to 192.168.30.59:8250 > 2021-12-15 18:04:16,057 INFO [kvm.storage.LibvirtStorageAdaptor] > (Agent-Handler-1:null) (logid:) Attempting to create storage pool > 18796842-a137-475d-9799-9874240e3c0c (Filesystem) in libvirt > 2021-12-15 18:04:16,062 ERROR [kvm.resource.LibvirtConnection] > (Agent-Handler-1:null) (logid:) Connection with libvirtd is broken: > invalid > connection pointer in virConnectGetVersion > 2021-12-15 18:04:16,066 INFO [kvm.storage.LibvirtStorageAdaptor] > (Agent-Handler-1:null) (logid:) Found existing defined storage pool > 18796842-a137-475d-9799-9874240e3c0c, using it. > 2021-12-15 18:04:16,066 INFO [kvm.storage.LibvirtStorageAdaptor] > (Agent-Handler-1:null) (logid:) Trying to fetch storage pool > 18796842-a137-475d-9799-9874240e3c0c from libvirt > 2021-12-15 18:04:16,151 INFO
