issue2740: updates to debugging doc for SELinux intermittent label issue#3702
Merged
openshift-bot merged 1 commit intoopenshift:masterfrom Jul 14, 2015
Merged
issue2740: updates to debugging doc for SELinux intermittent label issue#3702openshift-bot merged 1 commit intoopenshift:masterfrom
openshift-bot merged 1 commit intoopenshift:masterfrom
Conversation
Contributor
|
lgtm. [merge] |
Contributor
|
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/2729/) (Image: devenv-fedora_1994) |
Contributor
|
Evaluated for origin up to 0418122 |
openshift-bot
pushed a commit
that referenced
this pull request
Jul 14, 2015
Merged by openshift-bot
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixed #2740
@bparees @ncdc here is the debug guide / doc update for the SELinux intermittent issue. I ended up citing the high level description Andy provided, but not going into the initial list of 6 user error paths. That felt like a slippery slope.