18:05:47 releng/phatality: fetch stage(s): 100% (in-flight: 0; ok: 12; fail: 0; left: 0) 18:05:48 releng/phatality: config_deploy stage(s): 100% (in-flight: 0; ok: 12; fail: 0; left: 0) 18:05:51 ['/usr/bin/scap', 'deploy-local', '-v', '--repo', 'releng/phatality', '-g', 'default', 'promote', '--refresh-config'] (ran as deploy-service@logstash1032.eqiad.wmnet) returned [1]: Registering scripts in directory '/srv/deployment/releng/phatality-cache/revs/c2cb594a75503ba4c25e2e8653b56efa3950abba/scap/scripts' Registering scripts in directory '/srv/deployment/releng/phatality-cache/revs/c2cb594a75503ba4c25e2e8653b56efa3950abba/scap/scripts' Executing check 'install_zip' Check 'install_zip' failed: Removing existing phatality plugin before installation Removing phatality... Unable to remove plugin because of error: "EACCES: permission denied, unlink '/usr/share/opensearch-dashboards/plugins/phatality/opensearch_dashboards.json'" Executing check 'restart_dashboards' Check 'restart_dashboards' completed, output: 18:05:52 releng/phatality: promote stage(s): 100% (in-flight: 0; ok: 11; fail: 1; left: 0) 18:05:52 1 targets had deploy errors 18:05:52 1 targets failed
A general problem here is that a failing check does not appear to stop the next check from running. That's not acceptable if the checks are used for installation steps as they are in the phatality repo.