Description of problem:
Sudo Module
sudocrule added while adding rule with hostcategory=all and a specific host at the same time.

Version-Release number of selected component (if applicable):
ansible-freeipa-0.1.8-3.el8.noarch

Steps to Reproduce:
##On Server##
Actual results:
[root@master ~]# ipa sudorule-show Newsudo_rule
ipa: ERROR: Newsudo_rule: sudo rule not found

##On Controller##
[root@ansible ~]# cat sudoruleadd.yaml
---
- name: Playbook
  hosts: ipaserver
  become: true
 
  tasks:
  - name: Get Domain from the server name
    set_fact:
      ipaserver_domain: "{{ groups.ipaserver[0].split('.')[1:] | join ('.') }}"
 
  - ipasudorule:
      ipaadmin_password: Secret.123
      name: Newsudo_rule
      description: sudo rule
      host: "{{ 'mytesthbachost2.' + ipaserver_domain }}"
      hostcategory: "all"

root@ansible ~]# ansible-playbook -vv -i inventory/host.hosts sudoruleadd.yaml
ansible-playbook 2.9.6
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.6/site-packages/ansible
  executable location = /usr/bin/ansible-playbook
  python version = 3.6.8 (default, Dec  5 2019, 15:45:45) [GCC 8.3.1 20191121 (Red Hat 8.3.1-5)]
Using /etc/ansible/ansible.cfg as config file

PLAYBOOK: sudoruleadd.yaml **************************************************************************************************
1 plays in sudoruleadd.yaml

PLAY [Playbook] *************************************************************************************************************

TASK [Gathering Facts] ******************************************************************************************************
task path: /root/sudoruleadd.yaml:2
ok: [master.ipadomain.test]
META: ran handlers

TASK [Get Domain from server name] ******************************************************************************************
task path: /root/sudoruleadd.yaml:7
ok: [master.ipadomain.test] => {"ansible_facts": {"ipaserver_domain": "ipadomain.test"}, "changed": false}

TASK [ipasudorule] **********************************************************************************************************
task path: /root/sudoruleadd.yaml:11
fatal: [master.ipadomain.test]: FAILED! => {"changed": false, "msg": "sudorule_add_host: Newsudo_rule: hosts cannot be added when host category='all'"}

PLAY RECAP ******************************************************************************************************************
master.ipadomain.test      : ok=2    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0 

##On Server##
[root@master ~]# ipa sudorule-del Newsudo_rule
--------------------------------
Deleted Sudo Rule "Newsudo_rule"
--------------------------------
[root@master ~]# ipa sudorule-show Newsudo_rule
  Rule name: Newsudo_rule
  Description: sudo rule
  Enabled: TRUE
  Host category: all

Actual results:
SUDO rule added after the playbook failed.

Expected results:
Sudo rule should not add if the following command is failing.


Additional info:
Noticed the same behavior with the below variables
 - usercategory: 'all'
 - servicecategory: 'all'