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
  • #243
Closed
Open
Issue created Feb 03, 2021 by Paolo Pantellini@paolo.pantelliniMaintainer

Cannot cancel planned transfers

When cancelling a PLANNED transfer via the REST interface, the following error pops up:

2021/02/03 13:03:50 [CRITICAL] Admin: Failed to create new history entry: the transfer's end date cannot be anterior to the start date

As the error says, this is due to the fact that, when cancelling a transfer, the transfer's end date is set to the current time. However, since the transfer hasn't started yet, this means that the end date is anterior to the start date, which is forbidden by the database validator. Thus the cancel will always fail because the database refuses the new history entry.

A solution to this problem would be to allow the transfer_history end_date column to be null, which would actually make more sense since cancelled transfers technically did not end (and thus should not have an "end" date).

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