Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-4.8] Bug 2075043: golang toolchain unsupported parsers tag #1240

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #1239

/assign aojea

The RH golang toolchain has backported the strict parsers for IP
addresses, but Openshift can't invalidate that that was previously
valid, hence the golang team added a tag to keep the loose parsers

Signed-off-by: Antonio Ojea <antonio.ojea.garcia@gmail.com>
@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Apr 13, 2022
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@aojea
Copy link

aojea commented Apr 13, 2022

/assign @soltysh

@openshift-ci
Copy link

openshift-ci bot commented Apr 13, 2022

@openshift-cherrypick-robot: Bugzilla bug 2073153 has been cloned as Bugzilla bug 2075043. Retitling PR to link against new bug.
/retitle [release-4.8] Bug 2075043: golang toolchain unsupported parsers tag

In response to this:

[release-4.8] Bug 2073153: golang toolchain unsupported parsers tag

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 openshift-ci bot changed the title [release-4.8] Bug 2073153: golang toolchain unsupported parsers tag [release-4.8] Bug 2075043: golang toolchain unsupported parsers tag Apr 13, 2022
@openshift-ci openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Apr 13, 2022
@openshift-ci
Copy link

openshift-ci bot commented Apr 13, 2022

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2075043, which is invalid:

  • expected dependent Bugzilla bug 2073153 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead

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:

[release-4.8] Bug 2075043: golang toolchain unsupported parsers tag

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 openshift-ci bot requested review from soltysh and sttts April 13, 2022 13:41
@tkashem
Copy link

tkashem commented Apr 18, 2022

/remove-label backports/unvalidated-commits
/label backports/validated-commits

@openshift-ci openshift-ci bot added backports/validated-commits Indicates that all commits come to merged upstream PRs. and removed backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. labels Apr 18, 2022
@tkashem
Copy link

tkashem commented Apr 18, 2022

/bugzilla refresh

@openshift-ci openshift-ci bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Apr 18, 2022
@aojea
Copy link

aojea commented Apr 18, 2022

/retest required

@openshift-ci
Copy link

openshift-ci bot commented Apr 18, 2022

@tkashem: This pull request references Bugzilla bug 2075043, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.8.z) matches configured target release for branch (4.8.z)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2073153 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2073153 targets the "4.9.z" release, which is one of the valid target releases: 4.9.0, 4.9.z
  • bug has dependents

Requesting review from QA contact:
/cc @wangke19

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 openshift-ci bot requested a review from wangke19 April 18, 2022 16:24
@openshift-ci
Copy link

openshift-ci bot commented Apr 18, 2022

@aojea: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test configmap-scale
  • /test e2e-agnostic-cmd
  • /test e2e-aws
  • /test e2e-aws-csi
  • /test e2e-aws-downgrade
  • /test e2e-aws-fips
  • /test e2e-aws-jenkins
  • /test e2e-aws-multitenant
  • /test e2e-aws-ovn
  • /test e2e-aws-serial
  • /test e2e-aws-upgrade
  • /test e2e-azure
  • /test e2e-azure-upgrade
  • /test e2e-gcp
  • /test e2e-gcp-upgrade
  • /test e2e-metal-ipi
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-ovn-ipv6
  • /test e2e-vsphere
  • /test images
  • /test integration
  • /test k8s-e2e-conformance-aws
  • /test k8s-e2e-gcp
  • /test k8s-e2e-gcp-serial
  • /test unit
  • /test verify
  • /test verify-commits

