Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1504736 - Please pcp zeroconf subrpm out of optional into base channels [NEEDINFO]
Please pcp zeroconf subrpm out of optional into base channels
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: releng (Show other bugs)
7.6
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Lubos Kocman
Release Test Team
Vladimír Slávik
:
: 1526603 (view as bug list)
Depends On:
Blocks: 1505884
  Show dependency treegraph
 
Reported: 2017-10-20 09:53 EDT by Lukas Berk
Modified: 2018-10-30 03:23 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-10-30 03:21:39 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
vslavik: needinfo? (lkocman)


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3014 None None None 2018-10-30 03:23 EDT

  None (edit)
Description Lukas Berk 2017-10-20 09:53:06 EDT
Description of problem:
pcp zeroconf subrpm is in the optional channel.  It is a supported package, but reduces it's usefulness when not in base channels with pcp.

Please apply this change to rhel7.4 and newer versions.

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

How reproducible:
Always

Steps to Reproduce:
1. Try to install pcp-zeroconf without optional channel enabled
2.
3.

Actual results:
Can't install the pcp-zeroconf package


Expected results:
Installed pcp-zeroconf package

Additional info:
Comment 2 Lukas Berk 2017-12-20 11:03:01 EST
Additional comments from Terry,

This package contains configuration tweaks and files to increase metrics
gathering frequency, several extended pmlogger configurations, as well as
automated pmie diagnosis, alerting and self-healing for the localhost.

It contains no code but essentially configurations that improve the user experience with the tooling.

Currently, this is shipped in the RHEL 7 optional channel where it is not as easily accessible to users and hinders usage of PCP.  All of the other pcp components are shipped in the base repository.

For each applicable RHEL Variant, move from optional to the corresponding base channel.

   from  rhel-7-{VARIANT}-optional-rpms
   to    rhel-7-{VARIANT}-rpms
Comment 4 Lukas Berk 2018-03-09 16:51:28 EST
*** Bug 1526603 has been marked as a duplicate of this bug. ***
Comment 5 Lukas Berk 2018-03-20 11:56:04 EDT
Seeing as this change has missed the 7.5 release, what is required to ensure it's in 7.6?  Would you like a similar patch as the one provided for 7.5?
Comment 6 Lubos Kocman 2018-05-24 03:42:03 EDT
Fine by me, once we'll have all acks we can simply do it.

Lubos
Comment 7 Lubos Kocman 2018-05-25 06:16:01 EDT
Hello

I added pcp-zeroconf as optional to @performance (available on all variants without specific arch restrictions). 

https://code.engineering.redhat.com/gerrit/gitweb?p=comps.git;a=commit;h=7fa138a568f2d9deb14359e66e711bb6a7575c5c

Lubos
Comment 9 Alexander Todorov 2018-07-09 08:23:23 EDT
 find -name "pcp-zeroconf*"
./Server/ppc64/os/Packages/pcp-zeroconf-4.1.0-2.el7.ppc64.rpm
./Server/ppc64le/os/Packages/pcp-zeroconf-4.1.0-2.el7.ppc64le.rpm
./Server/s390x/os/Packages/pcp-zeroconf-4.1.0-2.el7.s390x.rpm
./Server/x86_64/os/Packages/pcp-zeroconf-4.1.0-2.el7.x86_64.rpm
./Client/x86_64/os/Packages/pcp-zeroconf-4.1.0-2.el7.x86_64.rpm
./ComputeNode/x86_64/os/Packages/pcp-zeroconf-4.1.0-2.el7.x86_64.rpm
./Workstation/x86_64/os/Packages/pcp-zeroconf-4.1.0-2.el7.x86_64.rpm
Comment 12 errata-xmlrpc 2018-10-30 03:21:39 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3014

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