Bug 1551663
Summary: | Pcs should check for non-valid characters in corosync.conf keynames | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Radek Steiger <rsteiger> | ||||
Component: | pcs | Assignee: | Tomas Jelinek <tojeline> | ||||
Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 7.5 | CC: | cfeist, cluster-maint, cluster-qe, idevat, jpokorny, mmazoure, nhostako, omular, tojeline | ||||
Target Milestone: | rc | Keywords: | EasyFix | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | pcs-0.9.168-1.el7 | Doc Type: | Bug Fix | ||||
Doc Text: |
Cause:
User puts special characters into heuristics name when configuring quorum device.
Consequence:
The heuristics are ignored by corosync / qdevice.
Fix:
Make pcs report an error when special characters are used.
Result:
Pcs does not allow to set up heuristics in a way they are ignored by corosync / qdevice.
|
Story Points: | --- | ||||
Clone Of: | 1515193 | ||||||
: | 1679197 (view as bug list) | Environment: | |||||
Last Closed: | 2020-03-31 19:09:37 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Radek Steiger
2018-03-05 16:23:52 UTC
Created attachment 1570051 [details] proposed fix Test according to comment 0. After Fix: [kid76 ~] $ rpm -q pcs pcs-0.9.168-1.el7.x86_64 [kid76 ~] $ pcs quorum device add model net host="virt-139.cluster-qe.lab.eng.brq.redhat.com" algorithm="lms" heuristics mode="on" exec_čivava="/usr/bin/ping -c 1 127.0.0.1" Error: invalid heuristics option 'exec_čivava', exec_NAME may contain a-z A-Z 0-9 /_- characters only 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, 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-2020:0996 |