Actions
Bug #16418
closedRepository for MongoDB can not be discovered
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1290917
Description of problem:
When trying to discover the following repository (Repo Discovery):"https://repo.mongodb.org/yum/redhat/7/mongodb-org/3.2/x86_64"
there are no changes under "Results", however, under Monitor=>Tasks it shows that the discovery process was successful and there are no errors reported. In "/var/log/foreman/production.log" there are no errors reported either.
If configuring the same repository using "yum", the packages are found and can be downloaded:
Example:
- cat /etc/yum.repos.d/mongo.repo
[mongo]
baseurl=https://repo.mongodb.org/yum/redhat/7/mongodb-org/3.2/x86_64
gpgcheck=0
enable=1
Other repositories such as "https://packages.vmware.com/tools/esx/5.5latest/rhel6/x86_64" are found without any problems.
As opposed to the specified VMware repository, the "mongodb" repository has separate folders for packages and repodata, however, that seems not to be the problem as already tested in my lab environment.
How reproducible:
Every time
Steps to Reproduce:
1. Content=>Products=>Repo Discovery
2. Enter the URL "https://repo.mongodb.org/yum/redhat/7/mongodb-org/3.2/x86_64"
3. No repositories discovered
Actual results:
The MongoDB repository is not discovered and there are no error messages.
Expected results:
MongoDB repository is discovered and shown under "Results" or an error message is reported why it could not be discovered.
Updated by Eric Helms about 8 years ago
- Subject changed from Repository for MongoDB can not be discovered to Repository for MongoDB can not be discovered
- Translation missing: en.field_release set to 114
Updated by Justin Sherrill about 3 years ago
- Status changed from New to Rejected
- Triaged set to No
Katello 4.0 has dropped pulp 2 and mongo, so this issue is no longer relevant.
Actions