[ 
https://issues.apache.org/jira/browse/HDDS-15769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siyao Meng updated HDDS-15769:
------------------------------
    Description: 
The non-rolling-upgrade test loads its version-specific callback from 
callbacks/<OZONE_UPGRADE_TO>/callback.sh and falls back to only 
common/callback.sh when none exists (compose/upgrade/testlib.sh). Today 
callbacks/ has 1.3.0, 1.4.0, 2.0.0, and common. Nothing for 2.1.0 or 2.2.0, 
even though layout features landed in that window (OM SNAPSHOT_DEFRAG, HDDS 
STORAGE_SPACE_DISTRIBUTION). So those releases got only the generic 
generate/validate checks, with no pre-finalized/finalized layout-feature 
assertions.
h3. Scope
 - Add callbacks/2.1.0/callback.sh and callbacks/2.2.0/callback.sh following 
the 2.0.0 pattern.
 - with_this_version_pre_finalized: assert pre-finalized state and 
feature-gated behavior for that release's layout features.
 - with_this_version_finalized: assert the feature works after finalization.
 - Run non-rolling-upgrade from 2.1.0 and from 2.2.0 to current; confirm the 
new callbacks run and pass.

 
||Release||Layer||Layout feature||Layout version||Introduced by||
|2.1.0|HDDS/SCM|WITNESSED_CONTAINER_DB_PROTO_VALUE|9|HDDS-13176|
|2.2.0|OM|SNAPSHOT_DEFRAG|9|HDDS-13452|
|2.2.0|HDDS/SCM|STORAGE_SPACE_DISTRIBUTION|10|HDDS-13184|

  was:
The non-rolling-upgrade test loads its version-specific callback from 
callbacks/<OZONE_UPGRADE_TO>/callback.sh and falls back to only 
common/callback.sh when none exists (compose/upgrade/testlib.sh). Today 
callbacks/ has 1.3.0, 1.4.0, 2.0.0, and common. Nothing for 2.1.0 or 2.2.0, 
even though layout features landed in that window (OM SNAPSHOT_DEFRAG, HDDS 
STORAGE_SPACE_DISTRIBUTION). So those releases got only the generic 
generate/validate checks, with no pre-finalized/finalized layout-feature 
assertions.

h3. Scope
- Add callbacks/2.1.0/callback.sh and callbacks/2.2.0/callback.sh following the 
2.0.0 pattern.
- with_this_version_pre_finalized: assert pre-finalized state and feature-gated 
behavior for that release's layout features.
- with_this_version_finalized: assert the feature works after finalization.
- Run non-rolling-upgrade from 2.1.0 and from 2.2.0 to current; confirm the new 
callbacks run and pass.


> Add non-rolling-upgrade callbacks for 2.1.0 and 2.2.0
> -----------------------------------------------------
>
>                 Key: HDDS-15769
>                 URL: https://issues.apache.org/jira/browse/HDDS-15769
>             Project: Apache Ozone
>          Issue Type: Task
>            Reporter: Siyao Meng
>            Priority: Major
>
> The non-rolling-upgrade test loads its version-specific callback from 
> callbacks/<OZONE_UPGRADE_TO>/callback.sh and falls back to only 
> common/callback.sh when none exists (compose/upgrade/testlib.sh). Today 
> callbacks/ has 1.3.0, 1.4.0, 2.0.0, and common. Nothing for 2.1.0 or 2.2.0, 
> even though layout features landed in that window (OM SNAPSHOT_DEFRAG, HDDS 
> STORAGE_SPACE_DISTRIBUTION). So those releases got only the generic 
> generate/validate checks, with no pre-finalized/finalized layout-feature 
> assertions.
> h3. Scope
>  - Add callbacks/2.1.0/callback.sh and callbacks/2.2.0/callback.sh following 
> the 2.0.0 pattern.
>  - with_this_version_pre_finalized: assert pre-finalized state and 
> feature-gated behavior for that release's layout features.
>  - with_this_version_finalized: assert the feature works after finalization.
>  - Run non-rolling-upgrade from 2.1.0 and from 2.2.0 to current; confirm the 
> new callbacks run and pass.
>  
> ||Release||Layer||Layout feature||Layout version||Introduced by||
> |2.1.0|HDDS/SCM|WITNESSED_CONTAINER_DB_PROTO_VALUE|9|HDDS-13176|
> |2.2.0|OM|SNAPSHOT_DEFRAG|9|HDDS-13452|
> |2.2.0|HDDS/SCM|STORAGE_SPACE_DISTRIBUTION|10|HDDS-13184|



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to