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.

Bug 1899519

Summary: pcs will not accept non-ascii characters for pcmk_host_map
Product: Red Hat Enterprise Linux 7 Reporter: michal novacek <mnovacek>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: CLOSED WONTFIX QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.9CC: cluster-maint, idevat, mlisik, mpospisi, omular, tojeline
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-19 07:27:24 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:

Description michal novacek 2020-11-19 13:28:16 UTC
Description of problem:

With vm in VMware VCenter that contain non-ascii characters pcs is unable to create fencing for such machine as it does not accept such characters resulting in inability to use such vms as cluster nodes.

Version-Release number of selected component (if applicable):
pcs-0.9.169-3.el7_9.1.x86_64
pacemaker-1.1.23-1.el7.x86_64

How reproducible: always

Steps to Reproduce:
1. pcs stonith  create fence_vmware_rest fence_vmware_rest ... pcmk_host_map="vmware-beta-11.cluster-qe.lab.eng.brq.redhat.com:vmwar€-b€ta-11" ...

Actual results: python exception

Expected results: fencing added to cluster

Additional info:

$ pcs stonith  create fence_vmware_rest fence_vmware_rest ipaddr="vcenter-beta.cluster-qe.lab.eng.brq.redhat.com" login="fence_user" passwd="Password1." ssl_insecure="on" ssl="on" pcmk_host_check="static-list" pcmk_host_list="vmware-beta-11.cluster-qe.lab.eng.brq.redhat.com,vmware-beta-12.cluster-qe.lab.eng.brq.redhat.com" pcmk_host_map="vmware-beta-11.cluster-qe.lab.eng.brq.redhat.com:vmwar€-b€ta-11:vmware-beta-12.cluster-qe.lab.eng.brq.redhat.com:vmwar€-b€ta-12" delay=5
Traceback (most recent call last):
  File "/usr/sbin/pcs", line 9, in <module>
    load_entry_point('pcs==0.9.169', 'console_scripts', 'pcs')()
  File "/usr/lib/python2.7/site-packages/pcs/app.py", line 296, in main
    cmd_map[command](argv)
  File "/usr/lib/python2.7/site-packages/pcs/stonith.py", line 46, in stonith_cmd
    stonith_create(lib, argv_next, modifiers)
  File "/usr/lib/python2.7/site-packages/pcs/stonith.py", line 214, in stonith_create
    **settings
  File "/usr/lib/python2.7/site-packages/pcs/cli/common/lib_wrapper.py", line 97, in decorated_run
    return run_with_middleware(run, cli_env, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/pcs/cli/common/middleware.py", line 19, in run
    return next_in_line(env, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/pcs/cli/common/middleware.py", line 42, in apply
    result_of_next = next_in_line(env, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/pcs/cli/common/middleware.py", line 68, in apply
    result_of_next = next_in_line(env, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/pcs/cli/common/lib_wrapper.py", line 87, in run
    lib_call_result = run_library_command(lib_env, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/pcs/lib/commands/stonith.py", line 86, in create
    resource_type="stonith"
  File "/usr/lib/python2.7/site-packages/pcs/lib/cib/resource/primitive.py", line 113, in create
    operation_list=operation_list
  File "/usr/lib/python2.7/site-packages/pcs/lib/cib/resource/primitive.py", line 147, in append_new
    instance_attributes
  File "/usr/lib/python2.7/site-packages/pcs/lib/cib/nvpair.py", line 102, in append_new_nvset
    _append_new_nvpair(nvset_element, name, value, id_provider)
  File "/usr/lib/python2.7/site-packages/pcs/lib/cib/nvpair.py", line 30, in _append_new_nvpair
    value=value
  File "lxml.etree.pyx", line 2898, in lxml.etree.SubElement (src/lxml/lxml.etree.c:62059)
  File "apihelpers.pxi", line 191, in lxml.etree._makeSubElement (src/lxml/lxml.etree.c:14455)
  File "apihelpers.pxi", line 186, in lxml.etree._makeSubElement (src/lxml/lxml.etree.c:14379)
  File "apihelpers.pxi", line 264, in lxml.etree._initNodeAttributes (src/lxml/lxml.etree.c:15351)
  File "apihelpers.pxi", line 1335, in lxml.etree._utf8 (src/lxml/lxml.etree.c:24625)
ValueError: All strings must be XML compatible: Unicode or ASCII, no NULL bytes or control characters

Comment 5 RHEL Program Management 2022-05-19 07:27:24 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.