Skip to content

Bug 1820633: Cherry-pick release 4.4 Support for specific http proxy for the service#89

Merged
openshift-merge-robot merged 10 commits intoopenshift:release-4.4from
martinkunc:release-4.4
Apr 17, 2020
Merged

Bug 1820633: Cherry-pick release 4.4 Support for specific http proxy for the service#89
openshift-merge-robot merged 10 commits intoopenshift:release-4.4from
martinkunc:release-4.4

Conversation

@martinkunc
Copy link
Copy Markdown
Contributor

@martinkunc martinkunc commented Apr 3, 2020

Cherry-pick support for specific http proxy
Obviously I wasn't successful with squashing the commits here, so I had to cherry pick them manually this time.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@martinkunc: 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:

Release 4.4

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

@martinkunc: 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:

Release 4.4

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.

@alexandrevicenzi
Copy link
Copy Markdown
Contributor

It seems to me that there's more code than it supposed to be, is this correct?

If you try to apply the patch directly does it work?

Also, the title of this PR is misleading, we are backporting proxy to 4.4.

@martinkunc
Copy link
Copy Markdown
Contributor Author

/retest

@martinkunc martinkunc changed the title Release 4.4 Bug 1820595: Support for specific http proxy for the service Apr 3, 2020
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@martinkunc: This pull request references Bugzilla bug 1820595, which is invalid:

  • expected the bug to target the "4.4.0" release, but it targets "---" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is MODIFIED instead
  • expected Bugzilla bug 1820595 to depend on a bug targeting the "4.5.0" release and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), 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 1820595: Support for specific http proxy for the service

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 Apr 3, 2020
@martinkunc
Copy link
Copy Markdown
Contributor Author

/bugzilla refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@martinkunc: This pull request references Bugzilla bug 1820595, which is invalid:

  • expected the bug to target the "4.4.0" release, but it targets "---" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is MODIFIED instead
  • expected Bugzilla bug 1820595 to depend on a bug targeting the "4.5.0" release and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), 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.

@martinkunc
Copy link
Copy Markdown
Contributor Author

/bugzilla refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@martinkunc: This pull request references Bugzilla bug 1820595, which is invalid:

  • expected the bug to target the "4.4.0" release, but it targets "4.3.z" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is MODIFIED instead
  • expected Bugzilla bug 1820595 to depend on a bug targeting the "4.5.0" release and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), 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.

@martinkunc martinkunc changed the title Bug 1820595: Support for specific http proxy for the service Bug 1820595: Cherry-pick release 4.4 Support for specific http proxy for the service Apr 3, 2020
@martinkunc martinkunc changed the title Bug 1820595: Cherry-pick release 4.4 Support for specific http proxy for the service Bug 1820633: Cherry-pick release 4.4 Support for specific http proxy for the service Apr 3, 2020
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@martinkunc: This pull request references Bugzilla bug 1820633, which is invalid:

  • expected dependent Bugzilla bug 1820595 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is MODIFIED instead
  • expected dependent Bugzilla bug 1820595 to target the "4.5.0" release, but it targets "4.3.z" 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.

Details

In response to this:

Bug 1820633: Cherry-pick release 4.4 Support for specific http proxy for the service

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.

@martinkunc
Copy link
Copy Markdown
Contributor Author

/retest

@martinkunc
Copy link
Copy Markdown
Contributor Author

/bugzilla refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@martinkunc: This pull request references Bugzilla bug 1820633, which is invalid:

  • expected dependent Bugzilla bug 1820595 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), 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.

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.

@martinkunc
Copy link
Copy Markdown
Contributor Author

/bugzilla refresh

@openshift-ci-robot openshift-ci-robot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Apr 6, 2020
@iNecas
Copy link
Copy Markdown
Contributor

iNecas commented Apr 6, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Apr 6, 2020
@martinkunc
Copy link
Copy Markdown
Contributor Author

@jwforres Could I ask for approving the cherry-pick with cherry-pick-approved label please ?

@derekwaynecarr derekwaynecarr added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Apr 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.

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.

@eparis
Copy link
Copy Markdown
Member

eparis commented Apr 9, 2020

/lgtm cancel
why are the insights test failing? seems that needs to be addressed.

@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Apr 9, 2020
@eparis
Copy link
Copy Markdown
Member

eparis commented Apr 11, 2020

/test ci/prow/insights-operator-e2e-tests

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

  • /test e2e-aws
  • /test e2e-aws-upgrade
  • /test images
  • /test insights-operator-e2e-tests
  • /test unit

Use /test all to run all jobs.

Details

In response to this:

/test ci/prow/insights-operator-e2e-tests

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.

@eparis
Copy link
Copy Markdown
Member

eparis commented Apr 11, 2020

/test insights-operator-e2e-tests

@eparis
Copy link
Copy Markdown
Member

eparis commented Apr 13, 2020

So far I see base_test.go failing 4 times in the history and passing 3 times. how are things in master? Is your flake rate 50% there?

/test insights-operator-e2e-tests

@martinkunc
Copy link
Copy Markdown
Contributor Author

@eparis We have the same situation in master with this test. I already have an internal case to investigate it.

@alexandrevicenzi
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 16, 2020
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alexandrevicenzi, iNecas, martinkunc

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:
  • OWNERS [alexandrevicenzi,iNecas]

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

@alexandrevicenzi
Copy link
Copy Markdown
Contributor

/test insights-operator-e2e-tests

@nee1esh
Copy link
Copy Markdown

nee1esh commented Apr 16, 2020

/retest

1 similar comment
@martinkunc
Copy link
Copy Markdown
Contributor Author

/retest

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

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

@openshift-merge-robot openshift-merge-robot merged commit 9d96623 into openshift:release-4.4 Apr 17, 2020
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@martinkunc: All pull requests linked via external trackers have merged: openshift/insights-operator#89. Bugzilla bug 1820633 has been moved to the MODIFIED state.

Details

In response to this:

Bug 1820633: Cherry-pick release 4.4 Support for specific http proxy for the service

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.

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

9 participants