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

doc : Add info about hypervisor log file locations for troubleshooting (#3688) #4492

Conversation

rohanKanojia
Copy link
Contributor

Description

Fixes: #3688

Relates to: #3688

Add information about hyper-v, vfkit and libvirt virtual machine specific logs to help users find more information while troubleshooting issues.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change
  • Chore (non-breaking change which doesn't affect codebase;
    test, version modification, documentation, etc.)

Proposed changes

Add documentation for checking hypervisor log details while troubleshooting

Testing

N/A

Contribution Checklist

  • I have read the contributing guidelines
  • My code follows the style guidelines of this project
  • I Keep It Small and Simple: The smaller the PR is, the easier it is to review and have it merged
  • I have performed a self-review of my code
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I tested my code on specified platforms
    • Linux
    • Windows
    • MacOS

Related to crc-org#3688

Add information about hyper-v, vfkit and libvirt virtual machine specific logs to
help users find more information while troubleshooting issues.

Signed-off-by: Rohan Kumar <[email protected]>
@openshift-ci openshift-ci bot requested review from gbraad and themr0c December 2, 2024 06:24
Copy link

openshift-ci bot commented Dec 2, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign evidolob for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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

@rohanKanojia rohanKanojia changed the title doc : Add info about hypervisor log file locations for troubleshooting doc : Add info about hypervisor log file locations for troubleshooting (#3688) Dec 2, 2024
Copy link

openshift-ci bot commented Dec 2, 2024

@rohanKanojia: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/integration-crc 3aa222f link true /test integration-crc
ci/prow/e2e-crc 3aa222f link true /test e2e-crc

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

@themr0c
Copy link
Contributor

themr0c commented Dec 2, 2024

The docs just moved to an external repository: https://github.com/crc-org/docs/.

Consider rather proposing the change to this file in the new repository: https://github.com/crc-org/docs/blob/main/modules/ROOT/pages/troubleshooting.adoc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Write console log of CRC instance to a file
2 participants