Recent changes about default labeling

Archives Ansible Developer
1

Hi,

I’m one of oVirt modules maintainers and and we were using “ovirt” label to filter issues related to oVirt Ansible modules [1].

Today I’ve found out that “ovirt” label doesn’t exist anymore and instead all issues around various virtualization related modules are labeled with “virt” label.But this is a huge issue for both oVirt developers and QEs, because we don’t have any way how to easily filter issues related to oVirt modules.

So can this change be reverted and can all issues related to ovirt modules [1] be again labeled with “ovirt” label?

Thanks a lot

Martin

[1] https://github.com/ansible/ansible/tree/devel/lib/ansible/modules/cloud/ovirt

2

Hi,
Looks like this got changed to https://github.com/ansible/ansible/labels/virt which should apply to everything once the bot has caught up.

3

Hi,
Looks like this got changed to https://github.com/ansible/ansible/labels/virt which should apply to everything once the bot has caught up.

Yes, but it also labels modules from different projects like proxmox or libvirt, so there is no easy way how to easily filter open issues for oVirt modules only.
So is there a way how to automatically label oVirt modules with “ovirt” label as before?

4

Hi,
Looks like this got changed to https://github.com/ansible/ansible/labels/virt which should apply to everything once the bot has caught up.

Yes, but it also labels modules from different projects like proxmox or libvirt, so there is no easy way how to easily filter open issues for oVirt modules only.
So is there a way how to automatically label oVirt modules with “ovirt” label as before?

Ahh, I’ve found out where labeling is configured and created https://github.com/ansible/ansible/pull/52510 to restore ovirt label again