Red Hat Bugzilla – 1457204 – Deployment fails with Error: Invalid parameter transport on Class[Nova::Migration::Libvirt] at /var/lib/heat-config/heat-config-puppet/0793a63d-94b0-4a98-8cb1-70864e8d3b9f.pp:107 on node compute-1.localdomain\u001b[0m\n"
Deployment fails with Error: Invalid parameter transport on Class[Nova::Migration::Libvirt] at /var/lib/heat-config/heat-config-puppet/0793a63d-94b0-4a98-8cb1-70864e8d3b9f.pp:107 on node compute-1.localdomain\u001b[0m\n"
Description of problem:
Deployment fails with Error: Invalid parameter transport on Class[Nova::Migration::Libvirt] at /var/lib/heat-config/heat-config-puppet/0793a63d-94b0-4a98-8cb1-70864e8d3b9f.pp:107 on node compute-1.localdomain\u001b[0m\n"
Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-0.8.6-135.el7ost.noarch
openstack-puppet-modules-2015.1.8-53.el7ost.noarch
How reproducible:
100%
Steps to Reproduce:
1. Deploy OSP7 with 3 controllers, 2 computes, 3 ceph nodes
Actual results:
Deployment fails.
Expected results:
Successful deployment.
Additional info:
[stack@undercloud-0 ~]$ heat deployment-show 75eb3ae9-1262-4737-b222-9d02d6cdab1c
/usr/lib/python2.7/site-packages/requests/packages/urllib3/connection.py:251: SecurityWarning: Certificate has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/shazow/urllib3/issues/497 for details.)
SecurityWarning
/usr/lib/python2.7/site-packages/requests/packages/urllib3/connection.py:251: SecurityWarning: Certificate has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/shazow/urllib3/issues/497 for details.)
SecurityWarning
{
"status": "FAILED",
"server_id": "e81eb706-79a2-4129-b5da-e60cc567276a",
"config_id": "0793a63d-94b0-4a98-8cb1-70864e8d3b9f",
"output_values": {
"deploy_stdout": "",
"deploy_stderr": "Device \"br_isolated\" does not exist.\nDevice \"ovs_system\" does not exist.\n\u001b[1;31mWarning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::vncproxy::host'; class ::nova::vncproxy has not been evaluated\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::vncproxy::vncproxy_protocol'; class ::nova::vncproxy has not been evaluated\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::vncproxy::port'; class ::nova::vncproxy has not been evaluated\u001b[0m\n\u001b[1;31mWarning: Scope(Class[Nova::Vncproxy::Common]): Could not look up qualified variable '::nova::vncproxy::vncproxy_path'; class ::nova::vncproxy has not been evaluated\u001b[0m\n\u001b[1;31mError: Invalid parameter transport on Class[Nova::Migration::Libvirt] at /var/lib/heat-config/heat-config-puppet/0793a63d-94b0-4a98-8cb1-70864e8d3b9f.pp:107 on node compute-1.localdomain\nWrapped exception:\nInvalid parameter transport\u001b[0m\n\u001b[1;31mError: Invalid parameter transport on Class[Nova::Migration::Libvirt] at /var/lib/heat-config/heat-config-puppet/0793a63d-94b0-4a98-8cb1-70864e8d3b9f.pp:107 on node compute-1.localdomain\u001b[0m\n",
"deploy_status_code": 1
},
"creation_time": "2017-05-31T10:02:19Z",
"updated_time": "2017-05-31T10:02:57Z",
"input_values": {},
"action": "CREATE",
"status_reason": "deploy_status_code : Deployment exited with non-zero status code: 1",
"id": "75eb3ae9-1262-4737-b222-9d02d6cdab1c"
}
Just hit this while deploying osp8, took sosreports and put them here [1]. The deployment was a virtual 3 controller + 2 computes, with the latest (2017-05-30.1) available puddle.
[1] http://file.rdu.redhat.com/~rscarazz/BZ1457204/
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-2017:1538