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 -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> 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/users@ovirt.org/message/PXEFMZF3ZHF...