# Broken CI in ansible-community/molecule-plugins github project

**URL:** <https://forum.ansible.com/t/broken-ci-in-ansible-community-molecule-plugins-github-project/8611>\
**Category:** Get Help\
**Tags:** molecule6, molecule\
**Created:** [September 19, 2024, 2:09am UTC](https://forum.ansible.com/t/broken-ci-in-ansible-community-molecule-plugins-github-project/8611 "2024-09-19T02:09:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cnfrancis](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/cnfrancis/32/2615_2.png) [@cnfrancis](https://forum.ansible.com/u/cnfrancis)\
**Post date:** [September 19, 2024, 2:09am UTC](https://forum.ansible.com/t/broken-ci-in-ansible-community-molecule-plugins-github-project/8611/1 "2024-09-19T02:09:53Z")

</div>

Hello!  
Can someone from the community with write access review/approve the PR below please (`ansible-community/molecule-plugins`)?

It aims at fixing the broken CI which has been broken for the past 1.5 month. It’s preventing PRs from being merged that provide bug fixes and introduce important new features aiming at making the Molecule framework more robust and feature rich!

> <https://github.com/ansible-community/molecule-plugins/pull/260>
>
> \- Upgrade containers and boxes to use newer versions
> \- Remove create.yml/destro…y.yml templates copied by molecule with molecule init for unlucky plugins
> \- Rename vagrant tests to avoid "import vagrant" in the test importing the test module instead of importing the vagrant module.
> \- Move the vagrant box\_url testing to its own test to avoid failures in multi-node where it would be hard to know if the issue is with the test or with the box\_url test.

@Denney-tech perhaps you can involve someone who can get the ball moving?

---

<div class="post-metadata">

**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\
**Post date:** [September 19, 2024, 1:08pm UTC](https://forum.ansible.com/t/broken-ci-in-ansible-community-molecule-plugins-github-project/8611/2 "2024-09-19T13:08:51Z")

</div>

Considering it’s in the Ansible-Community org, perhaps the [@CommunityTeam](https://forum.ansible.com/groups/communityteam) would be able to help?

---

<div class="post-metadata">

**Author:** ![oranod](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/oranod/32/1434_2.png) [@oranod](https://forum.ansible.com/u/oranod)\
**Post date:** [September 19, 2024, 2:59pm UTC](https://forum.ansible.com/t/broken-ci-in-ansible-community-molecule-plugins-github-project/8611/3 "2024-09-19T14:59:02Z")

</div>

Thanks for the ping @Denney-tech. @cnfrancis I’ve approved and pinged @ssbarnea for review as well.

---

<div class="post-metadata">

**Author:** ![cnfrancis](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/cnfrancis/32/2615_2.png) [@cnfrancis](https://forum.ansible.com/u/cnfrancis)\
**Post date:** [September 19, 2024, 3:01pm UTC](https://forum.ansible.com/t/broken-ci-in-ansible-community-molecule-plugins-github-project/8611/4 "2024-09-19T15:01:48Z")

</div>

amazing thank you! @Denney-tech @oranod