RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1738218 - spausedd does not detect VMGuestLib
Summary: spausedd does not detect VMGuestLib
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: corosync
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Jan Friesse
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-06 14:38 UTC by Miroslav Lisik
Modified: 2020-11-14 07:42 UTC (History)
5 users (show)

Fixed In Version: corosync-3.0.2-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1737884
Environment:
Last Closed: 2019-11-05 21:12:28 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3435 0 None None None 2019-11-05 21:12:37 UTC

Description Miroslav Lisik 2019-08-06 14:38:20 UTC
This problem is also in rhel-8.1 for version corosync-3.0.2-2.el8 (spausedd).

+++ This bug was initially created as a clone of Bug #1737884 +++

Description of problem:

Daemon spausedd does not detect VMGuestLib and consequently does not set appropriate default for 'steal_threshold'.

From man spausedd(8):

 -t steal_threshold
             Set steal threshold percent. (default is 10 if kernel information is used and 100 if VMGuestLib is used).


Version-Release number of selected component (if applicable):
corosync-2.4.3-6.el7
spausedd-2.4.3-6.el7

How reproducible:
always on VMware platform

Steps to Reproduce:

1.1. Start spausedd
# systemctl start spausedd
2. check log messages



Actual results:
Aug  6 06:18:10 vmw600-node4-rhha spausedd[27578]: Running main poll loop with maximum timeout 200 and steal threshold 10%

Expected results:
threshold 100% on VMware


Additional info:

From discussion with developer it seems it is a problem with package compilation.

--- Additional comment from Jan Friesse on 2019-08-06 13:32:44 CEST ---

Proposed change in corosync.spec file:

@@ -178,13 +178,14 @@ make %{_smp_mflags}
 
 %if %{with spausedd}
 cd spausedd-%{spausedd_version}
+CFLAGS="${CFLAGS:-%{optflags}}" ; export CFLAGS
 make \
 %if %{defined use_vmguestlib}
     WITH_VMGUESTLIB=1 \
 %else
     WITH_VMGUESTLIB=0 \
 %endif
-    %{?_smp_mflags} CFLAGS="%{optflags}"
+    %{?_smp_mflags}
 %endif
 
 %install

Comment 3 Jan Friesse 2019-08-06 17:26:11 UTC
Luckily exception was not (yet) needed, so removing the exception?

Comment 6 errata-xmlrpc 2019-11-05 21:12:28 UTC
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:3435


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