[
https://issues.apache.org/jira/browse/IGNITE-28982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18105887#comment-18105887
]
Ignite TC Bot commented on IGNITE-28982:
----------------------------------------
{panel:title=Branch: [pull/13491/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13491/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9293872&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9293872
rerunBuildIds=none{color}
> Enable real Rolling Upgrade mode in testcontainers compatibility tests
> ----------------------------------------------------------------------
>
> Key: IGNITE-28982
> URL: https://issues.apache.org/jira/browse/IGNITE-28982
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksandr Chesnokov
> Assignee: Aleksandr Chesnokov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For now compatibility testcontainers use DisabledRollingUpgradeProcessor,
> which has naive implementation
>
> {code:java}
> @Nullable @Override public IgniteNodeValidationResult
> validateNode(ClusterNode node) {
> return null;
> } {code}
> Problem is that real processor has sophisticated logic for validation and it
> is not tested in testcontainers
>
> Let's implement provider that gives real RollingUpgradeProcessor but enabled
> by default. Probably it will be called AutoEnabledRollingUpgradeProcessor
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
