Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Installer leaks "yum install -y -q rh-mongodb34-syspaths finished successfully!" message which should be in log only.
Version-Release number of selected component (if applicable):
satellite-6.6.0-4.beta.el7sat.noarch
How reproducible:
1 of 1
Steps to Reproduce:
1. yum -y install satellite
2. time satellite-installer --scenario satellite --foreman-proxy-dhcp true --foreman-proxy-dhcp-interface eth1 --foreman-proxy-dhcp-gateway 192.168.11.2 --foreman-proxy-dhcp-nameservers 192.168.11.2 --foreman-proxy-dhcp-netmask 255.255.255.0 --foreman-proxy-dhcp-network 192.168.11.0 --foreman-proxy-dhcp-option-domain nodhcp.local --foreman-proxy-dhcp-pxeserver 192.168.11.2 --foreman-proxy-dhcp-range "192.168.11.100 192.168.11.200" --foreman-proxy-dns true --foreman-proxy-dns-forwarders 192.168.11.1 --foreman-proxy-dns-interface eth1 --foreman-proxy-dns-reverse 11.168.192.in-addr.arpa --foreman-proxy-dns-zone nodhcp.local --foreman-proxy-tftp true --foreman-proxy-tftp-servername=192.168.11.2
Actual results:
[root@satellite ~]# time satellite-installer --scenario satellite --foreman-proxy-dhcp true --foreman-proxy-dhcp-interface eth1 --foreman-proxy-dhcp-gateway 192.168.11.2 --foreman-proxy-dhcp-nameservers 192.168.11.2 --foreman-proxy-dhcp-netmask 255.255.255.0 --foreman-proxy-dhcp-network 192.168.11.0 --foreman-proxy-dhcp-option-domain nodhcp.local --foreman-proxy-dhcp-pxeserver 192.168.11.2 --foreman-proxy-dhcp-range "192.168.11.100 192.168.11.200" --foreman-proxy-dns true --foreman-proxy-dns-forwarders 192.168.11.1 --foreman-proxy-dns-interface eth1 --foreman-proxy-dns-reverse 11.168.192.in-addr.arpa --foreman-proxy-dns-zone nodhcp.local --foreman-proxy-tftp true --foreman-proxy-tftp-servername=192.168.11.2
Installing Done [100%] [...........................................................................................................................................................]
Success!
* Satellite is running at https://satellite.nodhcp.local
* To install an additional Capsule on separate machine continue by running:
capsule-certs-generate --foreman-proxy-fqdn "$CAPSULE" --certs-tar "/root/$CAPSULE-certs.tar"
* To upgrade an existing 6.5 Capsule to 6.6:
Please see official documentation for steps and parameters to use when upgrading a 6.5 Capsule to 6.6.
The full log is at /var/log/foreman-installer/satellite.log
yum install -y -q rh-mongodb34-syspaths finished successfully!
real 15m31.035s
user 10m50.406s
sys 1m16.948s
Expected results:
There should not be "yum install -y -q rh-mongodb34-syspaths finished successfully!" in the output.