# Unmaintained collection: frr.frr **URL:** \ **Category:** Project Discussions\ **Tags:** resolved, community-wg, collections\ **Created:** [June 7, 2024, 3:01pm UTC](https://forum.ansible.com/t/unmaintained-collection-frr-frr/6243 "2024-06-07T15:01:41Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 7, 2024, 3:01pm UTC](https://forum.ansible.com/t/unmaintained-collection-frr-frr/6243/1 "2024-06-07T15:01:41Z")
There has been a deprecation announcement in [The Bullhorn #123](http://forum.ansible.com/t/2568) for the [frr.frr](https://github.com/ansible-collections/frr.frr) collection. It says there won’t be any more major releases, but I don’t see any minor or even bugfix release either for quite some time. There is no information about deprecation neither in the repo nor on [galaxy](https://galaxy.ansible.com/ui/repo/published/frr/frr/). However, I suggest to remove it ASAP. That is in the Ansible Community Package 11. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 8, 2024, 12:36pm UTC](https://forum.ansible.com/t/unmaintained-collection-frr-frr/6243/2 "2024-06-08T12:36:54Z")
I have created a [Removal from Ansible Community Package](https://github.com/ansible-collections/frr.frr/issues/68) issue in the repository. It’s loosely based on the text that I use for the [Identifying and removing an unmaintained collection process](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_package_removal.html#id6). But since they did announce the removal in The Bullhorn but nowhere else, this doesn’t really fit and I’ve improvised a bit. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 9, 2024, 12:24pm UTC](https://forum.ansible.com/t/unmaintained-collection-frr-frr/6243/3 "2024-06-09T12:24:45Z")
There are also [failing sanity tests](https://github.com/ansible-collections/frr.frr/issues/66). ---
**Author:** ![nilashishc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nilashishc/32/3961_2.png) [@nilashishc](https://forum.ansible.com/u/nilashishc)\ **Post date:** [June 12, 2024, 2:30pm UTC](https://forum.ansible.com/t/unmaintained-collection-frr-frr/6243/4 "2024-06-12T14:30:51Z")
Hello [@mariolenz](https://github.com/mariolenz)! I’m from the Ansible Network team, that maintains the frr.frr collection. This collection was deprecated in December, 2023 and will reach end-of-life on December, 2025. During this period, we will only be doing patch releases for this collection if a critical bug or security vulnerability has been reported. We will continue to run ansible-test in CI for ansible-core\<=2.17, \>=2.15 and as such compatibility with ansible-core versions \>2.17 will not be guaranteed. I have opened a PR that fixes the sanity failure with \>=stable-2.16 and also an update to the README mentioning all the above. (Apologies to the Community for not doing that along with the Bullhorn announcement.) Please let me know if the above points would qualify this collection to continue being included in the Ansible Community Package. Thank you! ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 12, 2024, 3:29pm UTC](https://forum.ansible.com/t/unmaintained-collection-frr-frr/6243/5 "2024-06-12T15:29:37Z")
> [@nilashishc](#): > > This collection was deprecated in December, 2023 and will reach end-of-life on December, 2025. During this period, we will only be doing patch releases for this collection if a critical bug or security vulnerability has been reported. Thanks @nilashishc, this is a very important and valuable information! This sounds like we shouldn’t remove the collection ASAP / from Ansible 11. But also that we might want to announce the deprecation / removal from a future version of the Ansible Community Package. If we keep releasing new Ansible versions as we did in the past, I think 13 would have an ETA of around November 2025 and would be a good time. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [June 12, 2024, 5:05pm UTC](https://forum.ansible.com/t/unmaintained-collection-frr-frr/6243/6 "2024-06-12T17:05:51Z")
Ansible 11 is based on ansible-core 2.18, which is no longer officially supported by frr.frr then. Because of that I’m a bit hesitant to keep it included until Ansible 13. We definitely have to discuss this though 🙂 ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 12, 2024, 5:55pm UTC](https://forum.ansible.com/t/unmaintained-collection-frr-frr/6243/7 "2024-06-12T17:55:06Z")
I agree, [Compatibility with ansible-core\>2.17 is not guaranteed](https://github.com/ansible-collections/frr.frr/blob/d8f8475ee943531f17d7a5b32909b11327c2de86/README.md) looks problematic. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 13, 2024, 3:27pm UTC](https://forum.ansible.com/t/unmaintained-collection-frr-frr/6243/8 "2024-06-13T15:27:43Z")
Moving the discussion to [Several collections have been deprecated by the Ansible Network team](http://forum.ansible.com/t/6360). ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 19, 2024, 7:44pm UTC](https://forum.ansible.com/t/unmaintained-collection-frr-frr/6243/9 "2024-06-19T19:44:49Z")
Since this collection hasn’t been only deprecated, but it’s clear now that ansible-core 2.18 won’t be supported (see [here](https://github.com/ansible-collections/frr.frr/commit/90fa27060a0195a211911398d9959049985bbbba) and [here](https://github.com/ansible-collections/frr.frr/commit/69fd7210ae226f66ad8556b28203a357e759e526)) we _have_ to remove it from the Ansible Community Package 11 because it will be based on this. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 20, 2024, 6:27pm UTC](https://forum.ansible.com/t/unmaintained-collection-frr-frr/6243/10 "2024-06-20T18:27:25Z")
[Remove frr.frr and openvswitch.openvswitch](https://github.com/ansible-community/ansible-build-data/pull/437) FYI We’ve talked about this in the community meeting and decided we don’t need a vote on this because of [Removing a collection that has been explicitly deprecated or abandoned by its (former) maintainers](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_package_removal.html#removing-a-collection-that-has-been-explicitly-deprecated-or-abandoned-by-its-former-maintainers). ---
**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\ **Post date:** [June 24, 2024, 7:33am UTC](https://forum.ansible.com/t/unmaintained-collection-frr-frr/6243/11 "2024-06-24T07:33:52Z")
SGTM. Should our exclusion procedure be update to state it explicitly? Anyway, @mariolenz @nilashishc @felixfontein thanks for working on this!