This module requires libsemanage-python support

[mbruzek]

Is this a BUG REPORT or a FEATURE REQUEST ? (choose one): BUG REPORT

BUG REPORT INFO

Environment

• Cloud provider: OpenStack

• OS details (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):

      "Linux 3.10.0-737.el7.x86_64 x86_64", 
      "NAME=\"Red Hat Enterprise Linux Server\"", 
      "VERSION=\"7.4 (Maipo)\"", 
      "ID=\"rhel\"", 
      "ID_LIKE=\"fedora\"", 
      "VARIANT=\"Server\"", 
      "VARIANT_ID=\"server\"", 
      "VERSION_ID=\"7.4\"", 
      "PRETTY_NAME=\"Red Hat Enterprise Linux Server 7.4 (Maipo)\"", 
      "ANSI_COLOR=\"0;31\"", 
      "CPE_NAME=\"cpe:/o:redhat:enterprise_linux:7.4:GA:server\"", 
      "HOME_URL=\"https://www.redhat.com/\"", 
      "BUG_REPORT_URL=\"https://bugzilla.redhat.com/\"", 
      "", 
      "REDHAT_BUGZILLA_PRODUCT=\"Red Hat Enterprise Linux 7\"", 
      "REDHAT_BUGZILLA_PRODUCT_VERSION=7.4", 
      "REDHAT_SUPPORT_PRODUCT=\"Red Hat Enterprise Linux\"", 
      "REDHAT_SUPPORT_PRODUCT_VERSION=\"7.4\""

• Version of Ansible (ansible --version): 2.3.2.0

• Version of Jinja (pip freeze | grep -i jinja): 2.7.2

• Version of Shade (pip freeze | grep -i shade): 1.24.0

• The openstack-ansible-contrib version (commit) (git rev-parse --short HEAD): bb04b7b

Copy of inventory files and custom variables used (please omit your secrets!):

Command used to invoke ansible:
source /home/cloud-user/keystonerc; ansible-playbook -vvv openshift-ansible-contrib/playbooks/provisioning/openstack/provision.yaml 2>&1 > openstack_provision_log.txt

Output of ansible run:

TASK [infra-ansible/roles/dns-server : Configure SELinux] ***************************************************************************************************************************
task path: /home/cloud-user/openshift-ansible-contrib/roles/infra-ansible/roles/dns-server/tasks/prereq.yml:62                                                                       
Thursday 19 October 2017  16:57:36 -0400 (0:00:00.160)       0:04:52.097 ******                                                                                                      
Using module file /usr/lib/python2.7/site-packages/ansible/modules/system/seboolean.py                                                                                               
<172.21.0.119> ESTABLISH SSH CONNECTION FOR USER: openshift                                                                                                                          
<172.21.0.119> SSH: EXEC ssh -o ControlMaster=auto -o ControlPersist=900s -o GSSAPIAuthentication=no -o StrictHostKeyChecking=no -o 'IdentityFile="/home/cloud-user/.ssh/id_rsa"' -o 
KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=openshift -o ConnectTimeout=30 -o C
ontrolPath=/var/tmp/%h-%r 172.21.0.119 '/bin/sh -c '"'"'sudo -H -S -n -u root /bin/sh -c '"'"'"'"'"'"'"'"'echo BECOME-SUCCESS-mlnuwiciswefbcuyhowoqsfkgygzggct; /usr/bin/python'"'"'"
'"'"'"'"'"' && sleep 0'"'"''                                                                                                                                                         
<172.21.0.119> (1, '\n{"msg": "This module requires libsemanage-python support", "failed": true, "invocation": {"module_args": {"state": true, "persistent": true, "name": "named_wri
te_master_zones"}}}\n', '')                                                                                                                                                          
fatal: [dns-0.scale-ci.example.com]: FAILED! => {                                                                                                                                    
    "changed": false,                                                                                                                                                                
    "failed": true,                                                                                                                                                                  
    "invocation": {                                                                                                                                                                  
        "module_args": {                                                                                                                                                             
            "name": "named_write_master_zones",                                                                                                                                      
            "persistent": true,                                                                                                                                                      
            "state": true                                                                                                                                                            
        }                                                                                                                                                                            
    },                                                                                                                                                                               
    "msg": "This module requires libsemanage-python support"                                                                                                                         
}   

Anything else do we need to know:
This error is new to me. The script installs the "libselinux-python" package on the Ansible host, but not the "libsemanage-python" package. I can update my script but I do not know why this was not an issue before.

It looks to be a role that is installed in the ansible-galaxy command. Did something change over there? Is that a problem?

Thoughts? Ideas? Help?

[mbruzek]

I ran the automation scripts again today and got the same error as yesterday! However this run I updated the Ansible host to install libsemanage-python package. I think this is a serious problem preventing the provision.yaml script to complete. Would appreciate any help or advice on this.

[mbruzek]

This looks to be an issue with the infra-ansible project so an issue was created there as well: https://github.com/redhat-cop/infra-ansible/issues/89

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/openshift-ansible-contrib/issues/821#issuecomment-707929188): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.