yum_repository shouldn't require baseurl/metalink/mirrorlist to disable a repository

[rgarrigue]

SUMMARY

With yum on CentOS and most likely RHEL, Fedora, you might want to get rid of OS repositories in favor of local mirror. If you remove them, the OS might re-create them at the next yum update, so personnaly I disable them.

But ansile can't disable (enabled=false) a yum_repository without knowing its baseurl/metalink/mirrorlist. It can just remove it (state=absent).

I wish enabled=false behave the same way as state=absent, just find the unique [reponame] in the files without caring about baseurl & so on, which might change over time

ISSUE TYPE

• Feature Idea

COMPONENT NAME

yum_repository

[ansibot]

Files identified in the description:

• lib/ansible/modules/packaging/os/yum_repository.py

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[ansibot]

cc @jtyr
click here for bot help

[jtyr]

Thanks for opening this issue. I will try to look into it.

[ansiblejunky]

Yes, the yum_repository module should handle this similarly to how the `rhsm_repository' module handles it.

The `rhsm_repository' module allows for this simple way to disable all repos:

- name: Disable all RHSM repositories
  rhsm_repository:
    name: '*'
    state: disabled

Therefore, the yum_repository module should allow for the following, without user having to know about files or repo ID or anything else really. The user is simply trying to disable all repos managed by Yum.

- name: Disable all RHSM repositories
  yum_repository:
    name: '*'
    state: disabled

I had a customer recently who wanted to provision their servers to prepare for an Ansible Tower installation. So we wanted to cleanup any defined repos for both Yum managed and RHSM managed.

[markusdd]

I strongly want to support this idea, because I just ran across the exact same issue.
I'm currently writing a playbook which pre-configures our nodes for an openshift deployment, where the official instructions want you to disable EPEL from a certain point on.

EPEL is installed on CentOS 7 via epel-release, so I absolutely do not care what the URLs etc are.

I just want:

  - name: Deactivate EPEL
    yum_repository:
        name: epel
        state: present
        enabled: no

By the way, this would also serve as a sanity check. When you specify state present without any repo info, and the file is not there (because yum install epel-release failed in some strange way), you would correctly error out.

[ansibot]

Files identified in the description:

• lib/ansible/modules/yum_repository.py

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help

[MichaelDBA]

Anyone planning on fixing this issue anytime soon?

[ansibot]

Thank you very much for your submission to Ansible. It means a lot to us that you've taken time to contribute.

Unfortunately, this issue has been open for some time while waiting for a contributor to take it up but there does not seem to have been anyone that did so. So we are going to close this issue to clear up the queues and make it easier for contributors to browse possible implementation targets.

However, we're absolutely always up for discussion. Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time. If you or anyone else has any further questions, please let us know by using any of the communication methods listed in the page below:

• https://docs.ansible.com/ansible/latest/community/communication.html

In the future, sometimes starting a discussion on the development list prior to proposing or implementing a feature can make getting things included a little easier, but it's not always necessary.

Thank you once again for this and your interest in Ansible!

click here for bot help

[markusdd]

don't get why this is being closed.

this is still aproblem until this day.

[mkrizek]

@markusdd The functionality can still implemented, anyone is free to send a PR but no one has done so while the issue has been open for a long time.