This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 1447951 - crm_mon should give some indication when CIB is invalid
Summary: crm_mon should give some indication when CIB is invalid
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pacemaker
Version: 8.0
Hardware: All
OS: All
medium
medium
Target Milestone: pre-dev-freeze
: 8.10
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-04 09:59 UTC by Tomas Jelinek
Modified: 2023-09-22 18:16 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1462248 (view as bug list)
Environment:
Last Closed: 2023-09-22 18:16:51 UTC
Type: Enhancement
Target Upstream Version: 2.1.7
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Cluster Labs 5460 0 None None None 2020-12-01 16:25:13 UTC
Red Hat Issue Tracker   RHEL-7572 0 None Migrated None 2023-09-22 18:16:18 UTC
Red Hat Knowledge Base (Solution) 5361131 0 None None None 2020-09-01 04:42:35 UTC

Description Tomas Jelinek 2017-05-04 09:59:33 UTC 
Description of problem:
If a bundle resource is created without an IP address and a primitive resource is put inside the bundle, the bundle and the primitive is not shown in crm_mon and crm_mon --xml output. crm_verify shows why:
# crm_verify --live-check --verbose
   error: container_unpack:     Cannot control http-bundle inside dummy1
without either ip-range-start or control-port
   error: unpack_resources:     Failed unpacking bundle http-bundle
Errors found during check: config not valid

It would be nice to see these resources in crm_mon output.


Version-Release number of selected component (if applicable):
pacemaker-1.1.16-8.el7.x86_64


How reproducible:
always, easily


Steps to Reproduce:
1. create a bundle without an IP
2. put a primitive into the bundle


Actual results:
The bundle is missing in crm_mon and crm_mon --xml output. 


Expected results:
The bundle is present in crm_mon --xml output. Failed actions are shown in crm_mon output.


Additional info:
Expected results seem to be consistent with a misconfigured primitive (tested with a primitive based on a nonexistent resource agent).
Comment 2 Ken Gaillot 2017-05-04 14:42:41 UTC 
This will be considered in the 7.5 timeframe.
Comment 3 Andrew Beekhof 2017-05-05 00:09:23 UTC 
I agree invalid resources (not just bundles) should be in the xml output, I'm less sure about the normal output - unless as a "invalid resources detected, use crm_verify" line somewhere.

(Consider that it may be invalid because there is no id)

> Expected results seem to be consistent with a misconfigured primitive (tested with a primitive based on a nonexistent resource agent).

Thats a very different kind of invalid resource.

We would not want resources that cannot even be unpacked to show up in the "failed operations" section of the output.
Comment 4 Tomas Jelinek 2017-05-05 07:07:16 UTC 
This is the use case I am concerned about:
1) The user creates an invalid resource.
2) The user runs pcs status / crm_mon.
3) There is no sign of the resource created in step 1.
4) The user is confused.

Consider some time may pass between step 1 and two.

As long as crm_mon shows there is something wrong, by any means possible, I am fine with that.
Comment 6 Ken Gaillot 2017-08-29 21:21:30 UTC 
Due to a short time frame and limited capacity, this will not make 7.5.
Comment 8 Ken Gaillot 2019-01-15 17:34:55 UTC 
Bumping to 8.1 due to devel/QA capacity constraints
Comment 12 RHEL Program Management 2020-12-01 07:28:43 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 13 Ken Gaillot 2020-12-01 16:25:14 UTC 
An equivalent report has been filed upstream
Comment 15 RHEL Program Management 2023-09-22 18:15:40 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 16 RHEL Program Management 2023-09-22 18:16:51 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.