-
Notifications
You must be signed in to change notification settings - Fork 170
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
reboot nfs_client_vm if not accessible and retry connection #10129
reboot nfs_client_vm if not accessible and retry connection #10129
Conversation
74aba39
to
786b52d
Compare
Verification jobs:
|
Signed-off-by: Daniel Horak <[email protected]>
Signed-off-by: Daniel Horak <[email protected]>
Signed-off-by: Daniel Horak <[email protected]>
Signed-off-by: Daniel Horak <[email protected]>
Signed-off-by: Daniel Horak <[email protected]>
522a301
to
b43c826
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: amr1ta, dahorak, petr-balogh 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 |
…storage#10129) * reboot nfs_client_vm if not accessible and retry connection * do not reboot the VM, if not necessary Signed-off-by: Daniel Horak <[email protected]>
The aim of this PR is automatic reboot of NFS Client VM in case it is not accessible.
To make this work properly, following two new configuration parameters are required:
The logic is, that it firstly try to connect to the NFS Client VM and if it fails, it reboots it, wait some time and try to connect again (with retry this time).