Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1360939 - Putting repo_gpgcheck=1 into yum.conf causes 404 Errors
Putting repo_gpgcheck=1 into yum.conf causes 404 Errors
Status: CLOSED DEFERRED
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: releng (Show other bugs)
7.2
x86_64 Linux
medium Severity medium
: rc
: ---
Assigned To: Lubos Kocman
Release Test Team
: Reopened
: 1494234 (view as bug list)
Depends On:
Blocks: 1298243
  Show dependency treegraph
 
Reported: 2016-07-27 19:05 EDT by Ashlee Burch
Modified: 2018-09-10 11:15 EDT (History)
21 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-02-02 08:44:58 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Article) 2850911 None None None 2018-05-14 12:00 EDT

  None (edit)
Description Ashlee Burch 2016-07-27 19:05:26 EDT
Description of problem:
Putting repo_gpgcheck=1 into yum.conf causes the following error:

https://cdn.redhat.com/content/dist/rhel/server/7/7.2/x84_64/os/repodata/repomd.xml.asc: [Errno 14] HTTPS Error 404 - Not Found


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

RHEL 7.2
Yum version: 3.4.3

How reproducible:
Every time

Steps to Reproduce:
1.Edit yum.conf and add repo_gpgcheck=1; save
2.Run yum command; yum repolist


Actual results:
https://cdn.redhat.com/content/dist/rhel/server/7/7.2/x84_64/os/repodata/repomd.xml.asc: [Errno 14] HTTPS Error 404 - Not Found

Expected results:
gpgcheck on repo succeeds

Additional info:

It doesn't appear that we provide a gpgcheck for our repos, is this expected behavior? 

This variable is in the man yum.conf
Comment 2 Valentina Mukhamedzhanova 2016-09-20 06:11:47 EDT
This is not a bug in yum, moving to releng.
Comment 10 Lubos Kocman 2017-02-02 04:28:46 EST
Hello,

this particular repository has reached END OF LIFE. As far as RHEL-7.2 goes, please use relevant update stream (EUS/AUS). Y-stream repository will stay as it is, as far as I'm aware this doesn't happen in 7.3

Lubos
Comment 12 Lubos Kocman 2017-02-02 06:16:22 EST
Ah okay, so this is a request to support signed repomd.xml. 

I'm afraid we don't play to introduce this feature in nearest time. It would be best to open it against Satellite-6 to be honest. We don't really have strong business driver unless any satellite uses it. Also satellite 6 does use same tool (pulp) for repo management as cdn.redhat.com 

Changing from won't fix to can't fix. and proposing to open request against satellite 6.


Lubos
Comment 16 Lubos Kocman 2017-02-02 08:44:58 EST
As previously stated, rel-eng doesn't own tool which is generating repodata. That makes it impossible for us to fix within team.

Here's clone of this bug opened against CONTENT DELIVERY team. If you insist that DevOps should own it rather than Satellite 6 (who uses same tool internally as we use for CDN) then here yo go.

Unfortunately they don't use bugzilla. I still believe that Sat6 / pulp component would get more luck in fixing this.

https://projects.engineering.redhat.com/browse/DELIVERY-2451


Closing in favour of DELIVERY-2451. I'm not letting this particular bug open since there is nothing rel-eng can do about it.
Comment 18 Marek Haicman 2017-09-21 16:56:07 EDT
*** Bug 1494234 has been marked as a duplicate of this bug. ***

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