Comment 54 for bug 2009141

The logs are either now a bit different or at least better readable:
"
 2023-09-18 09:22:35,931 DEBUG subiquitycore.utils:132 arun_command ['chzdev', '--enable', '0.0.162f'] exited with code 0
 2023-09-18 09:22:35,931 DEBUG subiquitycore.utils:76 run_command called: ['lszdev', '--quiet', '--pairs', '--columns', 'id,type,on,exists,pers,auto,failed,names']
 2023-09-18 09:22:36,143 DEBUG subiquitycore.utils:95 run_command ['lszdev', '--quiet', '--pairs', '--columns', 'id,type,on,exists,pers,auto,failed,names'] exited with code 0
 2023-09-18 09:22:36,201 DEBUG root:30 finish: subiquity/Zdev/chzdev_POST: SUCCESS: 200 [{"id": "0.0.1600", "type": "dasd-eckd", "on": false, "exists": true, "pers":...
 2023-09-18 09:22:36,201 INFO aiohttp.access:206 [18/Sep/2023:09:22:32 +0000] "POST /zdev/chzdev?action=%22enable%22&zdev=%7B%22id%22:+%220.0.162f%22,+%22type%22:+%22dasd-eckd%22,+%22on%22:+false,+%22exists%22:+true,+%22pers%22:+false,+%22auto%22:+false,+%22failed%22:+false,+%22names%22:+%22%22%7D HTTP/1.1" 200 65093 "-" "Python/3.10 aiohttp/3.8.1"
 2023-09-18 09:22:36,202 DEBUG subiquitycore.utils:76 run_command called: ['udevadm', 'settle', '-t', '0']
 2023-09-18 09:22:36,221 DEBUG subiquitycore.utils:95 run_command ['udevadm', 'settle', '-t', '0'] exited with code 0
 2023-09-18 09:22:36,222 ERROR subiquity.server.server:415 top level error
 Traceback (most recent call last):
   File "/snap/subiquity/5107/usr/lib/python3.10/asyncio/events.py", line 80, in _run
     self._context.run(self._callback, *self._args)
   File "/snap/subiquity/5107/lib/python3.10/site-packages/subiquity/server/controllers/filesystem.py", line 1496, in _udev_event
     action, dev = self._monitor.receive_device()
   File "/snap/subiquity/5107/usr/lib/python3/dist-packages/pyudev/monitor.py", line 393, in receive_device
     device = self.poll()
   File "/snap/subiquity/5107/usr/lib/python3/dist-packages/pyudev/monitor.py", line 355, in poll
     return self._receive_device()
   File "/snap/subiquity/5107/usr/lib/python3/dist-packages/pyudev/monitor.py", line 294, in _receive_device
     device_p = self._libudev.udev_monitor_receive_device(self)
   File "/snap/subiquity/5107/usr/lib/python3/dist-packages/pyudev/_ctypeslib/_errorcheckers.py", line 103, in check_errno_on_null_pointer_return
     raise exception_from_errno(errnum)
 OSError: [Errno 105] No buffer space available
 2023-09-18 09:22:36,224 DEBUG subiquity.common.errorreport:394 generating crash report
 2023-09-18 09:22:36,225 INFO subiquity.common.errorreport:415 saving crash report 'unknown error crashed with OSError' to /var/crash/1695028956.225001574.unknown.crash
"

Two things I'm wondering about:
Yes I manually enabled "0.0.162f",
a few lines later I see: "subiquity/Zdev/chzdev_POST: SUCCESS: 200 [{"id": "0.0.1600", "type": "dasd-eckd" - but I haven't touched "0.0.1600" at all.
And the msg "[Errno 105] No buffer space available".