[ovirt-users]Re: [extern] Re: PsqlException at Engine
Hi Jean, I had a similar issue for the rocky 9 and unable to add the host into ovirt after dnf update. getting similar error. 2025-08-08 21:20:23,560+05 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) [] Unable to RefreshCapabilities: PSQLException: ERROR: value too long for type character varying(4000) Where: SQL statement "UPDATE vds_dynamic SET cpu_flags = v_cpu_flags WHERE vds_id = v_vds_id" PL/pgSQL function updatecpuflags(uuid,character varying) line 3 at SQL statement Any recommendation for rocky 9? Going to update in the github too.. ___ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives:
[ovirt-users] Re: [extern] Re: PsqlException at Engine
https://github.com/oVirt/ovirt-engine/issues This would be the place :) On 7/07/2025 08:59, Christoph Koehler wrote: Hi, Could you please send me a link to the repo you mean? Christoph Am 07.07.25 um 08:47 schrieb Jean-Louis Dupond via Users: Hi, Interesting :) Could you do me a favour, and create an issue on github so it can get tracked? Please also include the cpu flags of that CPU if possible. Then I'll get this fixed for the next release! Thanks Jean-Louis On 7/07/2025 08:20, Christoph Koehler wrote: Dear all, Since the last host update to the latest master snapshot, we have encountered a situation where hosts with the following CPU can no longer be activated: Xeon Gold 5418Y. The error comes from a database function of the engine: "PSQLEXCEPTION: ERROR: value too long for type character varying(4000) Where: SQL statement "UPDATE vds_dynamic SET cpuflags = vcpu_flags WHERE vdsid = vvds_id" PL/pgSQL function updatecpuflags(uuid, character varying) line 3 at SQL statement" Since the update, the length of the CPU flags exceeds the datatype varchar(4000) as declared in the DB. Currently, we have no solution, and the nodes remain 'unassigned'. Does anyone know of a workaround or when this presumably known error will be fixed? Thank you and best regards, Christoph ___ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/PXEFMZF3ZHF5ARWSOM2NYFZRRFSI454A/ ___ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/S2BXBO3XUGKAXEQJRBECPDJFE77FPBDY/ ___ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/5EBCYXW3FBOV5LHMACN3Q5EFVEQHGGO3/
[ovirt-users] Re: [extern] Re: PsqlException at Engine
Hi, Could you please send me a link to the repo you mean? Christoph Am 07.07.25 um 08:47 schrieb Jean-Louis Dupond via Users: Hi, Interesting :) Could you do me a favour, and create an issue on github so it can get tracked? Please also include the cpu flags of that CPU if possible. Then I'll get this fixed for the next release! Thanks Jean-Louis On 7/07/2025 08:20, Christoph Koehler wrote: Dear all, Since the last host update to the latest master snapshot, we have encountered a situation where hosts with the following CPU can no longer be activated: Xeon Gold 5418Y. The error comes from a database function of the engine: "PSQLEXCEPTION: ERROR: value too long for type character varying(4000) Where: SQL statement "UPDATE vds_dynamic SET cpuflags = vcpu_flags WHERE vdsid = vvds_id" PL/pgSQL function updatecpuflags(uuid, character varying) line 3 at SQL statement" Since the update, the length of the CPU flags exceeds the datatype varchar(4000) as declared in the DB. Currently, we have no solution, and the nodes remain 'unassigned'. Does anyone know of a workaround or when this presumably known error will be fixed? Thank you and best regards, Christoph ___ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/PXEFMZF3ZHF5ARWSOM2NYFZRRFSI454A/ ___ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/S2BXBO3XUGKAXEQJRBECPDJFE77FPBDY/ smime.p7s Description: Kryptografische S/MIME-Signatur ___ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/3GMEFWY6TYBNVKAOSCXLYO4USTUEFP4D/
