tripleo

Openstack overcloud node provision fails "Failed to connect to the host via ssh: ssh: Could not resolve hostname" for a node which is undeployed using metalsmith undeploy command

Bug #1969356 reported by swogat pradhan on 2022-04-18

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	tripleo	New	Undecided	Unassigned

Bug Description

After running metalsmith undeploy <failed node>, when i run "openstack overcloud node provision --stack overcloud --network-config --overcloud-ssh-key /home/stack/sshkey/id_rsa --output overcloud-baremetal-deployed.yaml overcloud-baremetal-deploy.yaml"

the node provision process starts and fails after sometime in the growvols section:

NO MORE HOSTS LEFT *************************************************************

PLAY RECAP *********************************************************************
overcloud-novacompute-0 : ok=2 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
overcloud-novacompute-1 : ok=1 changed=0 unreachable=1 failed=0 skipped=0 rescued=0 ignored=0
overcloud-novacompute-2 : ok=2 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
overcloud-novacompute-3 : ok=2 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
overcloud-novacompute-5 : ok=1 changed=0 unreachable=1 failed=0 skipped=0 rescued=0 ignored=0
overcloud-novecompute-1 : ok=2 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0

In this current scenario i used metalsmith undeploy command for openstack-novacompute-5 and openstack-novacompute-1.

This issue should not occur as i have removed the 2 above mentioned compute nodes (novacompute5 and novacompute1) from the overcloud-baremetal-deploy.yaml file (which is being passed in openstack overcloud node provision command)

overcloud-baremetal-deploy.yaml:
- name: Controller
  count: 2
  defaults:
    networks:
    - network: ctlplane
      vif: true
    - network: external
      subnet: external_subnet
    - network: internal_api
      subnet: internal_api_subnet
    - network: storage
      subnet: storage_subnet
    - network: storage_mgmt
      subnet: storage_mgmt_subnet
    - network: tenant
      subnet: tenant_subnet
    network_config:
      template: /home/stack/templates/controller.j2
      default_route_network:
      - external
  instances:
    #- hostname: overcloud-controller-0
    #name: dc2-controller1
  - hostname: overcloud-controller-1
    name: dc2-controller2
    #- hostname: overcloud-controller-2
    #name: dc1-controller1
  - hostname: overcloud-controller-3
    name: dc1-controller2

- name: Compute
  count: 4
  defaults:
    networks:
    - network: ctlplane
      vif: true
    - network: internal_api
      subnet: internal_api_subnet
    - network: tenant
      subnet: tenant_subnet
    - network: storage
      subnet: storage_subnet
    network_config:
      template: /home/stack/templates/compute.j2
  instances:
  - hostname: overcloud-novacompute-0
    name: dc2-compute1
  - hostname: overcloud-novecompute-1
    name: dc2-compute2
  - hostname: overcloud-novacompute-2
    name: dc1-compute1
  - hostname: overcloud-novacompute-3
    name: dc1-compute2

- name: CephStorage
  count: 3
  defaults:
    networks:
    - network: ctlplane
      vif: true
    - network: internal_api
      subnet: internal_api_subnet
    - network: storage
      subnet: storage_subnet
    - network: storage_mgmt
      subnet: storage_mgmt_subnet
    network_config:
      template: /home/stack/templates/ceph-storage.j2
  instances:
  - hostname: overcloud-cephstorage-0
    name: dc2-ceph1
    # - hostname: overcloud-cephstorage-1
    # name: dc2-ceph2
  - hostname: overcloud-cephstorage-2
    name: dc1-ceph1
  - hostname: overcloud-cephstorage-3
    name: dc1-ceph2

I have also tried adding the failed nodes as mentioned below in the yaml file:
    - hostname: overcloud-novacompute-5
      name: dc2-compute3
      provisioned: false
    - hostname: overcloud-novacompute-1
      name: dc1-controller1
      provisioned: false

Still the issue persists.
When i try openstack overcloud node delete or unprovision i receive an output that says 'No nodes to unprovision'

Steps to Reproduce:
1. Install openstack tripleo for wallaby
2. Introspect the nodes
3. provision network using openstack overcloud network provision
4. provision node using openstack overcloud node provision (if any node fails or if you stop the command halfway follow the next step)
5. metalsmith undeploy <failed node> (metalsmith list should show deploying for that particular node)

Tags:

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.