Bug 1183694

This has been well-known for many years, but nobody seems to bother:

Every dracut run started from YaST (e.g. in yast2-bootloader) is flooding the y2log with messages that are marked as category <3>, i.e. y2error.

2021-03-16 20:01:07 <3> install(14829) [Ruby]
  lib/cheetah.rb(log_stream_line):208 Error output: dracut:
  Executing: /usr/bin/dracut --logfile
  /var/log/YaST2/mkinitrd.log --force
  /boot/initrd-5.3.18-50-default 5.3.18-50-default

2021-03-16 20:01:07 <3> install(14829) [Ruby]
  lib/cheetah.rb(log_stream_line):208 Error output: dracut:
  dracut module 'lvmmerge' will not be installed, because command
  'lvm' could not be found!

2021-03-16 20:01:07 <3> install(14829) [Ruby]
  lib/cheetah.rb(log_stream_line):208 Error output: dracut:
  dracut module 'dmraid' will not be installed, because command
  'dmraid' could not be found!

2021-03-16 20:01:07 <3> install(14829) [Ruby]
  lib/cheetah.rb(log_stream_line):208 Error output: dracut:
  dracut module 'dmsquash-live-ntfs' will not be installed,
  because command 'ntfs-3g' could not be found!

This is flooding the y2log to a level where checking for errors becomes a PITA every single time. In general, there should be NO <3> messages in the y2log. Some cannot be avoided, but there is no reason to dump a ton of them for something as normal as an error-less dracut run.

It may very well be that it's normal for dracut to misbehave in that way and to simply dump EVERY message to stderr, even if it's not an error. This would be worth a separate bug.

But in YaST we know very well that dracut misbehaves that way, so it is in our hands to fix that.

Logging dracut output is perfectly okay, but not as errors, but as normal y2milestone ( <1> ) level messages.