diff --git a/hotsos/defs/scenarios/openstack/nova/bugs/lp2012284.yaml b/hotsos/defs/scenarios/openstack/nova/bugs/lp2012284.yaml index ccd585b4a..71b58dfe8 100644 --- a/hotsos/defs/scenarios/openstack/nova/bugs/lp2012284.yaml +++ b/hotsos/defs/scenarios/openstack/nova/bugs/lp2012284.yaml @@ -2,7 +2,7 @@ checks: has_2012284: input: path: 'var/log/nova/nova-compute.log' - expr: ".+Failure prepping block device: gi.repository.GLib.GError: g-io-error-quark: Error opening directory '/usr/share/osinfo': Permission denied" + expr: '([\d-]+) ([\d:]+).\d{3} .+Failure prepping block device: gi.repository.GLib.GError: g-io-error-quark: Error opening directory ./usr/share/osinfo.: Permission denied' hint: 'osinfo' conclusions: lp2012284: @@ -11,8 +11,8 @@ conclusions: type: LaunchpadBug bug-id: 2012284 message: >- - known nova compute issue caused when package gir1.2-libosinfo-1.0 is installed - and apparmor is set to enforced. To fix the issue, the offending package needs to + Known nova compute issue caused when package gir1.2-libosinfo-1.0 is installed + and apparmor is set to enforce. To fix the issue, the offending package needs to be removed, or apparmor set to complain, or the rules would need to be added to the apparmor profile (but this is not supported and can be overridden). Please refer to the Launchpad #2012284 bug page more information. diff --git a/hotsos/defs/tests/scenarios/openstack/nova/bugs/lp2012284.yaml b/hotsos/defs/tests/scenarios/openstack/nova/bugs/lp2012284.yaml index 4fe8b2d38..38bf0c4f8 100644 --- a/hotsos/defs/tests/scenarios/openstack/nova/bugs/lp2012284.yaml +++ b/hotsos/defs/tests/scenarios/openstack/nova/bugs/lp2012284.yaml @@ -6,8 +6,8 @@ data-root: - sos_commands/date/date raised-bugs: https://bugs.launchpad.net/bugs/2012284: >- - known nova compute issue caused when package gir1.2-libosinfo-1.0 is installed - and apparmor is set to enforced. To fix the issue, the offending package needs to + Known nova compute issue caused when package gir1.2-libosinfo-1.0 is installed + and apparmor is set to enforce. To fix the issue, the offending package needs to be removed, or apparmor set to complain, or the rules would need to be added to the apparmor profile (but this is not supported and can be overridden). Please refer to the Launchpad #2012284 bug page more information.