# ansible-network GH workflows errors in openvswitch collection

**URL:** <https://forum.ansible.com/t/ansible-network-gh-workflows-errors-in-openvswitch-collection/45200>\
**Category:** Collection Development\
**Tags:** github, ci, network\
**Created:** [January 27, 2026, 12:50pm UTC](https://forum.ansible.com/t/ansible-network-gh-workflows-errors-in-openvswitch-collection/45200 "2026-01-27T12:50:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mnasiadka](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mnasiadka/32/9807_2.png) [@mnasiadka](https://forum.ansible.com/u/mnasiadka)\
**Post date:** [January 27, 2026, 12:50pm UTC](https://forum.ansible.com/t/ansible-network-gh-workflows-errors-in-openvswitch-collection/45200/1 "2026-01-27T12:50:09Z")

</div>

Hi,

Trying to revive testing for openvswitch.openvswitch collection I stumbled across this:

Error when evaluating ‘strategy’ for job ‘unit\_source’. ansible-network/github\_actions/.github/workflows/unit\_source.yml@main (Line: 128, Col: 18): Error from function ‘fromJSON’: empty input, ansible-network/github\_actions/.github/workflows/unit\_source.yml@main (Line: 128, Col: 18): Unexpected value ‘’

Details can be seen in [Fix ansible-lint errors · ansible-collections/openvswitch.openvswitch@e5ef4b9 · GitHub](https://github.com/ansible-collections/openvswitch.openvswitch/actions/runs/21387719694)

Does anyone have a clue what might be wrong?

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [January 27, 2026, 12:52pm UTC](https://forum.ansible.com/t/ansible-network-gh-workflows-errors-in-openvswitch-collection/45200/2 "2026-01-27T12:52:08Z")

</div>

As the GitHub Action Workflow is 2 years old, I’d maybe start by copying

> **[collection\_template/.github/workflows at main ·...](https://github.com/ansible-collections/collection_template/tree/main/.github/workflows)**
>
> A GitHub Template repo to use as the basis for future repos - ansible-collections/collection\_template

Remembering to add `ansible.netcommon` into `test-deps`

---

<div class="post-metadata">

**Author:** ![mnasiadka](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mnasiadka/32/9807_2.png) [@mnasiadka](https://forum.ansible.com/u/mnasiadka)\
**Post date:** [January 27, 2026, 1:00pm UTC](https://forum.ansible.com/t/ansible-network-gh-workflows-errors-in-openvswitch-collection/45200/3 "2026-01-27T13:00:04Z")

</div>

I think I had to learn GitHub Actions.  
First of all - variables won’t be available on a pull request from a fork  
And the variable was not holding a parseable JSON content - so that’s now working.

Trying to get a workable state of the repository - and then I can compare with the template.

Thanks for help!

---

<div class="post-metadata">

**Author:** ![mnasiadka](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mnasiadka/32/9807_2.png) [@mnasiadka](https://forum.ansible.com/u/mnasiadka)\
**Post date:** [January 27, 2026, 5:37pm UTC](https://forum.ansible.com/t/ansible-network-gh-workflows-errors-in-openvswitch-collection/45200/4 "2026-01-27T17:37:15Z")

</div>

Actually I could use more help - [unit\_galaxy: Fix undefined runs-on by mnasiadka · Pull Request #188 · ansible-network/github\_actions · GitHub](https://github.com/ansible-network/github_actions/pull/188#pullrequestreview-3712141699) needs a review, and that would unblock bringing openvswitch.openvswitch back to life

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [January 28, 2026, 9:59am UTC](https://forum.ansible.com/t/ansible-network-gh-workflows-errors-in-openvswitch-collection/45200/5 "2026-01-28T09:59:33Z")

</div>

@mnasiadka Good spot, thanks for investigating that and fixing it. From a quick look at the recent GitHub Action runs, it seems like this if fixed now. Please do let us know if there is anything else