Converts between experimental and non-experimental flags in downgrade & upgrade robustness & e2e test#20001
Conversation
|
Think this has same issue as #19506 (comment) |
ef2ab60 to
fb314b7
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted filessee 155 files with indirect coverage changes @@ Coverage Diff @@
## main #20001 +/- ##
==========================================
- Coverage 68.82% 61.08% -7.74%
==========================================
Files 424 410 -14
Lines 35762 34603 -1159
==========================================
- Hits 24612 21137 -3475
- Misses 9728 11879 +2151
- Partials 1422 1587 +165 Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
f355334 to
fa6dbc9
Compare
d0cd0ef to
0d2e938
Compare
4441c12 to
cae3452
Compare
tests/framework/e2e/downgrade.go
Outdated
|
|
||
| // When we downgrade or upgrade a member, we need to re-generate the flags, to convert some non-experimental | ||
| // flags to experimental flags, or vice verse. | ||
| if err := clus.UpdateProcOptions(memberID, t); err != nil { |
There was a problem hiding this comment.
This will not be called in robustness tests
There was a problem hiding this comment.
My understanding is both robustness test and e2e test reuse the same DowngradeUpgradeMembersByID to perform downgrade & upgrade.
If it doesn't, then robustness test will fail.
But the robustness test on older version is periodically test, can't be verified immediately. So I raised kubernetes/test-infra#34834
4dd1c71 to
7f7a746
Compare
|
FYI: I'm waiting for CI to pass before reviewing it again. |
I will rebase this PR once #20016 gets merged. Also we can see e2e workflow result in this PR before being rebased. |
7f7a746 to
a870bb7
Compare
|
ping @serathius It should be working now. |
tests/framework/e2e/config.go
Outdated
| return fmt.Sprintf("--%s=%s", name, value) | ||
| } | ||
|
|
||
| // version < 3.6 and name is experimental |
There was a problem hiding this comment.
Nit, those comments are not informative. Recommend to either remove them, or rewrite to answer "why?" instead of "what?". For example "In v3.7 etcd removed experimental prefix from flags (link to issue)"
a870bb7 to
dc92de1
Compare
dc92de1 to
e098bd4
Compare
e098bd4 to
f7d7ef2
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahrtr, serathius The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Since the kubernetes/test-infra#34834 hasn't been merged, so the robustness test against previous versions can't be verified in this PR. If there is still any issues after merging this PR, we can fix in followup PR(s). |
Have you run the test locally? |
Signed-off-by: Benjamin Wang <benjamin.ahrtr@gmail.com>
f7d7ef2 to
8859f41
Compare
3.6 works. 3.5/3.4 have issues, but unrelated to flags. test-robustness-release-3.5: So we should be good to merge this PR, and investigate the failure separately. |
SG |
|
/retest |
followup to #19959 (comment)
cc @fuweid @serathius @ivanvc @jmhbnz
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.