Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1990900 - When deploy Satellite6.10, failed by "[ERROR ] [configure] /Stage[main]/Foreman_proxy::Plugin::Ansible::Runner/Package[ansible-runner]/ensure: change from 'purged' to 'present' failed"
Summary: When deploy Satellite6.10, failed by "[ERROR ] [configure] /Stage[main]/Forem...
Keywords:
Status: CLOSED DUPLICATE of bug 1990897
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Devendra Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-06 14:36 UTC by qianzhan
Modified: 2021-08-09 13:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-09 13:45:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description qianzhan 2021-08-06 14:36:11 UTC 
Description of problem:
When deploy Satellite6.10, failed by "[ERROR ] [configure] /Stage[main]/Foreman_proxy::Plugin::Ansible::Runner/Package[ansible-runner]/ensure: change from 'purged' to 'present' failed"

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. On RHEL7.7 system, enable related repos for Satellite6.10:
[root@ent-01-vm-01 ~]# subscription-manager repos --list-enabled
----------------------------------------------------------
Available Repositories in /etc/yum.repos.d/redhat.repo
----------------------------------------------------------
Repo ID: rhel-server-rhscl-7-rpms
Repo Name: Red Hat Software Collections RPMs for Red Hat Enterprise Linux 7 Server
Repo URL: https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/rhscl/1/os
Enabled: 1

Repo ID: rhel-7-server-ansible-2.9-rpms
Repo Name: Red Hat Ansible Engine 2.9 RPMs for Red Hat Enterprise Linux 7 Server
Repo URL: https://cdn.redhat.com/content/dist/rhel/server/7/7Server/$basearch/ansible/2.9/os
Enabled: 1

Repo ID: rhel-7-server-rpms
Repo Name: Red Hat Enterprise Linux 7 Server (RPMs)
Repo URL: https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os
Enabled: 1

[root@ent-01-vm-01 ~]# cat /etc/yum.repos.d/satellite.repo
[Sat6-CI_Red_Hat_Satellite_6_10_Composes_Satellite_6_10_RHEL7]
metadata_expire = 1
baseurl = http://dogfood.sat.engineering.redhat.com/pulp/repos/Sat6-CI/QA/Satellite_6_10_with_RHEL7_Server/custom/Satellite_6_10_Composes/Satellite_6_10_RHEL7/
name = Satellite 6.10 RHEL7
enabled = 1
gpgcheck = 0

[Sat6-CI_Red_Hat_Satellite_6_10_Composes_Satellite_Tools_6_10_RHEL7]
metadata_expire = 1
baseurl = http://dogfood.sat.engineering.redhat.com/pulp/repos/Sat6-CI/QA/Satellite_6_10_with_RHEL7_Server/custom/Satellite_Tools_6_10_Composes/Satellite_Tools_6_10_RHEL7_$basearch/
name = Tools 6.10 RHEL7
enabled = 1
gpgcheck = 0

[Sat6-CI_Red_Hat_Satellite_6_10_Composes_Satellite_Maintenance_Next_RHEL7]
name=Satellite 6 Maintenance Next
baseurl = http://dogfood.sat.engineering.redhat.com/pulp/repos/Sat6-CI/QA/Satellite_6_10_with_RHEL7_Server/custom/Satellite_Maintenance_Next_Composes/Satellite_Maintenance_Next_RHEL7/
enabled=1
gpgcheck=0

2. Install Satellite successully:
[root@ent-01-vm-01 ~]# yum install -y satellite


