1
80%
master: 80%

Ran 09 Sep 2025 01:01PM UTC

Files 34

Run time 4s

Badge

Embed ▾

Committed 09 Sep 2025 12:53PM UTC coverage: 80.368%. Remained the same

Job # 17583250022.1

Build Type

push

github

Committed by

web-flow

Commit Message

Host.disable: add persistency flag (#6652)

Currently `Host.disable` only disables the host for the current xapi's
runtime - it will be re-enabled on toolstack restarts and host reboots
(if other conditions are met). This greatly complicates manual
maintenance in an HA cluster when reboots are needed, since VMs will
start moving to the host as soon as it's enabled.

To allow for keeping a host persistently disabled across toolstack
restarts and host reboots, add a new localdb flag `host_auto_enable`
(set through the parameter on Host.disable). This coexists with the
internal flag of `host_disabled_until_reboot`, which is only set on host
poweroff internally and cannot be controlled by the user directly.

With `host_auto_enable` set to false, xapi will not re-enable a host on
its own no matter what: toolstack restarts, host reboots, calls to
consider_enabling_host (triggered by PBD plugs etc.) will have no
effect. Only a manual call to `Host.enable` will re-enable the host.

Expose the new parameter in the CLI. Also fix up the comment in
`xapi_host_helpers.mli`.

I've verified the new functionality manually.

Run Details

3496 of 4350 relevant lines covered (80.37%)

0.8 hits per line

xapi-project / xen-api / 17583250022 / 1
80%
master: 80%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job python3.11 - 17583250022.1

xapi-project / xen-api / 17583250022 / 1 80% master: 80%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job python3.11 - 17583250022.1

xapi-project / xen-api / 17583250022 / 1
80%
master: 80%

README BADGES
x