Red Hat Bugzilla – Bug 1219574
[gui] resource optional arguments: quoted strings missing
Last modified: 2015-11-19 04:37:29 EST
Description of problem: Double quotes along with everything in-between are not visible in resource optional argument text fields. Eg. when additional_parameters option of mysql resource is set to: <nvpair id="my-instance_attributes-additional_parameters" name="additional_parameters" value="--bind-address="0.0.0.0""/> then the text field in pcs-gui contains just: --bind-address= Version-Release number of selected component (if applicable): pcs-0.9.137-13.el7.x86_64 How reproducible: always Steps to Reproduce: create resource with quotes in optional parameter Actual results: pcs-gui hides quotes and everything between them Expected results: show the same values as set in cib Additional info:
pcs cli shows the correct values: # pcs resource show my Resource: my (class=ocf provider=heartbeat type=mysql) Attributes: additional_parameters=--bind-address="0.0.0.0" config=/etc/oh-my.cnf Operations: start interval=0s timeout=120 (my-start-timeout-120) stop interval=0s timeout=120 (my-stop-timeout-120) monitor interval=20 timeout=30 (my-monitor-interval-20) monitor interval=10 role=Master timeout=30 (my-monitor-interval-10-role-Master) monitor interval=30 role=Slave timeout=30 (my-monitor-interval-30-role-Slave) promote interval=0s timeout=120 (my-promote-timeout-120) demote interval=0s timeout=120 (my-demote-timeout-120)
Cf. http://clusterlabs.org/pipermail/users/2015-May/000403.html
Fixed in a complex rewrite of the resources page in the web UI, patches in bz1189857 Before Fix: [root@rh71-node1 ~]# rpm -q pcs pcs-0.9.142-2.el7.x86_64 [root@rh71-node1:~]# pcs resource create dummy0 Dummy fake=quoted\ \"test\" Web UI shows an empty value of the fake attribute. After Fix: [root@rh71-node1:~]# rpm -q pcs pcs-0.9.143-1.el7.x86_64 [root@rh71-node1:~]# pcs resource create dummy0 Dummy fake=quoted\ \"test\" Web UI shows 'quoted "test"' as a value of the fake attribute.
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://rhn.redhat.com/errata/RHSA-2015-2290.html