Bug 1463625

Summary: Fail to create an instance with containerized compute
Product: Red Hat OpenStack Reporter: Jean-Francois Saucier <jsaucier>
Component: openstack-novaAssignee: Eoghan Glynn <eglynn>
Status: CLOSED DUPLICATE QA Contact: Joe H. Rahme <jhakimra>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 12.0 (Pike)CC: berrange, dasmith, eglynn, kchamart, sbauza, sferdjao, sgordon, srevivo, svanders, 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: 2017-06-23 09:26:20 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:
Attachments:
Description Flags
nova-compute log from the compute none

Description Jean-Francois Saucier 2017-06-21 11:18:21 UTC
Created attachment 1290022 [details]
nova-compute log from the compute

Description of problem:

I build a containerized OSP-12 deployment (1 controller, 1 compute) using the latest 12 rhos-release yesterday (2017-06-19.1 branch). My cluster seems to run fine but when I try to create an instance, it fail with the error : "No valid host was found. There are not enough hosts available."

However, the real error on the computer node seems to be : "libvirt:  error : Unable to move /dev/log mount to /var/run/libvirt/qemu/instance-00000001.log: No such file or directory"


Version-Release number of selected component (if applicable):

openstack-nova-common-16.0.0-0.20170609171025.el7ost.noarch
python-novaclient-9.0.0-0.20170609003607.7585703.el7ost.noarch


How reproducible:

Everytime I try to create or launch an instance.


Steps to Reproduce:
1. Install a containerized deployment using the latest 12 rhos-release
2. Try to create an instance


Actual results:

The instance creation fail.


Expected results:

The instance start normally.

Comment 1 Sven Anderson 2017-06-23 09:26:20 UTC

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