Regarding smart we don't enable smart anywhere in salt states. I assume it's actually a product issue that an installation automatically enables a smart service in an environment where it is not applicable. I know just removed smartmontools on s390zl12 and s390zl13. Don't plan to do more in this direction right now.
That is the output of failing service that I now removed.
# journalctl -u smartd
Oct 11 10:22:25 s390zl13 systemd[1]: Starting Self Monitoring and Reporting Technology (SMART) Daemon...
Oct 11 10:22:25 s390zl13 smartd[129471]: smartd 7.2 2021-09-14 r5237 [s390x-linux-5.14.21-150500.55.28-default] (SUSE RPM)
Oct 11 10:22:25 s390zl13 smartd[129471]: Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
Oct 11 10:22:25 s390zl13 smartd[129471]: Opened configuration file /etc/smartd.conf
Oct 11 10:22:25 s390zl13 smartd[129471]: Drive: DEVICESCAN, implied '-a' Directive on line 32 of file /etc/smartd.conf
Oct 11 10:22:25 s390zl13 smartd[129471]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Oct 11 10:22:25 s390zl13 smartd[129471]: Device: /dev/sda, opened
Oct 11 10:22:25 s390zl13 smartd[129471]: Device: /dev/sda, [IBM 2145 0000], lu id: 0x600507638081855cd80000000000004c, S/N: 00e020615736XX00, 4>
Oct 11 10:22:25 s390zl13 smartd[129471]: Device: /dev/sda, IE (SMART) not enabled, skip device
Oct 11 10:22:25 s390zl13 smartd[129471]: Try 'smartctl -s on /dev/sda' to turn on SMART features
Oct 11 10:22:25 s390zl13 smartd[129471]: Device: /dev/sdb, opened
Oct 11 10:22:25 s390zl13 smartd[129471]: Device: /dev/sdb, [IBM 2145 0000], lu id: 0x600507638081855cd80000000000004c, S/N: 00e020615736XX00, 4>
Oct 11 10:22:25 s390zl13 smartd[129471]: Device: /dev/sdb, IE (SMART) not enabled, skip device
Oct 11 10:22:25 s390zl13 smartd[129471]: Try 'smartctl -s on /dev/sdb' to turn on SMART features
Oct 11 10:22:25 s390zl13 smartd[129471]: Unable to monitor any SMART enabled devices. Try debug (-d) option. Exiting...
Oct 11 10:22:25 s390zl13 systemd[1]: smartd.service: Main process exited, code=exited, status=17/n/a
Oct 11 10:22:25 s390zl13 systemd[1]: smartd.service: Failed with result 'exit-code'.
Oct 11 10:22:25 s390zl13 systemd[1]: Failed to start Self Monitoring and Reporting Technology (SMART) Daemon.
Regarding kdump the problem is that we set the crashkernel parameter which needs a reboot to make kdump work and not start kdump directly. I have researched and found https://stackoverflow.com/questions/23660645/how-to-reboot-in-the-middle-of-a-salt-state , maybe helps.