Description of problem: When zypper commands are run for the first time against Satellite-provided repos, subscription-manager prompts interactively to accept if the repo is unsigned. Version-Release number of selected component (if applicable): Red Hat Satellite tools (i.e. subscription-manager + zypper plugins) for: SLES11 sp4 SLES12 SLES15 How reproducible: Always Steps to Reproduce: 1. Ensure cache is cleaned or first time executing 2. Install a package from a non-redhat repo provided by Satellite using zypper Actual results: Zypper plugin prompts interactively for acceptance of unsigned repo. Expected results: Zypper can install without interactive prompts. Additional info: The suggestion is a client-side --override for the SLES client tools that can accept the repo, or answer an automatic yes to the prompt.
Verified in latest builds of subman for sles. 11sp4: subscription-manager-1.25.11-7.sles11_4sat.subman_120.x86_64 12sp3: subscription-manager-1.25.20-3.sles12_3sat.x86_64 12sp4: subscription-manager-1.25.20-2.sles12_4sat.x86_64 15sp1: subscription-manager-1.25.20-1.sles15_1sat.x86_64 With the new change, there is no need to accept that Satellite repos are unsigned. Example of the new repos: [subscription-manager:Default_Organization_sles_11sp4] name=11sp4 enabled=1 autorefresh=0 baseurl=https://my.sat.host.com/pulp/repos/Default_Organization/Library/11sp4/custom/sles/11sp4?ssl_verify=host&ssl_clientcert=%2Fetc%2Fpki%2Fentitlement%2F6514123076998026754.pem&ssl_clientkey=%2Fetc%2Fpki%2Fentitlement%2F6514123076998026754-key.pem&ssl_capath=%2Fetc%2Frhsm%2Fca type=NONE gpgcheck=0 service=subscription-manager Note: While testing this bug, I encountered and filed this potentially related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1781887
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, 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/RHBA-2019:4217