BSD Commit Log Search

Fix

NAS-139515 / 26.0.0-BETA.1 / fix sysds migration instability (#18113)

Fix

Fix test

fix sysds migration instability

rework migration

rm bulk tests

handle when services stop before we check

Lightweight plugin parts

Lightweight plugin parts

rm bulk tests

fix system dataset migration instability

NAS-139512 / 26.0.0-BETA.1 / Fix import (#18111)

pwenc_data no longer exists, so don't try to import.

Fix import

split SMB path field

Fix

Fix

NAS-139506 / 26.0.0-BETA.1 / fix pool export when apps ds is gone (#18110)

This code is indecipherable and maddening. I can't export a pool because
the ix-apps dataset was destroyed (by me during bug reproduction) and
it's raising ENOENT. Investigating shows that this regressed when the
new zfs.resource API was put in which broke the `except CallError` catch
that should have been ignoring this and allowing it go through.

I've fixed the regression but this code makes me want to mow yards for a
living.

fix pool export when apps ds is gone

Include latest app version in app.query response

Fix docstring

Selectively raise app alerts

Fix failures in unit test

NAS-139505 / 26.0.0-BETA.1 / disable unused netdata plugins (#18108)

We're trying, YET AGAIN, to fix our system dataset migration nonsense
and I've noticed that netdata is the culprit for this particular
failure. It's not immediately apparent why and we might actually be on
the cusp of a hard-to-reproduce zfs bug but this PR disables a bunch of
unused netdata plugins that are just giving us grief.

disable unused netdata plugins

Keep persistent cache across upgrades

Fix test

disable sockets

NAS-139409 / 26.0.0-BETA.1 / Fix reboot reasons for HA (by Qubad786) (#18090)

## Problem

There were different problems identified with reboot reasons management
with HA:

1. We were setting reboot reason after rebooting remote node in case an
exception happened which meant that the remote would have to be rebooted
again because we would have stored it's boot_id as none at that point.
2. For any reboot reason, we always set disabled reasons as FIPS which
is wrong and we should show actual reason HA is being shown as disabled
3. Active node's reboot reason was added after remote had rebooted which
is not nice
4. We did not set appropriate reboot reason for FIPS/STIG if both were
toggled and only FIPS got added

## Solution


    [14 lines not shown]

Address review