Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • lava lava
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 64
    • Merge requests 64
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lava
  • lavalava
  • Issues
  • #591

Closed
Open
Created Feb 21, 2023 by Hervé Knochel@knochelhGuest

[2023.1] Internal Server Error when trying to assign a tag to a device

We recently upgraded one of our Lava testing instance to latest Lava release 2023.1 and since then, we are unable to assign a tag to any of our devices. Either through the admin interface or through lavacli, we encounter the following error message :

`# lavacli devices tags add qemu001 qemu

Unable to call 'devices.tags': <Fault -32603: 'Internal Server Error (contact server administrator for details): syntax error at or near "ON"\nLINE 1: ...gs" ("device_id", "tag_id") VALUES ('qemu001', 9) ON CONFLIC...\n ^\n'>`

Or through the administration interface: image

This error occurs both for already existing devices, as well as with newly created ones. Note that if the assigned tag does not exist, it gets created and appears in the the overall tags list, but the assignment to any device always fails. It is a regression, as tags assignment to devices works like a charm on our production instance in version 2022.11. Thanks for any advise on how to fix or workaround this issue.

Edited Feb 21, 2023 by Hervé Knochel
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking