Revert: Pass the container name to deployment config log options #10609
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
You had a separate commit for tests? [merge] |
|
[Test]ing while waiting on the merge queue |
|
Evaluated for origin test up to b5fac0b |
|
continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/8393/) |
|
#10002 [merge] Looks like the replication controller and the deployer pod both exist and run but for some reason the watch for the running deployment expires, and we end up reporting that the replication controller wasn't found. |
|
#9355 [merge] |
|
#10635 [merge] |
|
[merge] |
|
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/8473/) (Image: devenv-rhel7_4937) |
|
#10663 [merge] |
|
Evaluated for origin merge up to b5fac0b |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #10598
I will open a follow-up issue to discuss how to fix the original issue without breaking the backward compatibility.