We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
I've just noticed an issue while testing my first Nomad pack, which deploys a periodic job.
nomad-pack stop / destroy commands fail with the following error:
skipping job "my-test" - conflict check failed with err: prefix matched multiple jobs ID Namespace Type Priority Status Submit Date my-test default batch/periodic 50 running 2024-06-04T17:34:20+02:00 my-test/periodic-1717515273 default batch 50 dead 2024-06-04T17:34:33+02:00 Pack "postgres_db_backup" destroy complete with errors ! Error Destroying Pack Error: prefix matched multiple jobs ID Namespace Type Priority Status Submit Date my-test default batch/periodic 50 running 2024-06-04T17:34:20+02:00 my-test/periodic-1717515273 default batch 50 dead 2024-06-04T17:34:33+02:00 Context: - Registry Name: myregistry - Pack Name: postgres_db_backup - Pack Ref: latest - Deployment Name: my-test
I'm not sure if I'm missing something here. As a workaround I can use the Nomad CLI stop command, which works just fine, but it's not very convenient.
nomad-pack version: Nomad Pack v0.1.1 (5159a77) nomad CLI / server version: 1.7.3
Let me know if you need more info.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
I've just noticed an issue while testing my first Nomad pack, which deploys a periodic job.
nomad-pack stop / destroy commands fail with the following error:
I'm not sure if I'm missing something here. As a workaround I can use the Nomad CLI stop command, which works just fine, but it's not very convenient.
nomad-pack version: Nomad Pack v0.1.1 (5159a77)
nomad CLI / server version: 1.7.3
Let me know if you need more info.
The text was updated successfully, but these errors were encountered: