Comment 4 for bug 1922282

It looks like your patch adding the 'exec' tag for puppet tripleo fixed the issue, now scenario002 passes. Scenario001 is still failing for a different reason. Puppet fails because a ceph directory doesn't exit.

```
2021-04-06T16:10:33.498854609+00:00 stderr F <13>Apr 6 16:10:33 puppet-user: Notice: /Stage[main]/Apache::Mod::Status/File[status.conf]/ensure: defined content as '{md5}fa95c477a2085c1f7f17ee5f8eccfb90'

2021-04-06T16:10:33.544295196+00:00 stderr F <13>Apr 6 16:10:33 puppet-user: Notice: /Stage[main]/Tripleo::Profile::Base::Gnocchi::Api/Exec[exec-setfacl-openstack-gnocchi]/returns: setfacl: /etc/ceph/ceph.client.openstack.keyring: No such file or directory

2021-04-06T16:10:33.547817997+00:00 stderr F <13>Apr 6 16:10:33 puppet-user: Error: 'setfacl -m u:gnocchi:r-- /etc/ceph/ceph.client.openstack.keyring' returned 1 instead of one of [0]

2021-04-06T16:10:33.548188877+00:00 stderr F <13>Apr 6 16:10:33 puppet-user: Error: /Stage[main]/Tripleo::Profile::Base::Gnocchi::Api/Exec[exec-setfacl-openstack-gnocchi]/returns: change from 'notrun' to ['0'] failed: 'setfacl -m u:gnocchi:r--
```

Is this even necessary for these jobs?