Red Hat Bugzilla – Bug 1612057
[Deployment] Latest 8.3.0-2 opendaylight RPM fails with because controller for switches is not set
Last modified: 2018-10-18 03:24:47 EDT
Created attachment 1472957 [details] karaf.log Description of problem: With latest 8.3.0-2 ODL rpm, Overcloud deployment is failing in Step5 with overcloud.AllNodesDeploySteps.1029pComputeDeployment_Step5.14: resource_type: OS::Heat::StructuredDeployment physical_resource_id: be77f177-610c-45d2-9939-b075fea7e4a7 status: CREATE_FAILED status_reason: | Error: resources[14]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2 deploy_stdout: | ... "Warning: ModuleLoader: module 'neutron' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules" , "ovs-vsctl: no bridge named br-int", "Error: Evaluation Error: Error while evaluating a Function Call, OF controller for OVS was never set by ODL at /etc/puppet/modules/tripleo/manifests/profile/base/neutron/plugins /ovs/opendaylight.pp:137:10 on node overcloud-1029pcompute-14.localdomain" ] } d/s CI job fails as well with the same reason. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Deploy ODL + OS with 8.3.0-2 ODL rpm Actual results: Deployment fails Expected results: Deployment should go through. Additional info:
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible. If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-". To add draft documentation text: * Select the documentation type from the "Doc Type" drop down field. * A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.
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/RHSA-2018:2598