mirror of
https://github.com/ceph/ceph-csi.git
synced 2024-11-09 16:00:22 +00:00
ci: fix mdl related failures
This commit address the issue- https://github.com/ceph/ceph-csi/issues/3448. Signed-off-by: riya-singhal31 <rsinghal@redhat.com>
This commit is contained in:
parent
d721ed6c5c
commit
539686329f
@ -77,13 +77,16 @@ following errors:
|
|||||||
|
|
||||||
More details about the error codes can be found [here](https://www.gnu.org/software/libc/manual/html_node/Error-Codes.html)
|
More details about the error codes can be found [here](https://www.gnu.org/software/libc/manual/html_node/Error-Codes.html)
|
||||||
|
|
||||||
For such mounts, The CephCSI nodeplugin returns volume_condition as abnormal for `NodeGetVolumeStats` RPC call.
|
For such mounts, The CephCSI nodeplugin returns volume_condition as
|
||||||
|
abnormal for `NodeGetVolumeStats` RPC call.
|
||||||
|
|
||||||
### kernel client recovery
|
### kernel client recovery
|
||||||
|
|
||||||
Once a mountpoint corruption is detected, Below are the two methods to recover from it.
|
Once a mountpoint corruption is detected,
|
||||||
|
Below are the two methods to recover from it.
|
||||||
|
|
||||||
* Reboot the node where the abnormal volume behavior is observed.
|
* Reboot the node where the abnormal volume behavior is observed.
|
||||||
* Scale down all the applications using the CephFS PVC on the node where abnormal mounts
|
* Scale down all the applications using the CephFS PVC
|
||||||
are present. Once all the applications are deleted, scale up the application
|
on the node where abnormal mounts are present.
|
||||||
|
Once all the applications are deleted, scale up the application
|
||||||
to remount the CephFS PVC to application pods.
|
to remount the CephFS PVC to application pods.
|
||||||
|
@ -140,4 +140,3 @@ To know more about in-tree to CSI migration:
|
|||||||
|
|
||||||
- [design doc](./design/proposals/intree-migrate.md)
|
- [design doc](./design/proposals/intree-migrate.md)
|
||||||
- [Kubernetes 1.17 Feature: Kubernetes In-Tree to CSI Volume Migration Moves to Beta](https://Kubernetes.io/blog/2019/12/09/Kubernetes-1-17-feature-csi-migration-beta/)
|
- [Kubernetes 1.17 Feature: Kubernetes In-Tree to CSI Volume Migration Moves to Beta](https://Kubernetes.io/blog/2019/12/09/Kubernetes-1-17-feature-csi-migration-beta/)
|
||||||
|
|
||||||
|
@ -3,13 +3,8 @@ all
|
|||||||
#Refer below url for more information about the markdown rules.
|
#Refer below url for more information about the markdown rules.
|
||||||
#https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md
|
#https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md
|
||||||
|
|
||||||
rule 'MD013', :ignore_code_blocks => false, :tables => false, :line_length => 80
|
rule 'MD013', :ignore_code_blocks => true, :tables => false, :line_length => 80
|
||||||
|
|
||||||
exclude_rule 'MD033' # In-line HTML: GitHub style markdown adds HTML tags
|
exclude_rule 'MD033' # In-line HTML: GitHub style markdown adds HTML tags
|
||||||
exclude_rule 'MD040' # Fenced code blocks should have a language specified
|
exclude_rule 'MD040' # Fenced code blocks should have a language specified
|
||||||
exclude_rule 'MD041' # First line in file should be a top level header
|
exclude_rule 'MD041' # First line in file should be a top level header
|
||||||
# TODO: Enable the rules after making required changes.
|
|
||||||
exclude_rule 'MD007' # Unordered list indentation
|
|
||||||
exclude_rule 'MD012' # Multiple consecutive blank lines
|
|
||||||
exclude_rule 'MD013' # Line length
|
|
||||||
exclude_rule 'MD047' # File should end with a single newline character
|
|
@ -5,4 +5,3 @@
|
|||||||
`yamlgen` reads deployment configurations from the `api/` package and generates
|
`yamlgen` reads deployment configurations from the `api/` package and generates
|
||||||
YAML files that can be used for deploying without advanced automation like
|
YAML files that can be used for deploying without advanced automation like
|
||||||
Rook. The generated files are located under `deploy/`.
|
Rook. The generated files are located under `deploy/`.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user