3. Deploy Satellite6.10:
[root@ent-01-vm-01 ~]# satellite-installer --scenario satellite --foreman-initial-admin-password=admin
2021-08-05 23:11:39 [NOTICE] [root] Loading installer configuration. This will take some time.
2021-08-05 23:11:45 [NOTICE] [root] Running installer with log based terminal output at level NOTICE.
2021-08-05 23:11:45 [NOTICE] [root] Use -l to set the terminal output log level to ERROR, WARN, NOTICE, INFO, or DEBUG. See --full-help for definitions.
2021-08-05 23:19:44 [NOTICE] [configure] Starting system configuration.
2021-08-05 23:21:46 [NOTICE] [configure] 250 configuration steps out of 2012 steps complete.
2021-08-05 23:28:16 [NOTICE] [configure] 500 configuration steps out of 2012 steps complete.
2021-08-05 23:33:02 [ERROR ] [configure] Execution of '/bin/yum -d 0 -e 0 -y install ansible-runner' returned 1: One of the configured repositories failed (Ansible runner),
2021-08-05 23:33:02 [ERROR ] [configure] and yum doesn't have enough cached data to continue. At this point the only
2021-08-05 23:33:02 [ERROR ] [configure] safe thing yum can do is fail. There are a few ways to work "fix" this:
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] 1. Contact the upstream for the repository and get them to fix the problem.
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] 2. Reconfigure the baseurl/etc. for the repository, to point to a working
2021-08-05 23:33:02 [ERROR ] [configure] upstream. This is most often useful if you are using a newer
2021-08-05 23:33:02 [ERROR ] [configure] distribution release than is supported by the repository (and the
2021-08-05 23:33:02 [ERROR ] [configure] packages for the previous distribution release still work).
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] 3. Run the command with the repository temporarily disabled
2021-08-05 23:33:02 [ERROR ] [configure] yum --disablerepo=ansible-runner ...
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] 4. Disable the repository permanently, so yum won't use it by default. Yum
2021-08-05 23:33:02 [ERROR ] [configure] will then just ignore the repository until you permanently enable it
2021-08-05 23:33:02 [ERROR ] [configure] again or use --enablerepo for temporary usage:
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] yum-config-manager --disable ansible-runner
2021-08-05 23:33:02 [ERROR ] [configure] or
2021-08-05 23:33:02 [ERROR ] [configure] subscription-manager repos --disable=ansible-runner
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] 5. Configure the failing repository to be skipped, if it is unavailable.
2021-08-05 23:33:02 [ERROR ] [configure] Note that yum will try to contact the repo. when it runs most commands,
2021-08-05 23:33:02 [ERROR ] [configure] so will have to try and fail each time (and thus. yum will be be much
2021-08-05 23:33:02 [ERROR ] [configure] slower). If it is a very temporary problem though, this is often a nice
2021-08-05 23:33:02 [ERROR ] [configure] compromise:
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] yum-config-manager --save --setopt=ansible-runner.skip_if_unavailable=true
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] failure: repodata/repomd.xml from ansible-runner: [Errno 256] No more mirrors to try.
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Plugin::Ansible::Runner/Package[ansible-runner]/ensure: change from 'purged' to 'present' failed: Execution of '/bin/yum -d 0 -e 0 -y install ansible-runner' returned 1: One of the configured repositories failed (Ansible runner),
2021-08-05 23:33:02 [ERROR ] [configure] and yum doesn't have enough cached data to continue. At this point the only
2021-08-05 23:33:02 [ERROR ] [configure] safe thing yum can do is fail. There are a few ways to work "fix" this:
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] 1. Contact the upstream for the repository and get them to fix the problem.
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] 2. Reconfigure the baseurl/etc. for the repository, to point to a working
2021-08-05 23:33:02 [ERROR ] [configure] upstream. This is most often useful if you are using a newer
2021-08-05 23:33:02 [ERROR ] [configure] distribution release than is supported by the repository (and the
2021-08-05 23:33:02 [ERROR ] [configure] packages for the previous distribution release still work).
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] 3. Run the command with the repository temporarily disabled
2021-08-05 23:33:02 [ERROR ] [configure] yum --disablerepo=ansible-runner ...
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] 4. Disable the repository permanently, so yum won't use it by default. Yum
2021-08-05 23:33:02 [ERROR ] [configure] will then just ignore the repository until you permanently enable it
2021-08-05 23:33:02 [ERROR ] [configure] again or use --enablerepo for temporary usage:
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] yum-config-manager --disable ansible-runner
2021-08-05 23:33:02 [ERROR ] [configure] or
2021-08-05 23:33:02 [ERROR ] [configure] subscription-manager repos --disable=ansible-runner
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] 5. Configure the failing repository to be skipped, if it is unavailable.
2021-08-05 23:33:02 [ERROR ] [configure] Note that yum will try to contact the repo. when it runs most commands,
2021-08-05 23:33:02 [ERROR ] [configure] so will have to try and fail each time (and thus. yum will be be much
2021-08-05 23:33:02 [ERROR ] [configure] slower). If it is a very temporary problem though, this is often a nice
2021-08-05 23:33:02 [ERROR ] [configure] compromise:
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] yum-config-manager --save --setopt=ansible-runner.skip_if_unavailable=true
2021-08-05 23:33:02 [ERROR ] [configure]
2021-08-05 23:33:02 [ERROR ] [configure] failure: repodata/repomd.xml from ansible-runner: [Errno 256] No more mirrors to try.
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:02 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:33:05 [NOTICE] [configure] 750 configuration steps out of 2015 steps complete.
2021-08-05 23:38:01 [ERROR ] [configure] Execution of '/bin/yum -d 0 -e 0 -y install python3-pulp-container' returned 1: One of the configured repositories failed (Ansible runner),
2021-08-05 23:38:01 [ERROR ] [configure] and yum doesn't have enough cached data to continue. At this point the only
2021-08-05 23:38:01 [ERROR ] [configure] safe thing yum can do is fail. There are a few ways to work "fix" this:
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] 1. Contact the upstream for the repository and get them to fix the problem.
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] 2. Reconfigure the baseurl/etc. for the repository, to point to a working
2021-08-05 23:38:01 [ERROR ] [configure] upstream. This is most often useful if you are using a newer
2021-08-05 23:38:01 [ERROR ] [configure] distribution release than is supported by the repository (and the
2021-08-05 23:38:01 [ERROR ] [configure] packages for the previous distribution release still work).
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] 3. Run the command with the repository temporarily disabled
2021-08-05 23:38:01 [ERROR ] [configure] yum --disablerepo=ansible-runner ...
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] 4. Disable the repository permanently, so yum won't use it by default. Yum
2021-08-05 23:38:01 [ERROR ] [configure] will then just ignore the repository until you permanently enable it
2021-08-05 23:38:01 [ERROR ] [configure] again or use --enablerepo for temporary usage:
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] yum-config-manager --disable ansible-runner
2021-08-05 23:38:01 [ERROR ] [configure] or
2021-08-05 23:38:01 [ERROR ] [configure] subscription-manager repos --disable=ansible-runner
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] 5. Configure the failing repository to be skipped, if it is unavailable.
2021-08-05 23:38:01 [ERROR ] [configure] Note that yum will try to contact the repo. when it runs most commands,
2021-08-05 23:38:01 [ERROR ] [configure] so will have to try and fail each time (and thus. yum will be be much
2021-08-05 23:38:01 [ERROR ] [configure] slower). If it is a very temporary problem though, this is often a nice
2021-08-05 23:38:01 [ERROR ] [configure] compromise:
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] yum-config-manager --save --setopt=ansible-runner.skip_if_unavailable=true
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] failure: repodata/repomd.xml from ansible-runner: [Errno 256] No more mirrors to try.
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] /Stage[main]/Pulpcore::Plugin::Container/Pulpcore::Plugin[container]/Package[python3-pulp-container]/ensure: change from 'purged' to 'present' failed: Execution of '/bin/yum -d 0 -e 0 -y install python3-pulp-container' returned 1: One of the configured repositories failed (Ansible runner),
2021-08-05 23:38:01 [ERROR ] [configure] and yum doesn't have enough cached data to continue. At this point the only
2021-08-05 23:38:01 [ERROR ] [configure] safe thing yum can do is fail. There are a few ways to work "fix" this:
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] 1. Contact the upstream for the repository and get them to fix the problem.
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] 2. Reconfigure the baseurl/etc. for the repository, to point to a working
2021-08-05 23:38:01 [ERROR ] [configure] upstream. This is most often useful if you are using a newer
2021-08-05 23:38:01 [ERROR ] [configure] distribution release than is supported by the repository (and the
2021-08-05 23:38:01 [ERROR ] [configure] packages for the previous distribution release still work).
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] 3. Run the command with the repository temporarily disabled
2021-08-05 23:38:01 [ERROR ] [configure] yum --disablerepo=ansible-runner ...
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] 4. Disable the repository permanently, so yum won't use it by default. Yum
2021-08-05 23:38:01 [ERROR ] [configure] will then just ignore the repository until you permanently enable it
2021-08-05 23:38:01 [ERROR ] [configure] again or use --enablerepo for temporary usage:
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] yum-config-manager --disable ansible-runner
2021-08-05 23:38:01 [ERROR ] [configure] or
2021-08-05 23:38:01 [ERROR ] [configure] subscription-manager repos --disable=ansible-runner
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] 5. Configure the failing repository to be skipped, if it is unavailable.
2021-08-05 23:38:01 [ERROR ] [configure] Note that yum will try to contact the repo. when it runs most commands,
2021-08-05 23:38:01 [ERROR ] [configure] so will have to try and fail each time (and thus. yum will be be much
2021-08-05 23:38:01 [ERROR ] [configure] slower). If it is a very temporary problem though, this is often a nice
2021-08-05 23:38:01 [ERROR ] [configure] compromise:
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] yum-config-manager --save --setopt=ansible-runner.skip_if_unavailable=true
2021-08-05 23:38:01 [ERROR ] [configure]
2021-08-05 23:38:01 [ERROR ] [configure] failure: repodata/repomd.xml from ansible-runner: [Errno 256] No more mirrors to try.
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:38:01 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] Execution of '/bin/yum -d 0 -e 0 -y install python3-pulp-file' returned 1: One of the configured repositories failed (Ansible runner),
2021-08-05 23:42:44 [ERROR ] [configure] and yum doesn't have enough cached data to continue. At this point the only
2021-08-05 23:42:44 [ERROR ] [configure] safe thing yum can do is fail. There are a few ways to work "fix" this:
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] 1. Contact the upstream for the repository and get them to fix the problem.
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] 2. Reconfigure the baseurl/etc. for the repository, to point to a working
2021-08-05 23:42:44 [ERROR ] [configure] upstream. This is most often useful if you are using a newer
2021-08-05 23:42:44 [ERROR ] [configure] distribution release than is supported by the repository (and the
2021-08-05 23:42:44 [ERROR ] [configure] packages for the previous distribution release still work).
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] 3. Run the command with the repository temporarily disabled
2021-08-05 23:42:44 [ERROR ] [configure] yum --disablerepo=ansible-runner ...
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] 4. Disable the repository permanently, so yum won't use it by default. Yum
2021-08-05 23:42:44 [ERROR ] [configure] will then just ignore the repository until you permanently enable it
2021-08-05 23:42:44 [ERROR ] [configure] again or use --enablerepo for temporary usage:
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] yum-config-manager --disable ansible-runner
2021-08-05 23:42:44 [ERROR ] [configure] or
2021-08-05 23:42:44 [ERROR ] [configure] subscription-manager repos --disable=ansible-runner
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] 5. Configure the failing repository to be skipped, if it is unavailable.
2021-08-05 23:42:44 [ERROR ] [configure] Note that yum will try to contact the repo. when it runs most commands,
2021-08-05 23:42:44 [ERROR ] [configure] so will have to try and fail each time (and thus. yum will be be much
2021-08-05 23:42:44 [ERROR ] [configure] slower). If it is a very temporary problem though, this is often a nice
2021-08-05 23:42:44 [ERROR ] [configure] compromise:
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] yum-config-manager --save --setopt=ansible-runner.skip_if_unavailable=true
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] failure: repodata/repomd.xml from ansible-runner: [Errno 256] No more mirrors to try.
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] /Stage[main]/Pulpcore::Plugin::File/Pulpcore::Plugin[file]/Package[python3-pulp-file]/ensure: change from 'purged' to 'present' failed: Execution of '/bin/yum -d 0 -e 0 -y install python3-pulp-file' returned 1: One of the configured repositories failed (Ansible runner),
2021-08-05 23:42:44 [ERROR ] [configure] and yum doesn't have enough cached data to continue. At this point the only
2021-08-05 23:42:44 [ERROR ] [configure] safe thing yum can do is fail. There are a few ways to work "fix" this:
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] 1. Contact the upstream for the repository and get them to fix the problem.
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] 2. Reconfigure the baseurl/etc. for the repository, to point to a working
2021-08-05 23:42:44 [ERROR ] [configure] upstream. This is most often useful if you are using a newer
2021-08-05 23:42:44 [ERROR ] [configure] distribution release than is supported by the repository (and the
2021-08-05 23:42:44 [ERROR ] [configure] packages for the previous distribution release still work).
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] 3. Run the command with the repository temporarily disabled
2021-08-05 23:42:44 [ERROR ] [configure] yum --disablerepo=ansible-runner ...
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] 4. Disable the repository permanently, so yum won't use it by default. Yum
2021-08-05 23:42:44 [ERROR ] [configure] will then just ignore the repository until you permanently enable it
2021-08-05 23:42:44 [ERROR ] [configure] again or use --enablerepo for temporary usage:
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] yum-config-manager --disable ansible-runner
2021-08-05 23:42:44 [ERROR ] [configure] or
2021-08-05 23:42:44 [ERROR ] [configure] subscription-manager repos --disable=ansible-runner
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] 5. Configure the failing repository to be skipped, if it is unavailable.
2021-08-05 23:42:44 [ERROR ] [configure] Note that yum will try to contact the repo. when it runs most commands,
2021-08-05 23:42:44 [ERROR ] [configure] so will have to try and fail each time (and thus. yum will be be much
2021-08-05 23:42:44 [ERROR ] [configure] slower). If it is a very temporary problem though, this is often a nice
2021-08-05 23:42:44 [ERROR ] [configure] compromise:
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] yum-config-manager --save --setopt=ansible-runner.skip_if_unavailable=true
2021-08-05 23:42:44 [ERROR ] [configure]
2021-08-05 23:42:44 [ERROR ] [configure] failure: repodata/repomd.xml from ansible-runner: [Errno 256] No more mirrors to try.
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"
2021-08-05 23:42:44 [ERROR ] [configure] https://releases.ansible.com/ansible-runner/rpm/epel-7-x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to releases.ansible.com:443; Operation now in progress"

Actual results:
As step 3, satellite6.10 deployment failed

Expected results:
satellite6.10 deployment should succeed.

Additional info:
Comment 1 Brad Buckingham 2021-08-09 13:45:39 UTC 

*** This bug has been marked as a duplicate of bug 1990897 ***
Note You need to log in before you can comment on or make changes to this bug.