You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using community.general.dnf_config_manager, the process gets stuck after activating a repository (like PGDG extras repository). The module performs the following steps:
Lists existing repositories to check if the target repository is available and whether it is active. This step completes successfully.
Activates the repository if necessary.
Runs a second repolist to verify if the repository was activated (I think).
At this point, the process hangs, as dnf requests the import of the GPG key for the repository.
Run a playbook with dnf_config_manager module in it to enable pgdg-rhel9-extras :
- name: Ensure the PGDG Extra repository is enabledcommunity.general.dnf_config_manager:
name: pgdg-rhel9-extrasstate: enabled
Expected Results
The dnf_config_manager module should complete the repository activation process without blocking. After repository activation, if the GPG key needs to be imported, the module should handle this automatically (perhaps by adding --assumeyes to the repolist command).
Actual Results
Task with this module hangs.
Code of Conduct
I agree to follow the Ansible Code of Conduct
The text was updated successfully, but these errors were encountered:
Summary
When using community.general.dnf_config_manager, the process gets stuck after activating a repository (like PGDG extras repository). The module performs the following steps:
At this point, the process hangs, as dnf requests the import of the GPG key for the repository.
Issue Type
Bug Report
Component Name
dnf_config_manager
Ansible Version
Community.general Version
Configuration
$ ansible-config dump --only-changed
OS / Environment
No response
Steps to Reproduce
dnf_config_manager
module in it to enablepgdg-rhel9-extras
:Expected Results
The
dnf_config_manager
module should complete the repository activation process without blocking. After repository activation, if the GPG key needs to be imported, the module should handle this automatically (perhaps by adding--assumeyes
to the repolist command).Actual Results
Task with this module hangs.
Code of Conduct
The text was updated successfully, but these errors were encountered: