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 1804763: add imagestream for oauthproxy image #228

Merged
merged 1 commit into from Feb 19, 2020

Conversation

bparees
Copy link
Contributor

@bparees bparees commented Feb 18, 2020

No description provided.

@openshift-ci-robot openshift-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Feb 18, 2020
@bparees
Copy link
Contributor Author

bparees commented Feb 18, 2020

@gabemontero do we have any sort of test coverage for these imagestreams?

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 18, 2020
@bparees
Copy link
Contributor Author

bparees commented Feb 18, 2020

/hold
need @openshift/sig-auth acknowledgement since this is their image.

@openshift-ci-robot openshift-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Feb 18, 2020
@mfojtik
Copy link
Member

mfojtik commented Feb 18, 2020

/cc @sttts

I don't see problem shipping this via image stream as people can use it today anyway (and they do). ImageStream only makes it available for disconnected users.

@mfojtik
Copy link
Member

mfojtik commented Feb 18, 2020

/lgtm

Will wait for @sttts to unhold.

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

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@gabemontero
Copy link
Contributor

gabemontero commented Feb 18, 2020

@gabemontero do we have any sort of test coverage for these imagestreams?

Not as part of image-eco @bparees

I've tangentially seen some of them used in CI in other contexts of course (must-gather for artifact collection ... don't recall if that uses cli or not).

@bparees
Copy link
Contributor Author

bparees commented Feb 18, 2020

/test e2e-aws-image-ecosystem

@bparees
Copy link
Contributor Author

bparees commented Feb 18, 2020

/retest

2 similar comments
@bparees
Copy link
Contributor Author

bparees commented Feb 18, 2020

/retest

@bparees
Copy link
Contributor Author

bparees commented Feb 18, 2020

/retest

@bparees bparees changed the title add imagestream for oauthproxy image Bug 1804763: add imagestream for oauthproxy image Feb 19, 2020
@bparees
Copy link
Contributor Author

bparees commented Feb 19, 2020

/bugzilla refresh

@bparees
Copy link
Contributor Author

bparees commented Feb 19, 2020

/cherrypick release-4.4

@openshift-cherrypick-robot

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

In response to this:

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

1 similar comment
@openshift-cherrypick-robot

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

In response to this:

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

@sttts
Copy link
Contributor

sttts commented Feb 19, 2020

/retest

As discussed on Slack with @bparees @jwforres @smarterclayton this only makes the image stream available to components outside of OpenShift core. This does not imply any support or any future compatibility. Flags will change.

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 19, 2020
@openshift-bot
Copy link
Contributor

/retest

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

2 similar comments
@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
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 0b39607 into openshift:master Feb 19, 2020
@openshift-ci-robot
Copy link
Contributor

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

In response to this:

Bug 1804763: add imagestream for oauthproxy image

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.

1 similar comment
@openshift-ci-robot
Copy link
Contributor

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

In response to this:

Bug 1804763: add imagestream for oauthproxy image

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

@bparees: failed to push cherry-picked changes in GitHub: pushing failed, output: "To https://github.com/openshift-cherrypick-robot/cluster-samples-operator\n ! [remote rejected] cherry-pick-228-to-release-4.4 -> cherry-pick-228-to-release-4.4 (cannot lock ref 'refs/heads/cherry-pick-228-to-release-4.4': reference already exists)\nerror: failed to push some refs to 'https://openshift-cherrypick-robot:CENSORED@github.com/openshift-cherrypick-robot/cluster-samples-operator'\n", error: exit status 1

In response to this:

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

@bparees: new pull request created: #229

In response to this:

/cherrypick 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
Contributor

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

Test name Commit Details Rerun command
ci/prow/e2e-aws-upgrade f9f1810 link /test e2e-aws-upgrade
ci/prow/e2e-aws-image-ecosystem f9f1810 link /test e2e-aws-image-ecosystem
ci/prow/e2e-aws f9f1810 link /test e2e-aws
ci/prow/images f9f1810 link /test images
ci/prow/e2e-aws-operator f9f1810 link /test e2e-aws-operator

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your 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. I understand the commands that are listed here.

@bparees
Copy link
Contributor Author

bparees commented Feb 20, 2020

/cherrypick release-4.2

@openshift-cherrypick-robot

@bparees: failed to push cherry-picked changes in GitHub: pushing failed, output: "To https://github.com/openshift-cherrypick-robot/cluster-samples-operator\n ! [remote rejected] cherry-pick-228-to-release-4.2 -> cherry-pick-228-to-release-4.2 (cannot lock ref 'refs/heads/cherry-pick-228-to-release-4.2': reference already exists)\nerror: failed to push some refs to 'https://openshift-cherrypick-robot:CENSORED@github.com/openshift-cherrypick-robot/cluster-samples-operator'\n", error: exit status 1

In response to this:

/cherrypick release-4.2

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

@bparees: new pull request created: #231

In response to this:

/cherrypick release-4.2

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. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants