[Bug]: deploying nodes in orchestrator fails

[kvdb-surf]

Contact Details

No response

What happened?

While following the workshop (docs/workshops/advanced/execute-workflows.md), I got stuck at the deploying the nodes section. It seems to work without running docker with lso, but with lso enabled to get the full workshop experience, it fails.

view from orchestrator:

view from docker compose:

Hope this can be fixed. Or perhaps there's something I missed while workshopping.

Version

main

What python version are you seeing the problem on?

No response

Relevant log output

[kvklink]

It looks like LSO is unable to find the playbooks that should be available for this workflow. I had a look around, and could you try modifying docker/lso/lso.env to include the following line:
ANSIBLE_PLAYBOOKS_ROOT_DIR="/app/wfo/ansible"
Please let me know if this fixes the issue for you, and then we can open a PR that resolves this

[kvdb-surf]

Thanks for your response.
That doesn't seem to fix it. That fixes it, but now reveals another issue.

This is the change made as requested:

diff --git a/docker/lso/lso.env b/docker/lso/lso.env
index 59763db..1a8dc97 100644
--- a/docker/lso/lso.env
+++ b/docker/lso/lso.env
@@ -1,7 +1,7 @@
 # Environment configuration for LSO application
 
 # Ansible configuration
-ANSIBLE_PLAYBOOKS_ROOT_DIR="/app/demo/ansible/ansible_collections"
+ANSIBLE_PLAYBOOKS_ROOT_DIR="/app/wfo/ansible"
 ANSIBLE_ROLES_PATH="/app/demo/ansible"
 ANSIBLE_HOST_KEY_CHECKING: "False"

[kvklink]

Thanks for the reply. With some more tinkering in my local environment, I was able to solve that issue as well, but now I've landed at a third, new issue! Is this making any sense to you?

[kvdb-surf]

No, doesn't ring a bell to me. Perhaps @Mark90 or @pboers1988?

All this time I wondered if those unpinned srlinux containers inside clab/srlinux01.clab.yaml could be a source of trouble, maybe a breaking change was introduced upstream since someone went through the whole workshop.

[Mark90]

Not directly.

I've not worked on this project, though have worked with Ansible quite a bit - although that's been a while ago. From what I remember, fact gathering depends on certain commands/executables to be present for ansible to gather information about the target host. Perhaps, as you said, something changed upstream in the srlinux that removed/changed this dependency.

It might be worth trying to pin srlinux to an older version?

[kvdb-surf]

Perhaps you can push a draft PR of your fixes so far @kvklink , then I could try out some different versions of the docker images on top. I already tried pinning several versions of srlinux before, but that wasn't fixing the issue I was experiencing at the time, it might be different this time.

[kvklink]

I've opened a draft PR #34, let's see if pinning the srlinux image helps

[kvdb-surf]

Thanks, I'll let you know.

[kvdb-surf]

Ok, I tried a few. Different results, but not the success I was hoping for.

• nokia/srlinux:24.10.4: "fatal: [clab-orch-demo-ams-pe]: FAILED! => {\"changed\": false, \"msg\": \"No fact modules available and we could not find a fact module for your network OS (nokia.srlinux.srlinux), try setting one via theFACTS_MODULES configuration.\"}\n",
• nokia/srlinux:23.10.5: fails to deploy
• nokia/srlinux:24.10.1: same err as 24.10.4
• nokia/srlinux:25.3.2: hangs after the 1st "install node config" step, doesn't start the next "install node config" step.
• nokia/srlinux:25.3.1: same err as 24.10.4
• nokia/srlinux:24.7.2: hangs after the 1st "install node config" step, doesn't start the next "install node config" step.