Bug 1781692
| Summary: | RHEL 7.7 PCP Upgrade issues [rhel-7.7.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | RAD team bot copy to z-stream <autobot-eus-copy> |
| Component: | pcp | Assignee: | Nathan Scott <nathans> |
| Status: | CLOSED ERRATA | QA Contact: | Jan Kurik <jkurik> |
| Severity: | urgent | Docs Contact: | Apurva Bhide <abhide> |
| Priority: | urgent | ||
| Version: | 7.7 | CC: | abhide, agerstmayr, chorn, cww, jhradile, jkurik, klaas, lberk, lkuprova, mcermak, mgoodwin, mkolar, mnewsome, msuchane, myllynen, nathans, ofalk, patrickm, peter.vreman, phil.randal, pholica, rhayden, sbroz, snejoshi, yuokada |
| Target Milestone: | rc | Keywords: | PrioBumpGSS, Reopened, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
.Error while upgrading `PCP` from the RHEL 7.6 version
When you upgrade the `pcp` packages from the RHEL 7.6 to the RHEL 7.7 version, `yum` returns the following error message:
----
Failed to resolve allow statement at /etc/selinux/targeted/tmp/modules/400/pcpupstream/cil:83
semodule: Failed!
----
It is safe to ignore this harmless message, which is caused by a bug in the RHEL 7.6 build of `pcp` and not by the updated package. The `PCP` functionality in RHEL 7.7 is not affected.
|
Story Points: | --- |
| Clone Of: | 1714101 | Environment: | |
| Last Closed: | 2020-02-04 19:32:19 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1714101 | ||
| Bug Blocks: | |||
|
Description
RAD team bot copy to z-stream
2019-12-10 12:18:18 UTC
*** Bug 1782198 has been marked as a duplicate of this bug. *** I wrote a "Known issue" section for RHEL-7.7.z release, describing the behaviour commented in 1781692#c6 (Comment #6 of this bug). However I do not know, how to make sure it appears in RN (and goes through a Content Services review). @jhradilek - is it something you can help me with, please ? Thank you, Jan! I am looping in Lenka Spackova who is responsible for the RHEL 7 Release Notes, but based on the flags, I believe this known issue should be on her list already. 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-2020:0376 |