Bug 1394493 - extra repo in product 'Red Hat Enterprise Linux 7 Server for ARM (Kickstart)' with incorrect architecture
Summary: extra repo in product 'Red Hat Enterprise Linux 7 Server for ARM (Kickstart)'...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: releng
Version: 7.0
Hardware: aarch64
OS: Linux
medium
low
Target Milestone: pre-dev-freeze
: 7.6
Assignee: Jon Disnard
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1498541 1534323
TreeView+ depends on / blocked
 
Reported: 2016-11-12 15:30 UTC by Reartes Guillermo
Modified: 2018-09-04 14:27 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 14:27:37 UTC
Target Upstream Version:


Attachments (Terms of Use)
screenshot of the incorrect extra repo (28.35 KB, image/png)
2016-11-12 15:30 UTC, Reartes Guillermo
no flags Details

Description Reartes Guillermo 2016-11-12 15:30:45 UTC
Created attachment 1220027 [details]
screenshot of the incorrect extra repo

Description of problem:

The repository "Red Hat Enterprise Linux 7 Server for ARM Kickstart aarch64 7.3" has an extra repository entry:

* "Red Hat Enterprise Linux 7 Server for ARM Kickstart x86_64 7.3"

Please note the "x86_64".

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

How reproducible:
always

Steps to Reproduce:
1. go to red hat repositories, 
2. red hat enterprise linux server for arm
3. Red Hat Enterprise Linux 7 Server for ARM (Kickstart)
4. an extra repo is there.

Actual results:
This repo is listed: "Red Hat Enterprise Linux 7 Server for ARM Kickstart x86_64 7.3"


Expected results:
That repo should not be there.


Additional info:

Comment 1 Craig Donnelly 2017-09-21 17:23:46 UTC
Moving to RHEL rel-eng, as this is related to content-delivery of this product and not Satellite.

Comment 5 Yaakov Selkowitz 2018-01-15 01:27:17 UTC
Is this still an issue in 7.5 nightlies?

Comment 7 John Feeney 2018-03-01 17:37:53 UTC
I assume we still have this issue but it probably is more blatant. Can we get this resolved for 7.6, please.

Comment 8 Lubos Kocman 2018-05-29 07:51:48 UTC
Jaro please get in touch with delivery to resolve these

Lubos

Comment 10 Jaroslav Fedor 2018-06-22 14:10:15 UTC
Createad a CONTENT-DELIVERY ticket:
https://projects.engineering.redhat.com/browse/DELIVERY-4716

Because this is not a big priority, moving to Jon, please keep an eye on that jira. 

Thanks!

Comment 11 Jaroslav Fedor 2018-06-27 08:00:17 UTC
Jon, https://projects.engineering.redhat.com/browse/DELIVERY-4716 Jira was resolved! I feel it is safe to close the bug now.

Comment 13 John Feeney 2018-08-21 23:08:07 UTC
I see from comment #11 that this bugzilla was moved to MODIFIED and there is a comment to close. Can it be closed?

Comment 14 Jon Disnard 2018-09-04 14:27:37 UTC
sure, let it be closed.


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