1990897 – 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"

Bug 1990897 - 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 ERRATA
Alias:	None
Product:	Red Hat Satellite
Classification:	Red Hat
Component:	Installation
Sub Component:
Version:	6.10.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	medium
Target Milestone:	6.10.0
Assignee:	Evgeni Golov
QA Contact:	Devendra Singh
Docs Contact:
URL:
Whiteboard:
Duplicates (1):	1990900 (view as bug list)
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2021-08-06 14:31 UTC by qianzhan
Modified:	2022-07-19 16:15 UTC (History)
CC List:	3 users (show)
Fixed In Version:	satellite-installer-6.10.0.5
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2021-11-16 14:13:02 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2021:4702	0	None	None	None	2021-11-16 14:13:12 UTC

Description qianzhan 2021-08-06 14:31:20 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:
Deploy sat610 on RHEL7.7 manually:

1. Set repos for installing 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 satellite6.10 successfully.

3. Deploy Satellite server:
[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

*** Bug 1990900 has been marked as a duplicate of this bug. ***

Comment 2 Brad Buckingham 2021-08-09 13:47:45 UTC

According to the docs [1], the server should be on:
   "The latest version of Red Hat Enterprise Linux 7 Server"

It appears that the server under test is on RHEL 7.7 vs 7.9.  Closing this one as notabug; however, please do re-open if you see the same issue on RHEL 7.9.   Thanks!


[1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.9/html-single/installing_satellite_server_from_a_connected_network/index#system-requirements_satellite

Comment 3 qianzhan 2021-08-10 01:38:03 UTC

(In reply to Brad Buckingham from comment #2)
> According to the docs [1], the server should be on:
>    "The latest version of Red Hat Enterprise Linux 7 Server"
> 
> It appears that the server under test is on RHEL 7.7 vs 7.9.  Closing this
> one as notabug; however, please do re-open if you see the same issue on RHEL
> 7.9.   Thanks!
> 
> 
> [1]
> https://access.redhat.com/documentation/en-us/red_hat_satellite/6.9/html-
> single/installing_satellite_server_from_a_connected_network/index#system-
> requirements_satellite


This issue exists on RHEL7.9, but this time the issue does NOT block the satellite6.10 deployment:

https://main-jenkins-csb-rhsmintegration.apps.ocp4.prod.psi.redhat.com/job/rhsm-integration-satellite-runtest/141/consoleFull


[qianqianzhang@localhost ~]$ ssh root.eng.nay.redhat.com
The authenticity of host 'ent-01-vm-01.lab.eng.nay.redhat.com (10.66.147.48)' can't be established.
ECDSA key fingerprint is SHA256:8GYN2DVJQsBs8EYhkuBVhSViJLrUfQxhRFSRSQA18UE.
ECDSA key fingerprint is MD5:87:2f:e9:29:c1:21:d3:ba:cd:cd:b9:1e:20:7f:ef:da.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'ent-01-vm-01.lab.eng.nay.redhat.com,10.66.147.48' (ECDSA) to the list of known hosts.
root.eng.nay.redhat.com's password:

** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **
This System is reserved by sgao.
To return this system early. You can run the command: return2beaker.sh
Ensure you have your logs off the system before returning to Beaker

To extend your reservation time. You can run the command:
extendtesttime.sh
This is an interactive script. You will be prompted for how many
hours you would like to extend the reservation.
Please ensure that you adhere to the reservation policy
for Beaker systems:
https://home.corp.redhat.com/wiki/extended-reservations-beaker-general-pool-systems

You should verify the watchdog was updated succesfully after
you extend your reservation.
https://beaker.engineering.redhat.com/recipes/10462938

For ssh, kvm, serial and power control operations please look here:
https://beaker.engineering.redhat.com/view/ent-01-vm-01.lab.eng.nay.redhat.com

For the default root password, see:
https://beaker.engineering.redhat.com/prefs/

Beaker Test information:
HOSTNAME=ent-01-vm-01.lab.eng.nay.redhat.com
JOBID=5685400
RECIPEID=10462938
RESULT_SERVER=
DISTRO=RHEL-7.9-20200917.0
ARCHITECTURE=x86_64

Job Whiteboard: rhsm-integration provision, job: rhsm-integration-satellite-provision # 122

Recipe Whiteboard:

Comment 4 Evgeni Golov 2021-08-12 13:43:24 UTC

What are the credentials to that machine? The default beaker pw doesn't work.

Comment 5 Evgeni Golov 2021-08-12 16:09:36 UTC

reproduced locally

Comment 6 qianzhan 2021-08-13 02:24:16 UTC

(In reply to Evgeni Golov from comment #5)
> reproduced locally

Hi Evgeni,

The beaker machine is released. If you need to log in the sat6.10 machine, I will try to reproduce this issue next Monday, and reserve this machine for you.

Comment 7 Evgeni Golov 2021-08-16 05:38:49 UTC

Nah, it's fine, I know what happened.

Comment 10 qianzhan 2021-08-19 03:57:30 UTC

As per the latest satellite6.10 deployment result[1], move this bug from ON_QA to VERIFIED:


[1] https://main-jenkins-csb-rhsmintegration.apps.ocp4.prod.psi.redhat.com/job/rhsm-integration-satellite-runtest/157/consoleFull

Comment 13 errata-xmlrpc 2021-11-16 14:13:02 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.10 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:4702

Note You need to log in before you can comment on or make changes to this bug.