valid request, reassigning to initscripts

Yes we can add sleep, but It would be better to fix the issue instead of workaround. Michal is it possible to add some "more synchronous" switch to nut. I assume that similar issue will be in cooperation of nut and systemd.

OK, I reread the bug description and checked the nut sources.
The upsdrvctl does fork-exec-waitpid, so it should exit after shutdown command was sent to the UPS.

Tom, could you tell me what configuration you use?
Run following command and attach it's output here. Thanks

grep -rv '^#' /etc/ups/ | grep -v ':$' | grep -v '.html:'

Huh, that's interesting.  My config is pretty vanilla:

/etc/ups/upsd.users:[admin]
/etc/ups/upsd.users:	password = xxxx
/etc/ups/upsd.users:	actions = SET
/etc/ups/upsd.users:	instcmds = ALL
/etc/ups/upsd.users:[monuser]
/etc/ups/upsd.users:	password = xxxx
/etc/ups/upsd.users:	upsmon master
/etc/ups/upsmon.conf:MONITOR sss1_ups@localhost 1 monuser xxxx master
/etc/ups/upsmon.conf:MINSUPPLIES 1
/etc/ups/upsmon.conf:SHUTDOWNCMD "/sbin/shutdown -h +0"
/etc/ups/upsmon.conf:POLLFREQ 5
/etc/ups/upsmon.conf:POLLFREQALERT 5
/etc/ups/upsmon.conf:HOSTSYNC 15
/etc/ups/upsmon.conf:DEADTIME 15
/etc/ups/upsmon.conf:POWERDOWNFLAG /etc/killpower
/etc/ups/upsmon.conf:RBWARNTIME 43200
/etc/ups/upsmon.conf:NOCOMMWARNTIME 300
/etc/ups/upsmon.conf:FINALDELAY 5
/etc/ups/ups.conf:[sss1_ups]
/etc/ups/ups.conf:	driver = usbhid-ups
/etc/ups/ups.conf:	port = auto
/etc/ups/ups.conf:	offdelay = 30
/etc/ups/ups.conf:	ondelay = 40
/etc/ups/ups.conf:	desc = "APC RS 1000"
/etc/ups/upssched.conf:CMDSCRIPT /usr/bin/upssched-cmd

The machine I'm using is a dual CPU (8 core) x86_64 box.  I don't know much about the USB hardware it has, but it seems entirely clear from my testing that the UPS doesn't recognize the shutdown command if the kernel is allowed to close down with no delay.

I tried to reproduce this, but was not successful.
Anyway, that delay should be there and if it fixes it for you, it's good enough solution.

Lukas, please change the halt section. this way:
  if [ "$SERVER" = "yes" -a -f $POWERDOWNFLAG ]; then
        /sbin/upsdrvctl shutdown
+       sleep 120
+       /sbin/reboot --force
  fi

This is standard way to make it work out of the box with all different UPSes out there. When battery goes low, ups sw  asks system to shutdown, but when AC power comes back during the shutdown process, some UPSes won't turn the power Off - On to start the system again and just keep power on all the time. That's why the sleep is there. In normal circumstances UPS will power off a few seconds after it gets shutdown command, but when it does not, system would be halted with power on forever (until angry administrator comes and kicks the reset button). That why the reboot is there - if there is no power off, reboot the system so it's fully working again.

Yeah, that's what I was alluding to in the initial report --- nut upstream isn't going to think the need for a delay is a bug, because the above coding is exactly what they recommend to be fail-safe in case the UPS fails to honor the shutdown command for some reason.  +1 for doing it like they say to.

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

https://git.fedorahosted.org/cgit/initscripts.git/commit/?h=rhel6-branch&id=bd0f78b5d3b27ee78047ae02144fb8e16f8ee6e8

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1380.html