kubernetes-sigs/image-builder

pull-ova-all job failing on CentOS 7: "No package matching 'jq' found"

mboersma opened this issue · 4 comments

mboersma commented

What steps did you take and what happened:

CI for pull requests began failing recently building the centos7 target in the pull-ova-all job which runs ./images/capi/scripts/ci-ova.sh. Here is one example:

https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_image-builder/1192/pull-ova-all/1669524159467622400/artifacts/centos-7.log

What did you expect to happen:

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

Project (Image Builder for Cluster API:

Additional info for Image Builder for Cluster API related issues:

  • OS (e.g. from /etc/os-release, or cmd /c ver):
  • Packer Version:
  • Packer Provider:
  • Ansible Version:
  • Cluster-api version (if using):
  • Kubernetes version: (use kubectl version):

/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels]

mboersma commented

/help

k8s-ci-robot commented

@mboersma:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

mboersma commented

/close

This hasn't recurred AFAICT, so let's not spend time investigating.

k8s-ci-robot commented

@mboersma: Closing this issue.

In response to this:

/close

This hasn't recurred AFAICT, so let's not spend time investigating.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.