Problem with zypper_repository when using .repos

[JensHeinrich]

Summary

When using the zypper_repository module with a repo like http://download.opensuse.org/repositories/server:/monitoring/SLE_15_SP1/server:monitoring.repo will fail after the second run.

I have no idea, how this might be fixed other than the option to provide a name attribute to the task an prefer it when the repo is an URL

Issue Type

Bug Report

Component Name

zypper_repository

Ansible Version

ansible 2.10.4
...
  python version = 3.7.9 (default, Jan  5 2021, 01:21:20) [Clang 8.0.1 (tags/RELEASE_801/final 366581)]

Configuration

OS / Environment

No response

Steps To Reproduce

---
- hosts: all
  become: true
  tasks:

    - community.general.zypper_repository:
        name: server_monitoring
        state: absent

    - community.general.zypper_repository:
        repo: "http://download.opensuse.org/repositories/server:/monitoring/SLE_15_SP1/server:monitoring.repo"
        state: present
 
    - community.general.zypper_repository:
        repo: "http://download.opensuse.org/repositories/server:/monitoring/SLE_15_SP1/server:monitoring.repo"
        state: present

Expected Results

Expected result for first task is undefined
Second should add the repo
Third should register as ok

Actual Results

FAILED! => {"changed": false, "msg": "Zypper failed with rc 4", "rc": 4, "repodata": {"alias": null, "autorefresh": "1", "enabled": "1", "gpgcheck": "1", "name": null, "priority": null, "url": "http://download.opensuse.org/repositories/server:/monitoring/SLE_15_SP1/server:monitoring.repo"}, "state": "present", "stderr": "Ein Repository namens 'server_monitoring' ist bereits vorhanden. Verwenden Sie einen anderen Alias.\n", "stderr_lines": ["Ein Repository namens 'server_monitoring' ist bereits vorhanden. Verwenden Sie einen anderen Alias."], "stdout": "", "stdout_lines": []}

[ansibullbot]

Files identified in the description:

• plugins/modules/packaging/os/zypper_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

[ansibullbot]

cc @matze
click here for bot help

[wombelix]

As far I can see, no one is working on this Issues already, so I will give it a try during the ongoing Ansible Summit / Hackathon

[ansibullbot]

cc @AnderEnder @alxgu @andytom @commel @dcermak @evrardjp @lrupp @sealor @toabctl
click here for bot help