[SERVER-35140] Add a startupWarning if running in the previous FCV version relative to your binary version Created: 21/May/18 Updated: 06/Dec/22 Resolved: 09/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Backport Requested: |
v4.0, v3.6, v3.4
|
||||||||||||
| Sprint: | Storage NYC 2018-06-18 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Because startupWarnings are only refreshed on restart, some logic should be added to ensure the startupWarning is only shown when FCV is currently equal to the "downgraded" FCV value. |
| Comments |
| Comment by Eric Milkie [ 09/Dec/19 ] |
|
The logistics for generating this warning at ideal times are quite difficult so we're going to close this. |
| Comment by Cezary Bartosiak [ 22/May/18 ] |
|
Thank you for creating this task. Such a warning would not be obtrusive, because it would not be shown for most of deployments probably, while for these ones for which it would be shown, it would be useful. We upgraded 4 deployments from version 3.4 to 3.6 and the engineer who did this simply forgot about changing the feature compatibility for one of them. We have had no issues until now. It seems it should be easy to find out that this setting is not valid when you try to do something supported in a newer version only, but it looks like it's not so obvious. I ended up creating an issue... |
| Comment by Spencer Brody (Inactive) [ 21/May/18 ] |
|
This was a request from a user on |