← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1977490] [NEW] Tripleo Wallaby issue in template yaml generation

 

Public bug reported:

---------------------------------------------------------
High level description

I am trying to install Tripleo Wallaby for which I have successfully
installed the Undercloud Machine.

For deploying the overcloud I have followed the below document

https://docs.openstack.org/project-deploy-guide/tripleo-
docs/latest/features/custom_networks.html#custom-networks


------------------------------------------------------------
Issue

While running the Baremetal Provisioning Command:

openstack overcloud node provision   --stack overcloud --network-config
--output overcloud-baremetal-deployed.yaml overcloud-baremetal-
deploy.yaml

Connectivity to the overcloud gets lost after sometime when ansible
tries to apply the network config (with wrong syntax) and Overcloud
nodes become unavailable.


--------------------------------------------------------------
Sample Yaml

overcloud-baremetal-deploy.yaml


- name: Controller
  count: 3
  defaults:
    networks:
    - network: ctlplane
      vif: true
    - network: external
      subnet: external_subnet
    - network: internal_api
      subnet: internal_api_subnet
    - network: j3mgmt
      subnet: j3mgmt_subnet
    - network: oc_provisioning
      subnet: oc_provisioning_subnet
    network_config:
      template: /usr/share/ansible/roles/tripleo_network_config/templates/bonds_vlans/bonds_vlans.j2
      default_route_network:
      - external
  instances:
  - hostname: overcloud-controller-0
    name: node-a
    #provisioned: false
  - hostname: overcloud-controller-1
    name: node-b
    #provisioned: false
  - hostname: overcloud-controller-2
    name: node-c
    #provisioned: false

- name: Compute
  count: 1
  defaults:
    networks:
    - network: ctlplane
      vif: true
    - network: internal_api
      subnet: internal_api_subnet
    - network: j3mgmt
      subnet: j3mgmt_subnet
    network_config:
      template: /usr/share/ansible/roles/tripleo_network_config/templates/bonds_vlans/bonds_vlans.j2
  instances:
  - hostname: overcloud-novacompute-0
    name: node-d
    #provisioned: false

----------------------------------------------------------
Expected output

config.yaml should be generated correctly

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1977490

Title:
  Tripleo Wallaby issue in template yaml generation

Status in neutron:
  New

Bug description:
  ---------------------------------------------------------
  High level description

  I am trying to install Tripleo Wallaby for which I have successfully
  installed the Undercloud Machine.

  For deploying the overcloud I have followed the below document

  https://docs.openstack.org/project-deploy-guide/tripleo-
  docs/latest/features/custom_networks.html#custom-networks

  
  ------------------------------------------------------------
  Issue

  While running the Baremetal Provisioning Command:

  openstack overcloud node provision   --stack overcloud --network-
  config --output overcloud-baremetal-deployed.yaml overcloud-baremetal-
  deploy.yaml

  Connectivity to the overcloud gets lost after sometime when ansible
  tries to apply the network config (with wrong syntax) and Overcloud
  nodes become unavailable.

  
  --------------------------------------------------------------
  Sample Yaml

  overcloud-baremetal-deploy.yaml

  
  - name: Controller
    count: 3
    defaults:
      networks:
      - network: ctlplane
        vif: true
      - network: external
        subnet: external_subnet
      - network: internal_api
        subnet: internal_api_subnet
      - network: j3mgmt
        subnet: j3mgmt_subnet
      - network: oc_provisioning
        subnet: oc_provisioning_subnet
      network_config:
        template: /usr/share/ansible/roles/tripleo_network_config/templates/bonds_vlans/bonds_vlans.j2
        default_route_network:
        - external
    instances:
    - hostname: overcloud-controller-0
      name: node-a
      #provisioned: false
    - hostname: overcloud-controller-1
      name: node-b
      #provisioned: false
    - hostname: overcloud-controller-2
      name: node-c
      #provisioned: false

  - name: Compute
    count: 1
    defaults:
      networks:
      - network: ctlplane
        vif: true
      - network: internal_api
        subnet: internal_api_subnet
      - network: j3mgmt
        subnet: j3mgmt_subnet
      network_config:
        template: /usr/share/ansible/roles/tripleo_network_config/templates/bonds_vlans/bonds_vlans.j2
    instances:
    - hostname: overcloud-novacompute-0
      name: node-d
      #provisioned: false

  ----------------------------------------------------------
  Expected output

  config.yaml should be generated correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1977490/+subscriptions



Follow ups