Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • W Waarp Gateway
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 48
    • Issues 48
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Applications
  • Waarp Gateway
  • Waarp Gateway
  • Issues
  • #272
Closed
Open
Issue created Aug 31, 2021 by Paolo Pantellini@paolo.pantelliniMaintainer

Fix LocalAgent existance check during import

When importing a LocalAgent, the backup tool checks if the agent already exist in the database (to determine whether it should insert or update it). But the check is incorrect, because it does not take into account the owner of the LocalAgent when checking if it exists. In practice, this means if another gateway instance (which shares the database) has a LocalAgent with the same name, the backup tool will try to update that agent, instead of inserting a new one.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking