image-builder icon indicating copy to clipboard operation
image-builder copied to clipboard

set python version to 3.9 minimum

Open cpanato opened this issue 1 year ago • 7 comments

Change description

  • set python version to 3.9 minimum

getting this error when building rhel-8 for capg

Python 3.6.x is no longer officially supported by the Google Cloud CLI\nand may not function correctly. 

job: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/periodic-image-builder-gcp-all-nightly/1781957253432086528

/assign @mboersma @dims

Related issues

  • Fixes #

Additional context

cpanato avatar Apr 21 '24 15:04 cpanato

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign jsturtevant for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

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

k8s-ci-robot avatar Apr 21 '24 15:04 k8s-ci-robot

/test ls

cpanato avatar Apr 21 '24 15:04 cpanato

@cpanato: The specified target(s) for /test were not found. The following commands are available to trigger required jobs:

  • /test json-sort-check
  • /test pull-azure-vhds
  • /test pull-goss-populate
  • /test pull-lint
  • /test pull-ova-all
  • /test pull-packer-validate

The following commands are available to trigger optional jobs:

  • /test pull-azure-sigs
  • /test pull-container-image-build
  • /test pull-image-builder-gcp-all

Use /test all to run the following jobs that were automatically triggered:

  • pull-azure-vhds
  • pull-lint
  • pull-ova-all

In response to this:

/test ls

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.

k8s-ci-robot avatar Apr 21 '24 15:04 k8s-ci-robot

/test pull-image-builder-gcp-all

cpanato avatar Apr 21 '24 15:04 cpanato

/lgtm

mboersma avatar Apr 21 '24 16:04 mboersma

/hold

looks like there is not the place : https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_image-builder/1447/pull-image-builder-gcp-all/1782072065260523520

:/

cpanato avatar Apr 21 '24 16:04 cpanato

@cpanato: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-image-builder-gcp-all 78351775eb54d5edecca0df923816f91c801b006 link false /test pull-image-builder-gcp-all
pull-ova-all 78351775eb54d5edecca0df923816f91c801b006 link true /test pull-ova-all

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

k8s-ci-robot avatar Apr 21 '24 16:04 k8s-ci-robot

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jul 30 '24 16:07 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle rotten
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar Aug 29 '24 17:08 k8s-triage-robot

/close

( based on last comment from @cpanato )

dims avatar Sep 21 '24 02:09 dims

@dims: Closed this PR.

In response to this:

/close

( based on last comment from @cpanato )

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-sigs/prow repository.

k8s-ci-robot avatar Sep 21 '24 02:09 k8s-ci-robot