Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1772181

Summary: [Deployment][TLS everywhere] OC deployment fails at " Error: unable to exec into nova_compute: no container with name or ID nova_compute found"
Product: Red Hat OpenStack Reporter: Archit Modi <amodi>
Component: openstack-novaAssignee: OSP DFG:Compute <osp-dfg-compute>
Status: CLOSED DUPLICATE QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15.0 (Stein)CC: dasmith, eglynn, jagee, jhakimra, kchamart, michele, mschuppe, sbauza, sgordon, vromanso
Target Milestone: ---   
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: 2019-11-14 07:58:28 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 Archit Modi 2019-11-13 20:49:21 UTC
Description of problem: Deploying RHOS-15 with TLS everywhere fails at overcloud deployment on the metioned error

How reproducible: always

Steps to Reproduce:
1. Deploy RHOS-15 with freeipa node (and TLS everywhere) 
2. Deployment fails at overcloud deploy stage

Actual results:
TASK [Discovering nova hosts] **************************************************
Wednesday 13 November 2019  16:27:00 +0000 (0:00:00.160)       0:40:25.744 **** 
[DEPRECATION WARNING]: Distribution redhat 8.1 on host undercloud should use 
/usr/libexec/platform-python, but is using /usr/bin/python for backward 
compatibility with prior Ansible releases. A future Ansible release will 
default to using the discovered platform python for this host. See https://docs
.ansible.com/ansible/2.8/reference_appendices/interpreter_discovery.html for 
more information. This feature will be removed in version 2.12. Deprecation 
warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
fatal: [undercloud -> 192.168.24.46]: FAILED! => {"ansible_facts": {"discovered_interpreter_python": "/usr/bin/python"}, "changed": false, "cmd": ["podman", "exec", "nova_compute", "nova-manage", "cell_v2", "discover_hosts", "--by-service"], "delta": "0:00:00.094124", "end": "2019-11-13 16:27:01.403895", "msg": "non-zero return code", "rc": 125, "start": "2019-11-13 16:27:01.309771", "stderr": "Error: unable to exec into nova_compute: no container with name or ID nova_compute found: no such container", "stderr_lines": ["Error: unable to exec into nova_compute: no container with name or ID nova_compute found: no such container"], "stdout": "", "stdout_lines": []}

Expected results:
Deployment succeeded


Additional info:

Comment 3 Martin Schuppert 2019-11-14 07:58:28 UTC
The real error is:

        "<13>Nov 13 15:48:11 puppet-user: Error: More than one line in file '/etc/sysconfig/libvirtd' matches pattern 'LIBVIRTD_ARGS='",
        "<13>Nov 13 15:48:11 puppet-user: Error: /Stage[main]/Nova::Migration::Libvirt/File_line[/etc/sysconfig/libvirtd libvirtd args]/ensure: change from 'absent' to 'present' failed: More than one line in file '/etc/sysconfig/libvirtd' matches pattern 'LIBVIRTD_ARGS='",

Closing as a dupe of BZ1767154 . Feel free to reopen if you still see the issue with the fix from mentioned BZ

*** This bug has been marked as a duplicate of bug 1767154 ***