Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1598067 - Need to have separate repositories for Puppet 4 for s390x architecture
Summary: Need to have separate repositories for Puppet 4 for s390x architecture
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Puppet
Version: 6.3.1
Hardware: s390x
OS: Linux
high
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-04 09:16 UTC by Gauravi
Modified: 2018-12-04 15:03 UTC (History)
5 users (show)

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


Attachments (Terms of Use)

Description Gauravi 2018-07-04 09:16:41 UTC
Description of problem:
Need to have repositories for Puppet 4 for s390x architecture.
At the moment there are no Puppet 4 repositories present for s390x architecture in Satellite.

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

How reproducible:
Always

Steps to Reproduce:
1. On Satellite web UI, navigate to 
Content >> Red Hat Repositories >> Red Hat Enterprise Linux Server >> Red Hat Satellite Tools 6.3 - Puppet 4 (for RHEL 7 Server) (RPMs) or Red Hat Satellite Tools 6.3 - Puppet 4 (for RHEL 6 Server) (RPMs) 

2. 

3.

Actual results:
There are repositories available only for x86_64 and not for s390x architecture

Expected results:
There should be new repositories available for s390x architecture.

Additional info:
Puppet (upstream) is providing packages for s390x architecture:
https://puppet.com/docs/puppet/4.6/release_notes_agent.html


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