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.

Description of problem:
User is unable to set CA renewal master using `ipa config-mod --ca-renewal-master-server` 

# ipa config-mod --ca-renewal-master-server `hostname`
ipa: ERROR: invalid 'ca_renewal_master_server': must be enabled only on a single master

Whereas, following command works fine 

# ipa config-show | grep renewal
  IPA CA renewal master: master1.testrelm.test
# ipa-csreplica-manage set-renewal-master
Directory Manager password:

replica1.testrelm.test is now the renewal master
# ipa config-show | grep renewal
  IPA CA renewal master: replica1.testrelm.test

Version-Release number of selected component (if applicable):
ipa-server-4.5.0-21.el7_4.1.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install IPA Master and Replica
2. Install CA on Replica
3. ipa config-mod --ca-renewal-master-server `hostname` on replica

Actual results:
config-mod Command fails to set ca renewal master server, but csreplica-manage command successfully sets ca renewal master.

Expected results:
Both command should set ca renewal master server.

Additional info:
Documentation here - https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/moving-crl-gen-old.html 
should discuss `config-mod` command as well.

In ipaserver/servroles.py, l 421:

class SingleValuedServerAttribute(ServerAttribute):
    """
    Base class for server attributes that are forced to be single valued

    this means that `get` method will return a one-element list, and `set`
    method will accept only one-element list
    """

    def set(self, api_instance, masters):
        if len(masters) > 1:
            raise errors.ValidationError(
                name=self.attr_name,
                error=_("must be enabled only on a single master"))


The issue is that the set() method is called with masters = a unicode, and len(masters) returns the length of the string, not the number of elements in a list.

Probably a regression introduced with commit bddb90f38a3505a2768862d2f814c5e749a7dcde
Allow for multivalued server attributes

Upstream ticket:
https://pagure.io/freeipa/issue/7120

Fixed upstream
master:
https://pagure.io/freeipa/c/a077c705fe211716e967faf7a12ed738bc5261e9
ipa-4-6:
https://pagure.io/freeipa/c/5f79504d3dc29891802c6d7eeaa465c298b7e417
ipa-4-5:
https://pagure.io/freeipa/c/770fb59637affc22c76256478b53bbe831b3ec88

Verified on ipa-server-4.5.4-6.el7.x86_64

Created attachment 1364705 [details]
verification_steps

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-2018:0918