Bug 1281359
Summary: | [RFE] pcs does not support resource templates in CIB | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Tomas Jelinek <tojeline> |
Component: | pcs | Assignee: | Tomas Jelinek <tojeline> |
Status: | CLOSED MIGRATED | QA Contact: | cluster-qe <cluster-qe> |
Severity: | unspecified | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | cluster-maint, idevat, kgaillot, mlisik, mpospisi, nwahl, omular, tojeline |
Target Milestone: | rc | Keywords: | FutureFeature, MigratedToJIRA, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-09-22 18:19:07 UTC | Type: | Story |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tomas Jelinek
2015-11-12 11:38:49 UTC
This currently prevents "clufter ccs2pcscmd" emitting pcs commands of how shared fence devices are encoded in CIB during the conversion process right now (not that it cannot be changed, but it is inconvenient at the very least). *** Bug 1513538 has been marked as a duplicate of this bug. *** Similarly to [bug 1281358 comment 2], this could be worked around using appropriate (currently non-existent) switch to cibadmin until there's a proper support delivered in pcs. Note that unline id-refs, templates are first-class concept, substantially easier to present to the users. Re [comment 1]: One of the options is to implement "template" exploding in XSLT, which could then be reused as a filter in clufter easily, so if the target pcs would be the one that doesn't resolve this bug yet, it would resort to using that filter on the path from CIB to pcs commands. Templates _do_ get used -- as opposed to other syntanctic extensions (extravagance); see the conclusion of the recent upstream community survey (not very representative but at least some backing numbers): https://lists.clusterlabs.org/pipermail/users/2018-June/015165.html 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. 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. |