Bug 1730643
Summary: | REGRESSION: Egg 3.0.110 does not start on standard RHEL6/RHEL7 anymore due to cgroups check | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Peter Vreman <peter.vreman> |
Component: | insights-client | Assignee: | Richard Brantley <rbrantle> |
Status: | CLOSED ERRATA | QA Contact: | Jeff Needle <jneedle> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.10 | CC: | alng, ihands, jcrafts, klape, ktordeur, lphiri, pakotvan, pravisha |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-08-13 14:59:46 UTC | Type: | Bug |
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: | |||
Bug Blocks: | 1122832 |
Description
Peter Vreman
2019-07-17 09:10:59 UTC
My apologies, Peter. This was a complete and total process breakdown on our part in our coordination, testing, and release gating processes. We have reverted that change and a new egg will be available very soon (within the hour, it is propagating now). We will be addressing the QE failure and make immediate changes. This was inexcusable on our part. Peter please accept another apology from myself. This was a fix that was meant to address an issue where certain customers were experiencing a client failure when cgroups was partially disabled. This was a P1 for those customers. Obviously there was a bug and this affected a wider audience. The new egg is going out now but I believe you will have to manually force an egg update. Or tweak the setting and then the egg will update. Unfortunately this check happens before the egg is updated on the machine I believe. I think you do done of these: - https://access.redhat.com/articles/3747741 - rm /var/lib/insights - set ignore_cgroup=True in /etc/insights-client/insights-client.conf then run the client, then remove it Good to read that you have identified it as a missing part of the QE process. I am not really affected by it as i have auto_update=False. I had only to revert my last commit, because i thought the egg was successful as the first run (in which the new egg is downloaded) was successful Only then when looking for the output of a new feature to print the egg versions (based on a diff of the unpacked egg source code i found this feature was developed) i noticed it failed to start on RHEL6.10 Many Thanks for seeing the issue being picked up quickly. Confirmed egg 3.0.112 fixes the issue 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-2019:2474 |