-
Notifications
You must be signed in to change notification settings - Fork 185
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
Reset Volume Manager during reload config & ca file rotation #1043
Reset Volume Manager during reload config & ca file rotation #1043
Conversation
Started Vanilla block pre-checkin pipeline... Build Number: 111 |
Started WCP block pre-checkin pipeline... Build Number: 74 |
Change look good to me. Will approve it after the pipeline pass. |
|
Performed the same steps for testing after addressing review comments:
Also performed password rotation:
|
Started vanilla Block pipeline... Build Number: 352 |
Change looks good. Are there any e2e tests that cover password rotation scenario in WCP? If not, it will be good to manually execute it in your setup just for sanity. /approve |
Yes, I ran it manually and captured the logs here: #1043 (comment) |
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.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chethanv28, divyenpatel, gohilankit The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
What this PR does / why we need it:
This PR is resetting VC instance in volume manager during reload config. Currently, the VC instance is reset only when VC hostname is changed. However with secure connection supported in WCP & Vanilla, the existing secure connections before reload config(before certificates regeneration) do not continue to work. Instead, the VC instance has to be invalidated(reset) during reload config.
Before the change:
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Testing done:
After the change:
Steps performed for testing:
Logs: https://gist.github.com/chethanv28/aa96a69c906627e6fb27bb4c6ee14b20
Running e2e pipelines
Special notes for your reviewer:
Release note: