The openstack-operations role [1] does not live in tripleo-ansible [2]. When I originally opened the bug I thought this was limited only to tripleo-ansible but I was mistaken.
Another way to describe this bug is:
While running linters for tripleo-ansible there's a warning about the openatack-operations name
I suspect CI doesn't hit this because it's dedicated to that repos only while in my local environment where I run it on an undercloud both ansible repos are installed so tripleo-ansible's linter is checkikng more than it should.
The openstack- operations role [1] does not live in tripleo-ansible [2]. When I originally opened the bug I thought this was limited only to tripleo-ansible but I was mistaken.
Another way to describe this bug is:
While running linters for tripleo-ansible there's a warning about the openatack- operations name
I suspect CI doesn't hit this because it's dedicated to that repos only while in my local environment where I run it on an undercloud both ansible repos are installed so tripleo-ansible's linter is checkikng more than it should.
[1] https:/ /github. com/openstack/ ansible- role-openstack- operations /github. com/openstack/ tripleo- ansible/ tree/master/ tripleo_ ansible/ roles
[2] https:/