QA (public) » openQA Project (public) » openQA Infrastructure (public)

Observation¶

worker40.oqa.prg2.suse.org:
----------
          ID: firewalld_zones
    Function: file.managed
        Name: /etc/firewalld/zones/trusted.xml
      Result: False
     Comment: Unable to manage file: name '__env__' is not defined
     Started: 13:36:50.135092
    Duration: 200.901 ms
     Changes:   
Summary for worker40.oqa.prg2.suse.org
--------------
Succeeded: 501
Failed:      1
--------------

from https://gitlab.suse.de/openqa/salt-pillars-openqa/-/jobs/2807754#L224

I have seen similar messages in other cases in sporadic failures. A rerun seems to fix this.

Acceptance criteria¶

• AC1: Consistently stable salt deployment jobs with no error "Unable to manage file: name 'env' is not defined"

Suggestions¶

• DONE Do upstream research on error message "Unable to manage file: name 'env' is not defined" -> https://github.com/search?q=repo%3Asaltstack%2Fsalt%20%20%22Unable%20to%20manage%20file%3A%20name%20%27__env__%27%20is%20not%20defined%22&type=code reveals nothing, so does https://www.ecosia.org/search?method=index&q=salt%20%22Unable%20to%20manage%20file%3A%20name%20%27__env__%27%20is%20not%20defined%22 . Only remotely similar https://github.com/saltstack/salt/issues/24273 but no helpful content.

Workaround¶

Retrigger the according CI job