Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
There is no concept of 'transactions' and 'locking' in WBEM protocol and in CIM architecture.
We can provide voluntary locking, which is tracked upstream as https://fedorahosted.org/openlmi/ticket/81
The issue with LMI_Service instances mentioned in comment #0 is fixed in current master in upstream git (the fix will land in 7.1 as the package will be rebased).
But the missing locking mechanism is property of the CIM technologies. There is nothing much we can do in the providers. We could do some voluntary locking mechanism (discussed upstream in https://fedorahosted.org/openlmi/ticket/81) but that has not yet been decided.
For now, I'm closing this bug as NOTABUG, the locking mechanism won't be implemented in the near future. If there is some actual provider breakage in the concurrent access (like that one in comment #0), please fill a new bug.