The following commands are available to trigger optional jobs:

  • /test e2e-aws-csi-migration
  • /test e2e-aws-disruptive
  • /test e2e-aws-single-node

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

  • pull-ci-openshift-kubernetes-release-4.8-e2e-agnostic-cmd
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-csi
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-downgrade
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-fips
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-jenkins
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-multitenant
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-ovn
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-serial
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-upgrade
  • pull-ci-openshift-kubernetes-release-4.8-e2e-azure
  • pull-ci-openshift-kubernetes-release-4.8-e2e-azure-upgrade
  • pull-ci-openshift-kubernetes-release-4.8-e2e-gcp
  • pull-ci-openshift-kubernetes-release-4.8-e2e-gcp-upgrade
  • pull-ci-openshift-kubernetes-release-4.8-e2e-metal-ipi
  • pull-ci-openshift-kubernetes-release-4.8-e2e-metal-ipi-ovn-dualstack
  • pull-ci-openshift-kubernetes-release-4.8-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-kubernetes-release-4.8-e2e-vsphere
  • pull-ci-openshift-kubernetes-release-4.8-images
  • pull-ci-openshift-kubernetes-release-4.8-integration
  • pull-ci-openshift-kubernetes-release-4.8-k8s-e2e-conformance-aws
  • pull-ci-openshift-kubernetes-release-4.8-k8s-e2e-gcp
  • pull-ci-openshift-kubernetes-release-4.8-k8s-e2e-gcp-serial
  • pull-ci-openshift-kubernetes-release-4.8-unit
  • pull-ci-openshift-kubernetes-release-4.8-verify
  • pull-ci-openshift-kubernetes-release-4.8-verify-commits

In response to this:

/retest required

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.

@tkashem
Copy link

tkashem commented Apr 18, 2022

/retest

@tkashem
Copy link

tkashem commented Apr 18, 2022

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 18, 2022
@tkashem
Copy link

tkashem commented Apr 18, 2022

  1. If the Bugzilla associated with the PR has the "FastFix" keyword, the subjective assessment on the issue has already been done and a customer is impacted. These PRs should be prioritized for merge.
    • verified
    • does not apply
  2. The bug has significant impact either through severity, reduction in supportability, or number of users affected.
    • verified
    • does not apply
  3. For branches that are in the Maintenance lifecycle phase:
    • The bug is a critical fix, no reasonable workaround exists, and a recommendation for upgrade has been ruled out, or
    • The bug is a security related bug
    • Branch not in maintenance mode yet (current release + previous release for 90 days after current GA; everything older is in maintenance)
  4. The severity field of the bug must be set to accurately reflect criticality.
    • verified
  5. The PR was created with the cherry-pick bot OR the PR’s description is well formed with user-focused release notes that state the bug number, impact, cause, and resolution. Where appropriate, it should also contain information about how a user can identify whether a particular cluster is affected.
    • verified

@tkashem
Copy link

tkashem commented Apr 18, 2022

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Apr 18, 2022
@kasturinarra
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Apr 18, 2022
@marun
Copy link

marun commented Apr 18, 2022

Wielding my magic rubber stamp!
/lgtm
/approve

@openshift-ci
Copy link

openshift-ci bot commented Apr 18, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: marun, openshift-cherrypick-robot, tkashem

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 18, 2022
@sanchezl
Copy link

/test e2e-metal-ipi-ovn-ipv6

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

5 similar comments
@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@soltysh
Copy link

soltysh commented Apr 19, 2022

/test e2e-metal-ipi-ovn-ipv6

1 similar comment
@tkashem
Copy link

tkashem commented Apr 19, 2022

/test e2e-metal-ipi-ovn-ipv6

@mfojtik
Copy link

mfojtik commented Apr 19, 2022

/override e2e-metal-ipi-ovn-ipv6

Based on openshift/release#27535 and the fact the problem is being tracked and not related to this PR.

@openshift-ci
Copy link

openshift-ci bot commented Apr 19, 2022

@mfojtik: /override requires a failed status context or a job name to operate on.
The following unknown contexts were given:

  • e2e-metal-ipi-ovn-ipv6

