Description of problem: When one creates a custom repo but doesn't generate an entitlement certificate yet, 'c' option (list custom repository entitlements) returns "No custom repositories exist in the RHUI.", but it should be "No custom repository entitlements exist in the RHUI." Version-Release number of selected component (if applicable): >> rpm -qa *rhui* rhui-installer-base-0.0.24-1.el7ui.noarch rh-rhui-tools-libs-pre.3.0.16-1.el7ui.noarch rhui-installer-0.0.24-1.el7ui.noarch rh-rhui-tools-pre.3.0.16-1.el7ui.noarch rhui-default-ca-1.0-1.noarch rh-amazon-rhui-client-2.2.118-1.el7.noarch rh-amazon-rhui-client-rhs30-2.2.124-1.el7.noarch RHUI iso 20151013 How reproducible: always Steps to Reproduce: 1. create one or two custom repos (home RHUI screen -> 'r' -> 'c') and specify that these repo should require an entitlement certificate to access 2. list repos to ensure they exist 3. go to Entitlements Manager screen: 'home' -> 'n' 4. 'c' list custom repository entitlements 5. observe the message Custom Repository Entitlements No custom repositories exist in the RHUI. Actual results: rhui (repo) => c Unique ID for the custom repository (alphanumerics, _, and - only): repo_1 Display name for the custom repository [repo_1]: Path at which the repository will be served [repo_1]: Algorithm to use when calculating the checksum values for repository metadata: * Select "sha256" for RHEL6: * Select "sha1" for either RHEL5 or RHEL6: 1 - sha256 2 - sha1 Enter value (1-2) or 'b' to abort: 1 Should the repository require an entitlement certificate to access? (y/n) y Based on the repository's relative path, the suggested entitlement path is: repo_1 Path that should be used when granting an entitlement for this repository. This may use yum variable substitutions (e.g. $basearch) to group this together with other repositories that share the entitlement [repo_1]: Should the repository require clients to perform a GPG check and verify packages are signed by a GPG key? (y/n) n The following repository will be created: ID: repo_1 Name: repo_1 Path: repo_1 Entitlement: repo_1 GPG Check No Red Hat GPG Key: No Proceed? (y/n) y Successfully created repository repo_1 ------------------------------------------------------------------------------ rhui (repo) => c Unique ID for the custom repository (alphanumerics, _, and - only): repo_2 Display name for the custom repository [repo_2]: Path at which the repository will be served [repo_2]: Algorithm to use when calculating the checksum values for repository metadata: * Select "sha256" for RHEL6: * Select "sha1" for either RHEL5 or RHEL6: 1 - sha256 2 - sha1 Enter value (1-2) or 'b' to abort: 1 Should the repository require an entitlement certificate to access? (y/n) y Based on the repository's relative path, the suggested entitlement path is: repo_2 Path that should be used when granting an entitlement for this repository. This may use yum variable substitutions (e.g. $basearch) to group this together with other repositories that share the entitlement [repo_2]: Should the repository require clients to perform a GPG check and verify packages are signed by a GPG key? (y/n) n The following repository will be created: ID: repo_2 Name: repo_2 Path: repo_2 Entitlement: repo_2 GPG Check No Red Hat GPG Key: No Proceed? (y/n) y Successfully created repository repo_2 ------------------------------------------------------------------------------ rhui (repo) => l Custom Repositories repo_1 repo_2 rhui (entitlements) => c Custom Repository Entitlements No custom repositories exist in the RHUI. Expected results: A message: "No custom repository entitlements exist in the RHUI."
Steps #1 and #2 are optional. Those are just to demonstrate that the message by 'c' is wrong and repos exist. rhui (repo) => l Custom Repositories repo_1 repo_2 ------------------------------------------------------------------------------ rhui (repo) => d Select one or more repositories: Custom Repositories - 1 : repo_1 - 2 : repo_2 Red Hat Repositories Enter value (1-2) to toggle selection, 'c' to confirm selections, or '?' for more commands: 1-2 Select one or more repositories: Custom Repositories x 1 : repo_1 x 2 : repo_2 Red Hat Repositories Enter value (1-2) to toggle selection, 'c' to confirm selections, or '?' for more commands: c The following repositories will be deleted: Custom Repositories repo_1 repo_2 Proceed? (y/n) y Delete repo_1 task has been queued up...repo will be deleted at the next available time slot Delete repo_2 task has been queued up...repo will be deleted at the next available time slot ------------------------------------------------------------------------------ rhui (repo) => l No repositories are currently managed by the RHUI Now it's False True =)
Hm, I think it was fixed somewhere earlier because I reported BZ 1397412 which doesn't have this issue... Anyway, evrth is ok on 20161122 iso: when there are protected custom repos: ------------------------------------------------------------------------------ -= Red Hat Update Infrastructure Management Tool =- -= Entitlements Manager =- l list Red Hat content certificate entitlements c list custom repository entitlements u upload a new or updated Red Hat content certificate Connected: rhua.example.com ------------------------------------------------------------------------------ rhui (entitlements) => c Custom Repository Entitlements For each entitlement URL listed, the corresponding repositories that are configured with that entitlement are listed. protected/protected_custom_repo1 Name: protected_custom_repo1 URL: protected/protected_custom_repo1 protected/protected_custom_repo2 Name: protected_custom_repo2 URL: protected/protected_custom_repo2 ------------------------------------------------------------------------------ when there are no repos: rhui (entitlements) => c Custom Repository Entitlements No custom repository entitlements exist in the RHUI. ------------------------------------------------------------------------------
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-2017:0367