nomad-pack stop / destroy fail on periodic jobs

[Kenshir0]

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.

[jrasell]

Hi @Kenshir0 and thanks for raising this issue. It looks like we are not correctly handling the fact that periodic child jobs have a prefix built from their parent. I'll mark this for roadmapping.