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 2055028 - Cluster pacemaker complains about a resource which is not there
Summary: Cluster pacemaker complains about a resource which is not there
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: pacemaker
Version: CentOS Stream
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-16 09:04 UTC by lejeczek
Modified: 2022-04-19 16:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-19 16:27:47 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1493416 1 medium CLOSED Allow only OCF resources to be promotable or globally-unique clones 2023-05-12 00:40:21 UTC
Red Hat Issue Tracker RHELPLAN-112480 0 None None None 2022-02-16 09:15:05 UTC

Internal Links: 1493416

Description lejeczek 2022-02-16 09:04:25 UTC 
Description of problem:

Hi.
This is from: /var/log/pacemaker/pacemaker.log
...
Feb 16 09:01:30.977 swir.mine.private crm_resource        [3107823] (native_unpack) 	error: Resource GATEWAY:0 is of type systemd and therefore cannot be used as a promotable clone resource
Feb 16 09:01:30.977 swir.mine.private crm_resource        [3107823] (pe__create_clone_child) error: Failed unpacking resource GATEWAY
Feb 16 09:01:30.977 swir.mine.private crm_resource        [3107823] (unpack_resources) 	error: Ignoring <clone> resource 'GATEWAY-clone' because configuration is invalid
Feb 16 09:01:31.014 swir.mine.private crm_resource        [3107872] (clone_unpack) 	error: Ignoring promoted-max for GATEWAY-clone because anonymous clones support only one instance per node
Feb 16 09:01:31.014 swir.mine.private crm_resource        [3107872] (native_unpack) 	error: Resource GATEWAY:0 is of type systemd and therefore cannot be used as a promotable clone resource
Feb 16 09:01:31.014 swir.mine.private crm_resource        [3107872] (pe__create_clone_child) error: Failed unpacking resource GATEWAY

but, there is no such resource defined
-> $ pcs status --full | grep -i gateway
(blank)
-> $ pcs resource status | grep -i gateway
(blank)

thanks, L.


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

pacemaker-schemas-2.1.2-4.el9.noarch
pacemaker-libs-2.1.2-4.el9.x86_64
pacemaker-cluster-libs-2.1.2-4.el9.x86_64
pacemaker-cli-2.1.2-4.el9.x86_64
pacemaker-2.1.2-4.el9.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Tomas Jelinek 2022-02-16 12:25:43 UTC 
I think that this is due to a misconfiguration explained in the log you provided:
Resource GATEWAY:0 is of type systemd and therefore cannot be used as a promotable clone resource

Try running 'pcs resource config' and check if you can see the resource defined.
Comment 2 Ken Gaillot 2022-02-16 14:48:52 UTC 
Hi,

Can you attach the CIB (or a pcs cluster report) from the time this happened? If you look in the logs on the cluster nodes, find the closest "saving inputs" message before the relevant time, and it will show a file name that is the CIB from that moment.
Comment 3 lejeczek 2022-02-16 15:49:34 UTC 
Hi.
There is config for that resource, according to 'resource config' but the fact that 'cluster' does not show the resource in "usual" places made me decide it was a BZ.(no?)

regarding logs - perhaps a side "issue" - my /var/log/pacemaker/pacemaker.log grew freaking gigantic(>2GB with entries few months old), had to run logrotate manually and I wonder if logrotate's problem or ha-cluster's - I just thought I'd share here.

thanks, L.
Comment 4 Ken Gaillot 2022-02-17 16:00:28 UTC 
(In reply to lejeczek from comment #3)
> Hi.
> There is config for that resource, according to 'resource config' but the
> fact that 'cluster' does not show the resource in "usual" places made me
> decide it was a BZ.(no?)

I would expect it to show up in pcs status. If you have the CIB from when it didn't, we can check whether it's a bug.

> 
> regarding logs - perhaps a side "issue" - my
> /var/log/pacemaker/pacemaker.log grew freaking gigantic(>2GB with entries
> few months old), had to run logrotate manually and I wonder if logrotate's
> problem or ha-cluster's - I just thought I'd share here.
> 
> thanks, L.

The logrotate configuration in /etc/logrotate.d/pacemaker should rotate if the log hits 100MB (or at least weekly). The cluster doesn't deal with log rotation directly so it would be a logrotate issue.
Comment 5 Ken Gaillot 2022-04-19 16:27:47 UTC 
If this continues to be an issue, we can investigate further if we get a scheduler input with the issue
Note You need to log in before you can comment on or make changes to this bug.