Only the following contexts were expected:

  • ci/prow/e2e-agnostic-cmd
  • ci/prow/e2e-aws
  • ci/prow/e2e-aws-csi
  • ci/prow/e2e-aws-downgrade
  • ci/prow/e2e-aws-fips
  • ci/prow/e2e-aws-jenkins
  • ci/prow/e2e-aws-multitenant
  • ci/prow/e2e-aws-ovn
  • ci/prow/e2e-aws-serial
  • ci/prow/e2e-aws-upgrade
  • ci/prow/e2e-azure
  • ci/prow/e2e-azure-upgrade
  • ci/prow/e2e-gcp
  • ci/prow/e2e-gcp-upgrade
  • ci/prow/e2e-metal-ipi
  • ci/prow/e2e-metal-ipi-ovn-dualstack
  • ci/prow/e2e-metal-ipi-ovn-ipv6
  • ci/prow/e2e-vsphere
  • ci/prow/images
  • ci/prow/integration
  • ci/prow/k8s-e2e-conformance-aws
  • ci/prow/k8s-e2e-gcp
  • ci/prow/k8s-e2e-gcp-serial
  • ci/prow/unit
  • ci/prow/verify
  • ci/prow/verify-commits
  • pull-ci-openshift-kubernetes-master-e2e-agnostic-cmd
  • pull-ci-openshift-kubernetes-master-e2e-aws
  • pull-ci-openshift-kubernetes-master-e2e-aws-csi
  • pull-ci-openshift-kubernetes-master-e2e-aws-downgrade
  • pull-ci-openshift-kubernetes-master-e2e-aws-fips
  • pull-ci-openshift-kubernetes-master-e2e-aws-jenkins
  • pull-ci-openshift-kubernetes-master-e2e-aws-multitenant
  • pull-ci-openshift-kubernetes-master-e2e-aws-ovn
  • pull-ci-openshift-kubernetes-master-e2e-aws-serial
  • pull-ci-openshift-kubernetes-master-e2e-aws-upgrade
  • pull-ci-openshift-kubernetes-master-e2e-azure
  • pull-ci-openshift-kubernetes-master-e2e-azure-upgrade
  • pull-ci-openshift-kubernetes-master-e2e-gcp
  • pull-ci-openshift-kubernetes-master-e2e-gcp-upgrade
  • pull-ci-openshift-kubernetes-master-e2e-metal-ipi
  • pull-ci-openshift-kubernetes-master-e2e-metal-ipi-ovn-dualstack
  • pull-ci-openshift-kubernetes-master-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-kubernetes-master-e2e-vsphere
  • pull-ci-openshift-kubernetes-master-images
  • pull-ci-openshift-kubernetes-master-integration
  • pull-ci-openshift-kubernetes-master-k8s-e2e-conformance-aws
  • pull-ci-openshift-kubernetes-master-k8s-e2e-gcp
  • pull-ci-openshift-kubernetes-master-k8s-e2e-gcp-serial
  • pull-ci-openshift-kubernetes-master-unit
  • pull-ci-openshift-kubernetes-master-verify
  • pull-ci-openshift-kubernetes-master-verify-commits
  • tide

In response to this:

/override e2e-metal-ipi-ovn-ipv6

Based on openshift/release#27535 and the fact the problem is being tracked and not related to this 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.

@mfojtik
Copy link

mfojtik commented Apr 19, 2022

/override ci/prow/e2e-metal-ipi-ovn-ipv6

@openshift-ci
Copy link

openshift-ci bot commented Apr 19, 2022

@mfojtik: Overrode contexts on behalf of mfojtik: ci/prow/e2e-metal-ipi-ovn-ipv6

In response to this:

/override ci/prow/e2e-metal-ipi-ovn-ipv6

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.

@mfojtik mfojtik merged commit c89f6b3 into openshift:release-4.8 Apr 19, 2022
@openshift-ci
Copy link

openshift-ci bot commented Apr 19, 2022

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

Bugzilla bug 2075043 has been moved to the MODIFIED state.

In response to this:

[release-4.8] Bug 2075043: golang toolchain unsupported parsers tag

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
Copy link

openshift-ci bot commented Apr 19, 2022

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. backports/validated-commits Indicates that all commits come to merged upstream PRs. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.