Skip to content

Bug 1845188: Revert "UPSTREAM: <carry>: Disable by default the addition of service ca to token secrets#25078

Merged
openshift-merge-robot merged 1 commit intoopenshift:release-4.5from
marun:revert-1813894
Jun 9, 2020
Merged

Bug 1845188: Revert "UPSTREAM: <carry>: Disable by default the addition of service ca to token secrets#25078
openshift-merge-robot merged 1 commit intoopenshift:release-4.5from
marun:revert-1813894

Conversation

@marun
Copy link
Copy Markdown
Contributor

@marun marun commented Jun 8, 2020

This reverts commit f24fbff.

/cc @mfojtik

@openshift-ci-robot
Copy link
Copy Markdown

@marun: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

Revert "UPSTREAM: : Disable by default the addition of service ca to token secrets

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-robot openshift-ci-robot added the vendor-update Touching vendor dir or related files label Jun 8, 2020
…ddition of service ca to token secrets"

This reverts commit f24fbff.
@mfojtik
Copy link
Copy Markdown
Contributor

mfojtik commented Jun 9, 2020

/retest

@mfojtik
Copy link
Copy Markdown
Contributor

mfojtik commented Jun 9, 2020

/lgtm

@mfojtik mfojtik added the staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). label Jun 9, 2020
@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 9, 2020
@openshift-ci-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: marun, mfojtik

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

The pull request process is described here

Details 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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 9, 2020
@mfojtik mfojtik added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Jun 9, 2020
@mfojtik mfojtik changed the title Revert "UPSTREAM: <carry>: Disable by default the addition of service ca to token secrets Bug 1845188: Revert "UPSTREAM: <carry>: Disable by default the addition of service ca to token secrets Jun 9, 2020
@openshift-ci-robot openshift-ci-robot added bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting. and removed bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Jun 9, 2020
@openshift-ci-robot
Copy link
Copy Markdown

@marun: This pull request references Bugzilla bug 1845188, which is invalid:

  • expected the bug to target the "4.5.0" release, but it targets "---" instead
  • expected Bugzilla bug 1845188 to depend on a bug targeting a release in 4.6.0, 4.6.z and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.

Details

In response to this:

Bug 1845188: Revert "UPSTREAM: : Disable by default the addition of service ca to token secrets

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-robot openshift-ci-robot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Jun 9, 2020
@mfojtik mfojtik 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 9, 2020
@mfojtik
Copy link
Copy Markdown
Contributor

mfojtik commented Jun 9, 2020

overriding valid-bug as there is no intent to revert this in master branch

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

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

1 similar comment
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

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

@mfojtik
Copy link
Copy Markdown
Contributor

mfojtik commented Jun 9, 2020

/bugzilla refresh

@openshift-ci-robot openshift-ci-robot removed the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Jun 9, 2020
@openshift-ci-robot
Copy link
Copy Markdown

@mfojtik: This pull request references Bugzilla bug 1845188, which is invalid:

  • expected Bugzilla bug 1845188 to depend on a bug targeting a release in 4.6.0, 4.6.z and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.

Details

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-robot openshift-ci-robot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Jun 9, 2020
@mfojtik mfojtik 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 9, 2020
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

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

1 similar comment
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

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

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

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

3 similar comments
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

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

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

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

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

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

@mfojtik
Copy link
Copy Markdown
Contributor

mfojtik commented Jun 9, 2020

/override ci/prow/e2e-aws-disruptive

This is known failure and should not be blocking

@openshift-ci-robot
Copy link
Copy Markdown

@mfojtik: Overrode contexts on behalf of mfojtik: ci/prow/e2e-aws-disruptive

Details

In response to this:

/override ci/prow/e2e-aws-disruptive

This is known failure and should not be blocking

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

mfojtik commented Jun 9, 2020

/override ci/prow/e2e-vsphere

this test is flaking on unrelated networking/router failures

@openshift-ci-robot
Copy link
Copy Markdown

@mfojtik: Overrode contexts on behalf of mfojtik: ci/prow/e2e-vsphere

Details

In response to this:

/override ci/prow/e2e-vsphere

this test is flaking on unrelated networking/router failures

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

mfojtik commented Jun 9, 2020

/override ci/prow/e2e-conformance-k8s

this passed last time on 2020-04-29: https://bugzilla.redhat.com/show_bug.cgi?id=1845549

@openshift-ci-robot
Copy link
Copy Markdown

@mfojtik: Overrode contexts on behalf of mfojtik: ci/prow/e2e-conformance-k8s

Details

In response to this:

/override ci/prow/e2e-conformance-k8s

this passed last time on 2020-04-29, the TRT team will investigate

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-merge-robot openshift-merge-robot merged commit cc5c3e3 into openshift:release-4.5 Jun 9, 2020
@openshift-ci-robot
Copy link
Copy Markdown

@marun: All pull requests linked via external trackers have merged: . Bugzilla bug 1845188 has been moved to the MODIFIED state.

Details

In response to this:

Bug 1845188: Revert "UPSTREAM: : Disable by default the addition of service ca to token secrets

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.

@runcom
Copy link
Copy Markdown
Member

runcom commented Jun 10, 2020

@mfojtik release-4.6 aka master is affected by this - can we revert on master as well? (MCO e2e-aws is busted)

@mfojtik
Copy link
Copy Markdown
Contributor

mfojtik commented Jun 10, 2020

@mfojtik release-4.6 aka master is affected by this - can we revert on master as well? (MCO e2e-aws is busted)

no, you have to fix MCO :)

@runcom
Copy link
Copy Markdown
Member

runcom commented Jun 10, 2020

@mfojtik release-4.6 aka master is affected by this - can we revert on master as well? (MCO e2e-aws is busted)

no, you have to fix MCO :)

actually, we're still looking at the failures and it doesn't even seem to be this - sorry for the noise (something related to the fedora registry 🤷‍♂️

@mfojtik
Copy link
Copy Markdown
Contributor

mfojtik commented Jun 10, 2020

@mfojtik release-4.6 aka master is affected by this - can we revert on master as well? (MCO e2e-aws is busted)

no, you have to fix MCO :)

actually, we're still looking at the failures and it doesn't even seem to be this - sorry for the noise (something related to the fedora registry 🤷‍♂️

#25087 this? :)

@runcom
Copy link
Copy Markdown
Member

runcom commented Jun 10, 2020

#25087 this? :)

exactly 😂

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. staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). vendor-update Touching vendor dir or related files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants