-
Notifications
You must be signed in to change notification settings - Fork 40k
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
AWS EBS mkfs and mount failures are difficult to debug #24568
Milestone
Comments
@pmorie - I can look into this, can the user or you supply any other steps or notes on how to reproduce... thanks! |
seems the mkfs for xfs might be squashed - referencing BZ here https://bugzilla.redhat.com/show_bug.cgi?id=1329370 will continue to focus on adding better logging for the identified areas above |
k8s-github-robot
pushed a commit
that referenced
this issue
Jul 22, 2016
Automatic merge from submit-queue add enhanced volume and mount logging for block devices Fixes #24568 Adding better logging and debugging for block device volumes and the shared SafeFormatAndMount (aws, gce, flex, rbd, cinder, etc...)
dims
pushed a commit
to dims/kubernetes
that referenced
this issue
Feb 8, 2018
Automatic merge from submit-queue add enhanced volume and mount logging for block devices Fixes kubernetes#24568 Adding better logging and debugging for block device volumes and the shared SafeFormatAndMount (aws, gce, flex, rbd, cinder, etc...)
openshift-publish-robot
pushed a commit
to openshift/kubernetes
that referenced
this issue
Feb 22, 2020
Bug 1802687: UPSTREAM: 88251: Partially fix incorrect configuration of kubepods.slice unit by kubelet Origin-commit: 1c3b6845d95f84cbb89e6689c3f131683721c8ac
openshift-publish-robot
pushed a commit
to openshift/kubernetes
that referenced
this issue
Feb 28, 2020
Bug 1802687: UPSTREAM: 88251: Partially fix incorrect configuration of kubepods.slice unit by kubelet Origin-commit: 1c3b6845d95f84cbb89e6689c3f131683721c8ac
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I helped a user troubleshoot an issue with EBS volumes not being formatted correctly today and found that there is almost no logging to help determine what happened when mkfs or mount fails. In my particular case, it's not even clear whether
mkfs
was ever run. So, we should:SafeFormatAndMount
code has appropriate loggingThe text was updated successfully, but these errors were encountered: