nh os switch fails when automount file systems are changed

[girlpunk]

I have confirmed that this is a bug related to nh

• This is a bug, and not an user error or a support request. I understand that my issue will be closed if it is not a bug in NH.
• I have checked the issues tab and confirmed that my issue has not yet been reported. I understand that my issue will be closed if it is a duplicate.

Description

When trying to make a change to an automount file system, such as reducing the timeout in the following configuration, nh tries to reload the automount unit, which failes.

{
  fileSystems."/media/stuff" = {
    device = "//server/Storage_stuff";
    fsType = "cifs";
    options = [
      "credentials=/etc/nixos/smb-secret"
      "x-systemd.automount"
      "noauto"
      "uid=1000"
      "gid=100"
      "x-systemd.idle-timeout=60,x-systemd.mount-timeout=5s"
    ];
  };
}

> Activating configuration
activating the configuration...
reloading user units for girlpunk...
restarting sysinit-reactivation.target
reloading the following units: media-stuff.automount
Failed to reload media-stuff.automount: Job type reload is not applicable for unit media-stuff.automount.
Error: 
   0: Activation (test) failed
   1: Activating configuration (exit status Exited(4))

Location:
   src/commands.rs:739

I believe this is the a similar issue being discussed in https://discourse.nixos.org/t/x-systemd-automount-makes-activation-fail/54589

Installation Method

Stable Release (nixpkgs, pkgs.nh from nixos-unstable or nixos-yy-mm)

Installation Method (Other)

No response

NH Version

nh 4.3.0

System Information

• system: "x86_64-linux"
• host os: Linux 6.12.76, NixOS, 25.11 (Xantusia), 25.11.20260316.48652e9
• multi-user?: yes
• sandbox: yes
• version: nix-env (Nix) 2.33.3
• channels(root): "nixos-24.11"
• nixpkgs: /nix/store/bxfbn4a6l0ji3pb6mzwsp3nybrpzrvv2-source

[NotAShelf]

This is not NH failing, but switch-to-configuration---which nh executes under the hood.. We have zero say over s-t-c, so there is not much we can do on NH's end. You can use nh os boot to add the "faulty" entry anyway. I intend to add a flag to nh os switch that switches anyway despite the activation "failing", however, that is only vaguely related.

[girlpunk]

Ah, in which case would there be somewhere more appropriate to report this issue?