Bug 1480694 - Custom Repositories built with SHA1 checksums produce incorrect SHA256 repodata
Custom Repositories built with SHA1 checksums produce incorrect SHA256 repodata
Status: POST
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Repositories (Show other bugs)
6.2.10
Unspecified Unspecified
medium Severity urgent (vote)
: Unspecified
: --
Assigned To: satellite6-bugs
Katello QA List
: PrioBumpGSS, Triaged
Depends On: 1466950
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-11 13:43 EDT by Justin Sherrill
Modified: 2018-02-13 17:04 EST (History)
14 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1466950
Environment:
Last Closed:
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)
el6 hotfix (8.14 MB, application/x-tar)
2017-08-16 09:55 EDT, Justin Sherrill
no flags Details
el7 hotfix (7.55 MB, application/x-tar)
2017-08-16 09:56 EDT, Justin Sherrill
no flags Details
RHEL7 Hotfix for Sat 6.2.14 (7.56 MB, application/x-tar)
2018-02-13 17:00 EST, Brad Buckingham
no flags Details
RHEL6 Hotfix for Sat 6.2.14 (8.15 MB, application/x-tar)
2018-02-13 17:01 EST, Brad Buckingham
no flags Details

  None (edit)
Comment 2 pulp-infra@redhat.com 2017-08-11 16:34:44 EDT
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 3 pulp-infra@redhat.com 2017-08-11 16:34:48 EDT
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 4 pulp-infra@redhat.com 2017-08-11 17:07:34 EDT
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 5 Justin Sherrill 2017-08-16 09:55 EDT
Created attachment 1314157 [details]
el6 hotfix
Comment 6 Justin Sherrill 2017-08-16 09:56 EDT
Created attachment 1314158 [details]
el7 hotfix
Comment 7 Bernie Hoefer 2017-08-16 10:47:23 EDT
(In reply to Justin Sherrill from comment #6)
===
> Created attachment 1314158 [details]
> el7 hotfix
===

Thanks, Justin!  Quick question:  after the customer updates to the tfm-rubygem-katello packages you put in the tar file, does he need to re-run satellite-installer or restart the services?  Do these need installed on both the satellite and capsule?  Thanks!
Comment 8 Bernie Hoefer 2017-08-16 10:59:59 EDT
I just looked at a co-worker's capsule server and see those packages are not present; so I presume the hot fix ones only need installed on the satellite.

Still, please let me know if satellite-installer needs re-run or if the services just need restarted.  Thanks!
Comment 9 Justin Sherrill 2017-08-17 14:38:16 EDT
HOTFIX INSTRUCTIONS:

1) Download the hotfix tarball of your choice from this bz

2) untar the tar file

3) Install hotfix RPMs:

# yum update tfm-rubygem-katell-*

4) Restart services:

# katello-service restart
Comment 10 Justin Sherrill 2017-08-17 14:38:43 EDT
Hotfix released with instructions!
Comment 16 Brad Buckingham 2018-02-13 17:00 EST
Created attachment 1395675 [details]
RHEL7 Hotfix for Sat 6.2.14
Comment 17 Brad Buckingham 2018-02-13 17:01 EST
Created attachment 1395676 [details]
RHEL6 Hotfix for Sat 6.2.14
Comment 18 Brad Buckingham 2018-02-13 17:04:30 EST
HOTFIX INSTRUCTIONS FOR SAT 6.2.14:

1) Download the hotfix tarball of your choice from this bz
   (e.g. "RHEL7 Hotfix for Sat 6.2.14" or "RHEL6 Hotfix for Sat 6.2.14")

2) untar the tar file

3) Install hotfix RPMs:

(e.g. for RHEL7)
# yum update tfm-rubygem-katello-3.0.0.162-3_HF1466950.el7sat.noarch.rpm tfm-rubygem-katello_ostree-3.0.0.162-3_HF1466950.el7sat.noarch.rpm

4) Restart services:

# katello-service restart

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