# Warning alert:Documentation Syntax Error: cannot parse plugin documention. **URL:** \ **Category:** Get Help\ **Tags:** ansible-lint, galaxy-ng\ **Created:** [July 1, 2026, 12:33pm UTC](https://forum.ansible.com/t/warning-alert-documentation-syntax-error-cannot-parse-plugin-documention/46013 "2026-07-01T12:33:49Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Sandip](https://avatars.discourse-cdn.com/v4/letter/s/ecae2f/32.png) [@Sandip](https://forum.ansible.com/u/Sandip)\ **Post date:** [July 1, 2026, 12:33pm UTC](https://forum.ansible.com/t/warning-alert-documentation-syntax-error-cannot-parse-plugin-documention/46013/1 "2026-07-01T12:33:49Z")
Hi Everyone, **ibm.storage\_virtualize** collection is successfully uploaded to the Galaxy portal after passing all the required checks, including: - `ansible-test sanity` - `ansible-test units` - `ansible-lint` None of these tests reported any issues. However, after the collection is uploaded, a few modules display the following warning on Galaxy: > **Warning:** Documentation Syntax Error: cannot parse plugin documentation. ![Screenshot 2026-07-01 at 3.38.28 PM](https://us1.discourse-cdn.com/ansible/original/2X/7/7a12e341045a5141aa299a84f90177f5002b7d55.png) To investigate further, I generated the collection documentation locally using **antsibull** by following the official documentation: > **[Linting collection docs - Creating a collection docsite - antsibull-docs –...](https://docs.ansible.com/projects/antsibull-docs/collection-docs/#linting-collection-docs)** > > antsibull-docs can be used to create a docsite for an individual collection. For example, take a look at the community.crypto docsite built from the latest commit to the community.crypto repository. This document explains how you can build such a... The documentation is generated successfully, and the affected modules are parsed correctly without any errors. I have attached a screenshot of the local output as well. ![Screenshot 2026-07-01 at 3.39.03 PM](https://us1.discourse-cdn.com/ansible/original/2X/d/d7dd0b4c887cecb29f28703db9c1e2258d491a3a.png) At this point, I’m not sure what I’m missing. Since the collection passes all the standard tests and the documentation builds successfully locally, I’m wondering: - Is there an additional validation performed by Ansible Galaxy that isn’t covered by `ansible-test` or `antsibull`? - Has there been a recent change or update in Galaxy’s documentation parser? - Has anyone else encountered this issue, and if so, what was the cause? Any suggestions or pointers would be greatly appreciated. > One more thing I noticed is that the same > **“Documentation Syntax Error: cannot parse plugin documentation”** > warning is also shown for all of the previous versions of the collection, not just the latest release. This makes me think the issue may not be related to the recent changes in the collection itself. Could this be an issue with the Galaxy documentation parser or the Galaxy portal? ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [July 1, 2026, 3:54pm UTC](https://forum.ansible.com/t/warning-alert-documentation-syntax-error-cannot-parse-plugin-documention/46013/2 "2026-07-01T15:54:48Z")
It’s a known bug in Galaxy, and has been there for some time (there was some discussion about htis a few weeks before I created the issue on Matrix): [Docs formatting broken on Galaxy for all modules/plugins that use `M(...)` (and likely also `P(...)`) in markup · Issue #5586 · ansible/ansible-hub-ui · GitHub](https://github.com/ansible/ansible-hub-ui/issues/5586) ---
**Author:** ![Sandip](https://avatars.discourse-cdn.com/v4/letter/s/ecae2f/32.png) [@Sandip](https://forum.ansible.com/u/Sandip)\ **Post date:** [July 2, 2026, 4:14am UTC](https://forum.ansible.com/t/warning-alert-documentation-syntax-error-cannot-parse-plugin-documention/46013/3 "2026-07-02T04:14:40Z")
Thank You @felixfontein , for confirming that the issue isn’t with the collection and is instead related to Galaxy. I’ll keep an eye on the GitHub issue you mentioned. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [July 17, 2026, 6:07am UTC](https://forum.ansible.com/t/warning-alert-documentation-syntax-error-cannot-parse-plugin-documention/46013/4 "2026-07-17T06:07:59Z")
Right now there is this issue, which has been around for some time with no reaction at all, and there’s another problem, namely that ansible-hub-ui’s dev environment is broken ([Dev environment does not work · Issue #5587 · ansible/ansible-hub-ui · GitHub](https://github.com/ansible/ansible-hub-ui/issues/5587)), so without first having to spend some time to get that working again, it’s not possible to develop a fix and actually test it. Is there any way to get attention to these problems from the repository’s maintainers side, or Red Hat in general? Also I’m wondering whether the repository’s code is only used for Ansible Galaxy, or also for Automation Hub etc. My impression was the latter, but I’m not sure. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [August 25, 2026, 6:24pm UTC](https://forum.ansible.com/t/warning-alert-documentation-syntax-error-cannot-parse-plugin-documention/46013/5 "2026-08-25T18:24:45Z")
This is now (mostly) fixed. The documentation is shown again, though links to other modules/plugins don’t work and just the module/plugin name are printed. ---
**Author:** ![Sandip](https://avatars.discourse-cdn.com/v4/letter/s/ecae2f/32.png) [@Sandip](https://forum.ansible.com/u/Sandip)\ **Post date:** [August 26, 2026, 4:29am UTC](https://forum.ansible.com/t/warning-alert-documentation-syntax-error-cannot-parse-plugin-documention/46013/6 "2026-08-26T04:29:16Z")
Thank You @felixfontein