Move yq parameters

[paramite]

Currently make openstack fails with yq installed via pip (yq 3.2.3). This patch make it work with it again.

[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://review.rdoproject.org/zuul/buildset/c82ae3f2d4214549afcdc2ee41213282

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 28m 42s
❌ install-yamls-crc-podified-edpm-baremetal RETRY_LIMIT in 13m 59s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 06m 53s
✔️ cifmw-data-plane-adoption-osp-17-to-extracted-crc SUCCESS in 2h 12m 27s

[paramite]

recheck

[jlarriba]

/lgtm

[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://review.rdoproject.org/zuul/buildset/1c48743fed0a4aa3970ebba3ded3ebcb

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 25m 43s
❌ install-yamls-crc-podified-edpm-baremetal RETRY_LIMIT in 12m 59s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 07m 28s
✔️ cifmw-data-plane-adoption-osp-17-to-extracted-crc SUCCESS in 2h 09m 04s

[fao89]

recheck

[fao89]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fao89, paramite

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [fao89]

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]

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://review.rdoproject.org/zuul/buildset/3b9d42cf36f743d38083e657ff27b5b4

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 42m 25s
❌ install-yamls-crc-podified-edpm-baremetal FAILURE in 25m 43s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 06m 14s
❌ cifmw-data-plane-adoption-osp-17-to-extracted-crc FAILURE in 1h 21m 19s

[paramite]

recheck

[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://review.rdoproject.org/zuul/buildset/923674aabc6c4bda8176a17a40bfba9f

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 19m 27s
❌ install-yamls-crc-podified-edpm-baremetal FAILURE in 25m 15s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 06m 58s
✔️ cifmw-data-plane-adoption-osp-17-to-extracted-crc SUCCESS in 2h 04m 23s

[fao89]

recheck

[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://review.rdoproject.org/zuul/buildset/b00c148c884d48b4bceadec2e05eae67

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 24m 06s
❌ install-yamls-crc-podified-edpm-baremetal RETRY_LIMIT in 14m 05s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 06m 08s
✔️ cifmw-data-plane-adoption-osp-17-to-extracted-crc SUCCESS in 2h 06m 29s

[abays]

recheck

[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://review.rdoproject.org/zuul/buildset/6cf74109a1474770971173f00fcaca3d

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 25m 16s
❌ install-yamls-crc-podified-edpm-baremetal FAILURE in 22m 29s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 06m 01s
✔️ cifmw-data-plane-adoption-osp-17-to-extracted-crc SUCCESS in 2h 10m 11s

[abays]

The baremetal job seems to consistently fail with this error:

 "error: must build at directory: not a valid directory: evalsymlink failure on '/home/zuul/ci-framework-data/artifacts/manifests/operator/baremetal-operator/config' : lstat /home/zuul/ci-framework-data/artifacts/manifests/operator: no such file or directory"

[paramite]

Studying the logs more deeply it fails with Error: unknown shorthand flag: 'y' in -y. Apparently version used by CI does not have -y option which unfortunately is required by version available in PIP. How is the job getting yq, so that I can get the same version in my lab? I guess we can give up on this PR until CI gets updated version.

[fao89]

I believe it gets yq from here: https://github.com/openstack-k8s-operators/install_yamls/blob/main/devsetup/roles/download_tools/tasks/main.yaml#L90

[ciecierski]

Hello,
@fao89 it is indeed [1] what causes problems. We should use yq from pip, not source. The yq from pip doesn't recognize -y flag, but it works without it just fine.

[1]https://github.com/openstack-k8s-operators/install_yamls/blob/main/devsetup/roles/download_tools/tasks/main.yaml#L116