Bug 1345862 - repos created in pulp-admin are not displayed in RHUI-manager
Summary: repos created in pulp-admin are not displayed in RHUI-manager
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: Documentation
Version: 3.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 3.0.0
Assignee: RHSM Documentation
QA Contact: Irina Gulina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-13 10:42 UTC by Irina Gulina
Modified: 2017-03-01 22:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-01 22:12:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0367 0 normal SHIPPED_LIVE Red Hat Update Infrastructure 3.0 Release 2017-03-02 03:05:22 UTC

Description Irina Gulina 2016-06-13 10:42:29 UTC
Description of problem:

If to create an rpm repo via pulp-admin, it will never be displayed in rhui-manager

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

>> rpm -qa "*rhui*"
rh-amazon-rhui-client-rhs30-2.2.130-1.el7.noarch
rhui-installer-base-0.0.28-1.el7ui.noarch
rh-rhui-tools-pre.3.0.16-1.el7ui.noarch
rhui-default-ca-1.0-1.noarch
rh-rhui-tools-libs-pre.3.0.16-1.el7ui.noarch
rh-amazon-rhui-client-2.2.124-1.el7.noarch
rhui-installer-0.0.28-1.el7ui.noarch

>> rpm -qa "*pulp*"
python-pulp-oid_validation-2.8.1.3-2.el7ui.noarch
python-pulp-docker-common-2.0.0.2-1.el7ui.noarch
pulp-ostree-plugins-1.1.0.2-1.el7ui.noarch
python-pulp-client-lib-2.8.1.3-2.el7ui.noarch
pulp-rpm-admin-extensions-2.8.1-3.el7ui.noarch
python-pulp-common-2.8.1.3-2.el7ui.noarch
python-pulp-repoauth-2.8.1.3-2.el7ui.noarch
pulp-rpm-plugins-2.8.1-3.el7ui.noarch
pulp-docker-plugins-2.0.0.2-1.el7ui.noarch
python-pulp-ostree-common-1.1.0.2-1.el7ui.noarch
python-pulp-bindings-2.8.1.3-2.el7ui.noarch
pulp-admin-client-2.8.1.3-2.el7ui.noarch
python-pulp-rpm-common-2.8.1-3.el7ui.noarch
pulp-server-2.8.1.3-2.el7ui.noarch
pulp-selinux-2.8.1.3-2.el7ui.noarch


How reproducible:
always

Steps to Reproduce:
1. create rpm repo in pulp-admin
2. list repos in rhui-manager
3. observe there is none displayed

Actual results:

Connected: rhua.example.com
------------------------------------------------------------------------------
rhui (repo) => l

No repositories are currently managed by the RHUI

>> pulp-admin rpm repo create --repo-id zoo --feed=https://repos.fedorapeople.org/repos/pulp/pulp/demo_repos/zoo/
Successfully created repository [zoo]

[root@rhua ~]# pulp-admin rpm repo list
+----------------------------------------------------------------------+
                            RPM Repositories
+----------------------------------------------------------------------+

Id:                  zoo
Display Name:        None
Description:         None
Content Unit Counts: 


[root@rhua ~]# pulp-admin rpm repo sync run --repo-id zoo
+----------------------------------------------------------------------+
                     Synchronizing Repository [zoo]
+----------------------------------------------------------------------+

This command may be exited via ctrl+c without affecting the request.


Downloading metadata...
[\]
... completed

Downloading repository content...
[-]
[==================================================] 100%
RPMs:       32/32 items
Delta RPMs: 0/0 items

... completed

Downloading distribution files...
[==================================================] 100%
Distributions: 0/0 items
... completed

Importing errata...
[\]
... completed

Importing package groups/categories...
[-]
... completed

Cleaning duplicate packages...
[-]
... completed


Task Succeeded



Initializing repo metadata
[-]
... completed

Publishing Distribution files
[-]
... completed

Publishing RPMs
[==================================================] 100%
32 of 32 items
... completed

Publishing Delta RPMs
... skipped

Publishing Errata
[==================================================] 100%
4 of 4 items
... completed

Publishing Comps file
[==================================================] 100%
3 of 3 items
... completed

Publishing Metadata.
[-]
... completed

Closing repo metadata
[-]
... completed

Generating sqlite files
... skipped

Publishing files to web
[-]
... completed

Writing Listings File
[-]
... completed


Task Succeeded


>> pulp-admin rpm repo list
+----------------------------------------------------------------------+
                            RPM Repositories
+----------------------------------------------------------------------+

Id:                  zoo
Display Name:        None
Description:         None
Content Unit Counts: 
  Erratum:          4
  Package Category: 1
  Package Group:    2
  Rpm:              32





 Connected: rhua.example.com
------------------------------------------------------------------------------
rhui (repo) => l

No repositories are currently managed by the RHUI

------------------------------------------------------------------------------
rhui (repo) => 



Expected results:
repo created in pulp-admin is displayed in rhui-manager


Additional info:
Tried logout/login, the weekend passed, the zoo repo never appeared in rhui-manager.
If to create a repo in rhui-manager, it will be displayed in pulp-admin at the same moment

------------------------------------------------------------------------------
rhui (repo) => c

Unique ID for the custom repository (alphanumerics, _, and - only):
test_repo

Display name for the custom repository [test_repo]:


Path at which the repository will be served [test_repo]:


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)
n

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:              test_repo
  Name:            test_repo
  Path:            test_repo
  GPG Check        No
  Red Hat GPG Key: No
Proceed? (y/n) y

Successfully created repository test_repo

>> pulp-admin rpm repo list
+----------------------------------------------------------------------+
                            RPM Repositories
+----------------------------------------------------------------------+

Id:                  zoo
Display Name:        None
Description:         None
Content Unit Counts: 
  Erratum:          4
  Package Category: 1
  Package Group:    2
  Rpm:              32

Id:                  test_repo
Display Name:        test_repo
Description:         test_repo
Content Unit Counts:

Comment 1 Irina Gulina 2016-06-13 10:45:44 UTC
maybe connected to 1345862

Comment 4 Irina Gulina 2016-06-13 14:24:05 UTC
It will be confusing if one creates a repo in rhui-manager and sees Uniqueness Id message since it already exists in pulp-admin ( and not displayed in rhui-manager)

Comment 5 Irina Gulina 2016-06-16 15:23:44 UTC
Moved to documentation BZ.

Note. If repo 'foo' created in pulp-admin wasn't added in 'custom' group, 'foo' is not displayed in rhui-manager. If one wants to create a repo with the same ID 'foo' in rhui-manager and is not aware of repo 'foo' created in pulp-admin, a message "A repository with ID "foo" already exists".

Comment 8 errata-xmlrpc 2017-03-01 22:12:11 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, 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


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