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

Bug 1972351: Bump jenkins version 2.289.1 #1283

Conversation

akram
Copy link
Contributor

@akram akram commented Jun 15, 2021

No description provided.

@openshift-ci openshift-ci bot requested review from otaviof and sbose78 June 15, 2021 17:27
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 15, 2021
@akram akram changed the title Bump jenkins version 2.289.1 Bug 1972351: Bump jenkins version 2.289.1 Jun 15, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 15, 2021

@akram: This pull request references Bugzilla bug 1972351, which is invalid:

  • expected the bug to target the "4.9.0" release, but it targets "---" 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:

Bug 1972351: Bump jenkins version 2.289.1

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 added bugzilla/severity-unspecified Referenced Bugzilla bug's severity is unspecified for the PR. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Jun 15, 2021
@akram
Copy link
Contributor Author

akram commented Jun 15, 2021

/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 Jun 15, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 15, 2021

@akram: This pull request references Bugzilla bug 1972351, 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.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.9.0) matches configured target release for branch (4.9.0)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @jitendar-singh

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.

@akram
Copy link
Contributor Author

akram commented Jun 15, 2021

/cherry-pick release-4.8

@openshift-cherrypick-robot

@akram: once the present PR merges, I will cherry-pick it on top of release-4.8 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.8

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.

@akram akram force-pushed the 4.9-update-jenkins-version-2.282.1 branch from 9d4ed3f to f1f2e9b Compare June 15, 2021 23:33
@jkhelil
Copy link
Contributor

jkhelil commented Jun 16, 2021

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 16, 2021
@akram
Copy link
Contributor Author

akram commented Jun 16, 2021

/bugzilla refresh

@openshift-ci openshift-ci bot added bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent 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. and removed bugzilla/severity-unspecified Referenced Bugzilla bug's severity is unspecified for the PR. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Jun 16, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 16, 2021

@akram: This pull request references Bugzilla bug 1972351, which is invalid:

  • expected the bug to target the "4.9.0" release, but it targets "---" 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:

/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.

@akram
Copy link
Contributor Author

akram commented Jun 16, 2021

flake:

level=error msg=Error: [ERR]: Error building changeset: InvalidChangeBatch: [Tried to create resource record set [name='api-int.ci-op-rhwy6tr6-93a8f.origin-ci-int-aws.dev.rhcloud.com.', type='A'] but it already exists]
level=error msg=	status code: 400, request id: fdf6743a-2a4d-4f06-adb4-57b9a98e7a8b

/retest

@openshift-bot
Copy link
Contributor

/retest

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

@akram
Copy link
Contributor Author

akram commented Jun 16, 2021

flake:

ps://api.ci-op-6qnf70k8-93a8f.origin-ci-int-aws.dev.rhcloud.com:6443/api?timeout=32s": dial tcp 52.52.235.121:6443: connect: connection refused, skipping gathering machineconfigs.machineconfiguration.openshift.io due to error: Get "https://api.ci-op-6qnf70k8-93a8f.origin-ci-int-aws.dev.rhcloud.com:6443/api?timeout=32s": dial tcp 52.52.235.121:6443: connect: connection refused, skipping gathering kubeletconfigs.machineconfiguration.openshift.io due to error: Get "https://api.ci-op-6qnf70k8-93a8f.origin-ci-int-aws.dev.rhcloud.com:6443/api?timeout=32s": dial tcp 52.52.235.121:6443: connect: connection refused, skipping gathering containerruntimeconfigs.machineconfiguration.openshift.io due to error: Get "https://api.ci-op-6qnf70k8-93a8f.origin-ci-int-aws.dev.rhcloud.com:6443/api?timeout=32s": dial tcp 52.52.235.121:6443: connect: connection refused, skipping gathering configs.samples.operator.openshift.io/cluster due to error: Get "https://api.ci-op-6qnf70k8-93a8f.origin-ci-int-aws.dev.rhcloud.com:6443/api?timeout=32s": dial tcp 52.52.235.121:6443: connect: connection refused, skipping gathering namespaces/openshift-cluster-samples-operator due to error: Get "https://api.ci-op-6qnf70k8-93a8f.origin-ci-int-aws.dev.rhcloud.com:6443/api/v1/namespaces/openshift-cluster-samples-operator": dial tcp 52.52.235.121:6443: connect: connection refused, skipping gathering namespaces/openshift due to error: Get "https://api.ci-op-6qnf70k8-93a8f.origin-ci-int-aws.dev.rhcloud.com:6443/api/v1/namespaces/openshift": dial tcp 52.52.235.121:6443: connect: connection refused]The connection to the server api.ci-op-6qnf70k8-93a8f.origin-ci-int-aws.dev.rhcloud.com:6443 was refused - did you specify the right host or port?

