You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nomad will refresh container(s) and all is fine .. but using nomad-pack .. it reverts from a nomad-pack deployed app, to a normal container. If we try to update the container via CI as Normad-pack again .. it fails:
echo "${LOCAL_CERT}" > $CI_PROJECT_DIR/server.crt # collapsed multi-line command ! Failed Job Conflict Validation ! Error: job with id "project1" already exists and is not managed by nomad pack ! Context: ! Template Name: project1/templates/project1.nomad.tpl Error: Failed to deploy nomad pack Cleaning up project directory and file based variables 00:01 ERROR: Job failed: exit code 1
The only way for now is to remove the job and redeploy.
Is that expected ? How can we avoid it or is it a bug ?
hi,
right now we using Levant and templates, where we can edit / change / Consul variables for the running containers with a template entry like:
Nomad will refresh container(s) and all is fine .. but using nomad-pack .. it reverts from a nomad-pack deployed app, to a normal container. If we try to update the container via CI as Normad-pack again .. it fails:
The only way for now is to remove the job and redeploy.
Is that expected ? How can we avoid it or is it a bug ?
maybe related: #561
cu denny
The text was updated successfully, but these errors were encountered: