Bug #30785
closed
Missed slash at the end of the repos
Added by jeschero please_edit_me over 4 years ago.
Updated over 4 years ago.
Description
Hello,
i have a bug/problem with the repo url on the clients.
My enviroment:
- Centos 7
- Foreman 2.1
- Katello 3.16
I have create a product for Centos 7 and repository for this. After this i have create a content-view and an activation-key for this product.
Now add i a client and the registration is successful, but i can't install any programms.
Night a few tests i have found the problem:
subscription-manager create this url: "https://<hostname>/pulp/repos/<domain>/Library/CentOS7_CV/custom/CentOS7/CentOS7_OS", but in a browser i get the message "404: Not Found".
But if a add a slash at the end of the url (https://<hostname>/pulp/repos/<domain>/Library/CentOS7_CV/custom/CentOS7/CentOS7_OS/) i can see the repos in the browser and add i the slash in the redhat.repo i can install programs and update the system.
After a "subscription-manager refresh/subscription-manager repos --list" the subscription-manager remove the slash und i can't install programs and update.
- Status changed from New to Need more information
Hey Jeschero,
Is this a fresh 3.16 install?
Samir Jha wrote:
Hey Jeschero,
Is this a fresh 3.16 install?
Hey Samir Jha,
yes, it is a fresh install.
- Status changed from Need more information to Ready For Testing
- Assignee set to Partha Aji
- Pull request https://github.com/Katello/katello/pull/8957 added
- Target version set to Katello 3.18.0
- Triaged changed from No to Yes
- Status changed from Ready For Testing to New
- Assignee deleted (
Partha Aji)
- Pull request deleted (
https://github.com/Katello/katello/pull/8957)
this had a pr accidentally associated with it, removing.
- Category set to Repositories
- Status changed from New to Rejected
- Target version changed from Katello 3.18.0 to Katello Recycle Bin
Hello! We're not able to reproduce this problem in Katello 3.18 which has just been released. Would you be able to upgrade (3.16 -> 3.17 -> 3.18) and see if this issue goes away? You may need a subscription-manager refresh/repos on your client to regenerate the redhat.repo file
If you are still hitting the problem please start a thread in our support forum: https://community.theforeman.org/c/support/10
Also available in: Atom
PDF