Add default cifmw_installyamls_repos value in ci/playbooks/kuttl/run-kuttl-tests.yml

[amartyasinha]

Since zuul ci playbooks won't read group_vars until it is upgraded, add the value of the var using defaults. It was missing only at a single place, so this should help.

Depends-On: #3438

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[softwarefactory-project-zuul]

This change depends on a change that failed to merge.

Change #3438 is needed.

[amartyasinha]

recheck

[danpawlik]

this is incorrect. If we move values to group_vars/all, such default vars should not be done anymore.

[amartyasinha]

this is incorrect. If we move values to group_vars/all, such default vars should not be done anymore.

@danpawlik Yes, it makes sense, but since we have not merged the change which will ensure group_vars are read in ci/playbooks yet, we might need a way to provide the value of this var until that PR to include group_vars in ci/playbooks is merged or zuul is upgraded..

[softwarefactory-project-zuul]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/ab9e062da65d4557bdfaea0242164c59

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 38m 40s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 13m 34s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 24m 22s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 8m 05s
✔️ cifmw-pod-pre-commit SUCCESS in 7m 50s
❌ cifmw-multinode-kuttl RETRY_LIMIT in 5m 29s
✔️ build-push-container-cifmw-client SUCCESS in 19m 13s

[amartyasinha]

recheck

[evallesp]

this is incorrect. If we move values to group_vars/all, such default vars should not be done anymore.

@danpawlik Yes, it makes sense, but since we have not merged the change which will ensure group_vars are read in ci/playbooks yet, we might need a way to provide the value of this var until that PR to include group_vars in ci/playbooks is merged or zuul is upgraded..

Would it make sense to add a comment there to remove then?