/retest

@akram
Copy link
Contributor Author

akram commented Jun 16, 2021

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 16, 2021

@akram: This pull request references Bugzilla bug 1972351, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.9.0) matches configured target release for branch (4.9.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @jitendar-singh

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 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 Jun 16, 2021
@openshift-bot
Copy link
Contributor

/retest

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

@akram
Copy link
Contributor Author

akram commented Jun 16, 2021

Flake again

level=error msg=Error: [ERR]: Error building changeset: InvalidChangeBatch: [Tried to create resource record set [name='api.ci-op-6qnf70k8-93a8f.origin-ci-int-aws.dev.rhcloud.com.', type='A'] but it already exists]
level=error msg=	status code: 400, request id: 7f70e769-c8bc-4fd9-b91*-5e6999ac718*
level=error
level=error msg=  on ../tmp/openshift-install-4797*8636/route53/base.tf line 4*, in resource "aws_route53_record" "api_external_alias":
level=error msg=  4*: resource "aws_route53_record" "api_external_alias" {

/retest

@openshift-bot
Copy link
Contributor

/retest

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

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

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

@akram
Copy link
Contributor Author

akram commented Jun 16, 2021

/hold
wait for a bit, until flakes get stabilized

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 16, 2021
@akram
Copy link
Contributor Author

akram commented Jun 17, 2021

/lgtm
/override ci/prow/e2e-aws-jenkins
/override ci/prow/e2e-aws

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 17, 2021

@akram: you cannot LGTM your own PR.

In response to this:

/lgtm
/override ci/prow/e2e-aws-jenkins
/override ci/prow/e2e-aws

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
Contributor

openshift-ci bot commented Jun 17, 2021

@akram: Overrode contexts on behalf of akram: ci/prow/e2e-aws, ci/prow/e2e-aws-jenkins

In response to this:

/lgtm
/override ci/prow/e2e-aws-jenkins
/override ci/prow/e2e-aws

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.

@akram
Copy link
Contributor Author

akram commented Jun 17, 2021

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 17, 2021
@jkhelil
Copy link
Contributor

jkhelil commented Jun 17, 2021

/lgtm
/override ci/prow/e2e-aws-jenkins
/override ci/prow/e2e-aws

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 17, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akram, jkhelil

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

openshift-ci bot commented Jun 17, 2021

@jkhelil: Overrode contexts on behalf of jkhelil: ci/prow/e2e-aws, ci/prow/e2e-aws-jenkins

In response to this:

/lgtm
/override ci/prow/e2e-aws-jenkins
/override ci/prow/e2e-aws

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.

@gabemontero
Copy link
Contributor

@jkhelil @akram I see you all overrode the e2e's

are we sure this change will fix the e2e-*-builds failures we are seeing in openshift/origin and other repos?

did you confirm that whatever issues you were seeing were beyond the e2e-*-builds failures? ... not seeing any detail here on the precise nature of any flakes you encountered here.

@adambkaplan FYI

@jkhelil
Copy link
Contributor

jkhelil commented Jun 17, 2021

@gabemontero Yes we need to new kubernetes-client-api, bumped in the PR

@gabemontero
Copy link
Contributor

@gabemontero Yes we need to new kubernetes-client-api, bumped in the PR

ok thanks @jkhelil

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 17, 2021

@akram: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws f1f2e9b link /test e2e-aws

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.

@openshift-merge-robot openshift-merge-robot merged commit 18fb26c into openshift:master Jun 17, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 17, 2021

@akram: All pull requests linked via external trackers have merged:

Bugzilla bug 1972351 has been moved to the MODIFIED state.

In response to this:

Bug 1972351: Bump jenkins version 2.289.1

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-cherrypick-robot

@akram: new pull request created: #1290

In response to this:

/cherry-pick release-4.8

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.

@akram
Copy link
Contributor Author

akram commented Jun 18, 2021

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. bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent 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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants