Skip to content

Squelch "Cannot set fs attributes on a non-existent symlink target" message

Please squelch this message and remove the Known Issues section from the README. Instructions to squelch message included below. Leaves a FIXME in the code as a reminder to remove follow=Force at some later date.

Documented known issue: https://open.greenhost.net/openappstack/wordpress-helm#known-issues

Root cause: https://github.com/ansible/ansible/issues/50543

Workaround:

diff --git a/wp-cli-docker/roles/wordpress-init/tasks/main.yml b/wp-cli-docker/roles/wordpress-init/tasks/m
ain.yml
index 2990b60..62a2737 100644
--- a/wp-cli-docker/roles/wordpress-init/tasks/main.yml
+++ b/wp-cli-docker/roles/wordpress-init/tasks/main.yml
@@ -17,6 +17,7 @@
     state: link
     # Force this, because the WP UPLOAD DIR is not mounted to the initContainer
     force: yes
+    follow: False # FIXME: https://github.com/ansible/ansible/issues/50543
   when: WP_UPLOAD_DIR != wordpress_homedir + "/wp-content/uploads