TASK .. run update and reboot using.. takes forever with multiple hosts (one after the other)

[crpb]

I had that issues often enough now but today as i currently am updating 18 hosts to the 24.7.2 i'm annoyed again.
Did some digging and the only thing i could find and which would make sense is throttle when i'm not mistaken.

i found a few occurences of that option but not directly in either -facts or -update which are the roles i have in the playbook (and -plugpack as it seems /o). And i don't see how that should trigger here?

Does anybody else has the same wait times or might that just be because i did something wrong?

I don't wanna stop it now and probably have just to try it again when the next update comes but that couldn't take too long 😆

- name: opnsense
  hosts:
    - opnsense
    - opnsensetest
  strategy: free
  vars:
    ansible_become: false
  roles:
    - role: ansible-opnsense-facts
      tags:
        - opnsense
        - facts
    - role: ansible-opnsense-plugpack
      tags:
        - opnsense
        - plugpack
    - role: ansible-opnsense-update
      tags:
        - opnsense
        - update
          #    - role: ansible-opnsense-checkmk
          #      tags:
          #        - opnsense
          #        - checkmk

ansible-playbook -e opn_update_desired_version=24.7.2 -D update.yaml -l   631.38s user 105.27s system 18% cpu 1:07:12.23 total

[zerwes]

Hello @crpb
Sorry to hear you had troubles using the role ...
Can you remember what was the value for reboot_timeout ?
If the next update comes around, you can try the branch throttle-reboot if you like

[zerwes]

@fnateghi ... did you encounter similar issues?

[crpb]

you can try the branch throttle-reboot if you like

thx, will do.

maybe it was also related to a silly problem i had when manualy updating a few other hosts. the download from the official/default mirror was like 20-50kb/s to dtag(multiple cities/towns). hetzner had no problems and nobody on irc seemed to have the same behaviours.

look at the timestamps which i added during the dots of pain.. ^_^

Will also try that one from now on ..

opn_general.system.system:
  - firmware/mirror: 'https://mirror.fra10.de.leaseweb.net/opnsense'

[zerwes]

merged the throttle stuff into main
maybe gathering more information during the next update using a log file and increasing verbosity (ansible-playbook -vv) can help to reproduce this