GPL-935 BUG - Failure on re-creating list of printers in cups on startup (C=M, V=4) about print_my_barcode

[BenTopping]

Line 5 of the shell script is: send -- "$env(CUPSD_PASSWORD)\n"
I would suspect the instance the script was running on did not have the CUPSD_PASSWORD environmental variable set and it could not find it so error'd. Need to find where CUPSD_PASSWORD is being set and make sure it is set before the script is run.
Should also probably be wrapping the send in a try/or statement.

[KatyTaylor]

Moving this to the UAT column for someone to test if it's still an issue.
Restart PMB and check the error logs.

[sdjmchattie]

I logged into pmb-uat and ran docker restart on the print my barcode container and I saw only one error message when it was restarting mkdir: cannot create directory ‘/etc/cups/’: File exists which I think is fine. I would say this looks fixed, but I didn't see it broken.

[BenTopping]

SUSPECTED issue: running the script deploy_samples_extraction.yml in the deployment project also deployed / affected PMB since they are in the same stack, potentially it deployed PMB without the CUPS password which caused the error.

[BenTopping]

Another possible cause is the docker start-up order for the saex pmb stack. PMB depends on the cupsd instance to be available for the command to execute correctly, so if its not available (PMB container spins up before the cupsd one) it could cause an error like this

[harrietc52]

There is a script somewhere, which sometimes fails. As PMB is in a docker container, may require extra config?