3.0.2

• update package version of saptune to 3.0.2
• avoid excluding LVM slaves when getting valid block devices
  (bsc#1194299)
• fix 'not compliant' state for energy_perf_bias on Power systems and suppress misleading error message regarding missing 'mokutil'
  (bsc#1193435)
• fix wrong behaviour of 'saptune revert all', if the saptune service was stopped between the two commands 'apply' and 'revert all'
• 'saptune service enablestart|disablestop' now always perform both actions and does no longer stop working, if the service is already started|stopped.
  (bsc#1193241)
• restrict the sys section of the AWS note 1656250 to the availability of a nvme block device to support AWS x1e instances too.
  sys section definition of Note 1656250 changed.
  (bsc#1192029)
• abandon the dependency to 'mokutil' by relying on sysfs to detect a secure boot environment.
  Related to bsc#1193435
• support /etc/fstab entries with 4 instead of 6 fields as these are valid entries.
  Change error handling from 'panic' to error log messages.
  (bsc#1193580)
• enhance man page 'saptune.8'.
  Add entry 'configured Note' and some more descriptions of the entries from 'saptune service status'
  (bsc#1192697)
• as the Power systems (hardware architecture 'ppc64le') does not support files in '/sys/class/dmi' (this directory is not available on the 'ppc64le' hardware architecture) some of our section 'tags' will not work.
  Add some additional log messages to identify the cause and add a hint to the man page.
• fix block device settings (e.g. NRREQ) for multipath devices
  (bsc#1193576)
• 'saptune verify' will now report a non existing sysctl or sys parameter as 'not available on the system' (footnote) and this parameter will not affect the compliance state.
  But a warning is displayed to raise attention to may be typos in the parameter name.
• 'saptune status' now reports the 'real' unit state, no mapping of not running (inactive) service to simply 'stopped' any more.
  (bsc#1194334)