openshift-ansible icon indicating copy to clipboard operation
openshift-ansible copied to clipboard

Published 20 hours ago • verified publisher icon openshift

[release-4.8] Bug 2040488: Unit tests to use python 3.7

Open openshift-cherrypick-robot opened this issue 2 years ago • 228 comments

This is an automated cherry-pick of #12372

/assign patrickdillon

openshift-cherrypick-robot avatar Mar 16 '22 13:03 openshift-cherrypick-robot

I don't see any other residual references to python3.6 or any other version of python

barbacbd avatar Apr 18 '22 14:04 barbacbd

/lgtm

barbacbd avatar Apr 18 '22 14:04 barbacbd

/approve /label backport-risk-assessed

patrickdillon avatar Apr 21 '22 16:04 patrickdillon

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: barbacbd, openshift-cherrypick-robot, patrickdillon

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:

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

openshift-ci[bot] avatar Apr 21 '22 16:04 openshift-ci[bot]

/bugzilla refresh

patrickdillon avatar Jun 03 '22 18:06 patrickdillon

@patrickdillon: This pull request references Bugzilla bug 2040488, which is invalid:

  • expected the bug to target the "4.8.z" release, but it targets "4.11.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
  • expected Bugzilla bug 2040488 to depend on a bug targeting a release in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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.

openshift-ci[bot] avatar Jun 03 '22 18:06 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-bot avatar Jun 04 '22 01:06 openshift-bot

@openshift-bot: This pull request references Bugzilla bug 2040488, which is invalid:

  • expected the bug to target the "4.8.z" release, but it targets "4.11.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
  • expected Bugzilla bug 2040488 to depend on a bug targeting a release in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

openshift-ci[bot] avatar Jun 04 '22 01:06 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-bot avatar Jun 05 '22 01:06 openshift-bot

@openshift-bot: This pull request references Bugzilla bug 2040488, which is invalid:

  • expected the bug to target the "4.8.z" release, but it targets "4.11.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
  • expected Bugzilla bug 2040488 to depend on a bug targeting a release in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

openshift-ci[bot] avatar Jun 05 '22 01:06 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-bot avatar Jun 06 '22 01:06 openshift-bot

@openshift-bot: This pull request references Bugzilla bug 2040488, which is invalid:

  • expected the bug to target the "4.8.z" release, but it targets "4.11.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
  • expected Bugzilla bug 2040488 to depend on a bug targeting a release in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

openshift-ci[bot] avatar Jun 06 '22 01:06 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-bot avatar Jun 07 '22 01:06 openshift-bot

@openshift-bot: This pull request references Bugzilla bug 2040488, which is invalid:

  • expected the bug to target the "4.8.z" release, but it targets "4.11.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
  • expected Bugzilla bug 2040488 to depend on a bug targeting a release in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

openshift-ci[bot] avatar Jun 07 '22 01:06 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-bot avatar Jun 08 '22 01:06 openshift-bot

@openshift-bot: This pull request references Bugzilla bug 2040488, which is invalid:

  • expected the bug to target the "4.8.z" release, but it targets "4.11.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
  • expected Bugzilla bug 2040488 to depend on a bug targeting a release in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

openshift-ci[bot] avatar Jun 08 '22 01:06 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-bot avatar Jun 09 '22 01:06 openshift-bot

@openshift-bot: This pull request references Bugzilla bug 2040488, which is invalid:

  • expected the bug to target the "4.8.z" release, but it targets "4.11.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
  • expected Bugzilla bug 2040488 to depend on a bug targeting a release in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

openshift-ci[bot] avatar Jun 09 '22 01:06 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-bot avatar Jun 10 '22 01:06 openshift-bot

@openshift-bot: This pull request references Bugzilla bug 2040488, which is invalid:

  • expected the bug to target the "4.8.z" release, but it targets "4.11.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
  • expected Bugzilla bug 2040488 to depend on a bug targeting a release in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

openshift-ci[bot] avatar Jun 10 '22 01:06 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-bot avatar Jun 11 '22 01:06 openshift-bot

@openshift-bot: This pull request references Bugzilla bug 2040488, which is invalid:

  • expected the bug to target the "4.8.z" release, but it targets "4.11.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
  • expected Bugzilla bug 2040488 to depend on a bug targeting a release in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

openshift-ci[bot] avatar Jun 11 '22 01:06 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-bot avatar Jun 12 '22 01:06 openshift-bot

@openshift-bot: This pull request references Bugzilla bug 2040488, which is invalid:

  • expected the bug to target the "4.8.z" release, but it targets "4.11.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
  • expected Bugzilla bug 2040488 to depend on a bug targeting a release in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

openshift-ci[bot] avatar Jun 12 '22 01:06 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-bot avatar Jun 13 '22 01:06 openshift-bot

@openshift-bot: This pull request references Bugzilla bug 2040488, which is invalid:

  • expected the bug to target the "4.8.z" release, but it targets "4.11.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
  • expected Bugzilla bug 2040488 to depend on a bug targeting a release in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

openshift-ci[bot] avatar Jun 13 '22 01:06 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-bot avatar Jun 14 '22 01:06 openshift-bot

@openshift-bot: This pull request references Bugzilla bug 2040488, which is invalid:

  • expected the bug to target the "4.8.z" release, but it targets "4.11.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
  • expected Bugzilla bug 2040488 to depend on a bug targeting a release in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

openshift-ci[bot] avatar Jun 14 '22 01:06 openshift-ci[bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-bot avatar Jun 15 '22 01:06 openshift-bot

@openshift-bot: This pull request references Bugzilla bug 2040488, which is invalid:

  • expected the bug to target the "4.8.z" release, but it targets "4.11.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
  • expected Bugzilla bug 2040488 to depend on a bug targeting a release in 4.9.0, 4.9.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

openshift-ci[bot] avatar Jun 15 '22 01:06 openshift-ci[bot]