Bug 1376538
Summary: | fencing: No allowance for spaces in pcmk_host_map values | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | John Ruemker <jruemker> |
Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
Severity: | low | Docs Contact: | Steven J. Levine <slevine> |
Priority: | medium | ||
Version: | 8.0 | CC: | cluster-maint, gfialova, kgaillot, mnovacek, msmazova, sbradley, slevine |
Target Milestone: | pre-dev-freeze | Keywords: | FutureFeature, Reopened |
Target Release: | 8.6 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | pacemaker-2.1.2-1.el8 | Doc Type: | Enhancement |
Doc Text: |
.Support for special characters inside `pcmk_host_map` values
The `pcmk_host_map` property now supports special characters inside `pcmk_host_map` values using a backslash (\) in front of the value. For example, you can specify `pcmk_host_map="node3:plug\ 1"` to include a space in the host alias.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-05-10 14:09:46 UTC | Type: | Enhancement |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | 2.1.2 |
Embargoed: |
Description
John Ruemker
2016-09-15 16:22:18 UTC
I don't have a great idea for how we could fix this without disrupting existing configurations. In my experience, most users prefer to use space as a delimiter over semi-colon, so if we start interpreting spaces differently, we're sure to cause problems. After that my best idea is to use a hack-job of a special character that signifies space in the alias. [[space]] or something like that. Not pretty, and definitely not intuitive (you'd have to just know about the alias for this character, and who reads manpages anymore?), but it'd be better than having no option at all. For the record, I'm not super keen on allowing characters out of the range of a-zA-Z0-0._- (basically the same as host names). If we add [[space]] we'd probably need [[colon]] and [[comma]] too :-( I'd prefer to document the restriction instead. Since pacemaker at the lowest level uses XML, I thought this might be possible using   in place of the space. However, pacemaker substitutes a space for that when reading and writing the CIB, so it is quickly lost, and is not treated any differently. I think the simplest approach would be to allow a backslash to mean that the next character is part of the text, and should have no special meaning to pacemaker. '\ ', '\:', and'\,' would handle the cases mentioned in Comment 2. I'll see what I can do with that. BTW, I could understand some users might want to use e.g. accented characters, too. I thought maybe using ñ or its equivalent Ñ would work as expected, since pacemaker doesn't use it as a separator, but it does not. But that's a different (and more complicated) question -- even if we had such a representation for characters, we'd still need a way to tell pacemaker to pass the character to the fence device rather than interpret it itself. This will not be ready in the 7.4 timeframe. Due to time constraints, this will not make 7.5 Bumping to RHEL 8.1 due to devel/QA capacity constraints Due to developer time constraints, this issue has been reported upstream, and this report will be closed. If developer time becomes available for it, this report will be reopened. Fixed upstream as of commit e95198f3 Verified as SanityOnly in pacemaker-2.1.2-2.el8 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 (pacemaker bug fix and enhancement update), 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-2022:1885 |