You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Aayush Gupta (Jira)" <ji...@apache.org> on 2026/10/12 11:26:00 UTC

[jira] [Updated] (HDDS-16941) Add unit tests for ozone om bootstrap CLI in TestOzoneManagerStarter

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

Aayush Gupta updated HDDS-16941:
--------------------------------
    Component/s: Ozone Manager
       Language: java
    Description: 
OzoneManagerStarter implements ozone om --bootstrap (and optional --force) for OM HA bootstrap. TestOzoneManagerStarter already unit-tests start and --init with a mocked OMStarterInterface, but --bootstrap is not covered—the mock still has a TODO and does not record calls.

Add tests in the same style as the init tests: extend the mock to track bootstrap(conf, force), then verify --bootstrap, --bootstrap --force, invalid options, and error exit codes. Test-only change; no cluster or production logic changes.

  was:sample

     Issue Type: Improvement  (was: Bug)
       Priority: Minor  (was: Major)
        Summary: Add unit tests for ozone om bootstrap CLI in TestOzoneManagerStarter  (was: sample)

I plan to work on this and open a PR with branch HDDS-16941.

> Add unit tests for ozone om bootstrap CLI in TestOzoneManagerStarter
> --------------------------------------------------------------------
>
>                 Key: HDDS-16941
>                 URL: https://issues.apache.org/jira/browse/HDDS-16941
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: Ozone Manager
>            Reporter: Aayush Gupta
>            Assignee: Aayush Gupta
>            Priority: Minor
>
> OzoneManagerStarter implements ozone om --bootstrap (and optional --force) for OM HA bootstrap. TestOzoneManagerStarter already unit-tests start and --init with a mocked OMStarterInterface, but --bootstrap is not covered—the mock still has a TODO and does not record calls.
> Add tests in the same style as the init tests: extend the mock to track bootstrap(conf, force), then verify --bootstrap, --bootstrap --force, invalid options, and error exit codes. Test-only change; no cluster or production logic changes.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org