- 
                Notifications
    
You must be signed in to change notification settings  - Fork 25.6k
 
Fix logsdb rolling upgrade tests again #135499
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
Changes from all commits
50a635a
              a4edaf6
              30a389c
              0c6bb8b
              30f384b
              dc7c9fb
              fa940fd
              File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | 
|---|---|---|
| 
          
            
          
           | 
    @@ -54,6 +54,12 @@ public static Iterable<Object[]> parameters() { | |
| 
     | 
||
| protected abstract ElasticsearchCluster getUpgradeCluster(); | ||
| 
     | 
||
| protected void beforeUpgrade() { | ||
| if (getOldClusterVersion().endsWith("-SNAPSHOT")) { | ||
| assumeTrue("rename of pattern_text mapper", oldClusterHasFeature("mapper.pattern_text_rename")); | ||
| } | ||
| } | ||
| 
     | 
||
| @Before | ||
| public void upgradeNode() throws Exception { | ||
| // extract old cluster features | ||
| 
          
            
          
           | 
    @@ -96,6 +102,8 @@ public void upgradeNode() throws Exception { | |
| // Skip remaining tests if upgrade failed | ||
| assumeFalse("Cluster upgrade failed", upgradeFailed); | ||
| 
     | 
||
| beforeUpgrade(); | ||
| 
         There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I checked a few test failures and it fails with fails with indices/data streams that are managed internally. For example the ilm history or deprecation logging. I think without this change a node upgrade could happen before the  So I think this should ensure that this doesn't happen.  | 
||
| 
     | 
||
| // finally, upgrade node | ||
| if (upgradedNodes.size() < requestedUpgradedNodes) { | ||
| closeClients(); | ||
| 
          
            
          
           | 
    ||
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.
I think a few more tests need to be unmuted now.