Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • overcloud install fails for br-ex network

    Posted on

    Hi,

    I am having problems getting OSP10 based overcloud to install. the undercloud went in ok.

    the system I am installing on has 2 compute and one controller nodes. i have tried several configurations without any success.

    When I follow the troubleshooting instructions, I get down to the following

    [stack@ostack2-director templates]$ openstack software deployment show 6afe6d18-d52f-4da7-87fd-39a877d4474c
    +---------------+--------------------------------------------------------+
    | Field | Value |
    +---------------+--------------------------------------------------------+
    | id | 6afe6d18-d52f-4da7-87fd-39a877d4474c |
    | server_id | 7e6bf1dc-4642-41fb-b062-19166f39c8e8 |
    | config_id | 1c071dc5-4bc2-434c-a880-a409f4ee5a8e |
    | creation_time | 2017-10-06T16:46:03Z |
    | updated_time | |
    | status | IN_PROGRESS |
    | status_reason | Deploy data available |
    | input_values | {u'interface_name': u'nic1', u'bridge_name': u'br-ex'} |
    | action | CREATE |
    +---------------+--------------------------------------------------------+

    I have br-ex defined on the controller and compute yaml files and have mapped in the network-environment file. The curious thing is that br-ex is part of an ovs-bridge that uses interface ens3f1 as the uplink, not nic1.

    any clues where nic1 is coming from and why the correct nic is not being used?

    I have included the two nic config files and the enviroment yaml files if that can give someone any clues. If there is any additional logs/data, please let me know.

    one additional piece of data from the overcloud install log

    [stack@ostack2-director ~]$ grep -i fail overcloud_install.log
    2017-10-06 16:53:47Z [overcloud.AllNodesValidationConfig]: CREATE_IN_PROGRESHeat Stack create failed.
    2017-10-06 17:29:59Z [overcloud.Compute]: CREATE_FAILED CREATE aborted
    2017-10-06 17:29:59Z [overcloud]: CREATE_FAILED Create timed out
    Stack overcloud CREATE_FAILED

    I know the last two lines are from the fact that the timeout is set to 60 mins.. the initial failure at 16:53 was about 21 mins into the stack create.

    Thanks in advance!

    Tim

    Attachments

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2026 Red Hat