Score:0

how openstack remove offline host node by kolla-ansible

us flag

As the title, I have an offline host node which include( compute node, control node and storage node), this host node was shutdown by incident and can't recovery to online, all services about that node was down and enable but can't set to disable.

So I can't remove the host by:

kolla-ansible -i multinode stop --yes-i-really-really-mean-it --limit node-17

it get this error:

TASK [Gather facts] ********************************************************************************************************************************************************************************************************************
fatal: [node-17]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host node-17 port 22: Connection timed out", "unreachable": true}

PLAY RECAP *****************************************************************************************************************************************************************************************************************************
node-17         : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0

How can I remove that offline host node? THX.

PS: Why I remove that offline host?

node-14(online)  : **manage node which kolla-ansible installed**; compute node, control node and storage node
node-15(online)  : compute node, control node and storage node
node-17(offline) : compute node, control node and storage node
osc99  (adding)  : compute node, control node and storage node

Because when I deploy a new host(osc99) with (the multinode file had comment the node-17 line):

kolla-ansible -i multinode deploy --limit osc99

kolla-ansible will report error:

TASK [keystone : include_tasks] ********************************************************************************************************************************************************************************************************
included: .../share/kolla-ansible/ansible/roles/keystone/tasks/init_fernet.yml for osc99

TASK [keystone : Waiting for Keystone SSH port to be UP] *******************************************************************************************************************************************************************************
ok: [osc99]

TASK [keystone : Initialise fernet key authentication] *********************************************************************************************************************************************************************************
ok: [osc99 -> node-14]

TASK [keystone : Run key distribution] *************************************************************************************************************************************************************************************************
fatal: [osc99 -> node-14]: FAILED! => {"changed": true, "cmd": ["docker", "exec", "-t", "keystone_fernet", "/usr/bin/fernet-push.sh"], "delta": "0:00:04.006900", "end": "2021-07-12 10:14:05.217609", "msg": "non-zero return code", "rc": 255, "start": "2021-07-12 10:14:01.210709", "stderr": "", "stderr_lines": [], "stdout": "Warning: Permanently added '[node.15]:8023' (ECDSA) to the list of known hosts.\r\r\nssh: connect to host node.17 port 8023: No route to host\r\r\nrsync: connection unexpectedly closed (0 bytes received so far) [sender]\r\nrsync error: unexplained error (code 255) at io.c(235) [sender=3.1.2]", "stdout_lines": ["Warning: Permanently added '[node.15]:8023' (ECDSA) to the list of known hosts.", "", "ssh: connect to host node.17 port 8023: No route to host", "", "rsync: connection unexpectedly closed (0 bytes received so far) [sender]", "rsync error: unexplained error (code 255) at io.c(235) [sender=3.1.2]"]}

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

PLAY RECAP *****************************************************************************************************************************************************************************************************************************
osc99                      : ok=120  changed=55   unreachable=0    failed=1    skipped=31   rescued=0    ignored=1 

How could I fixed this error, this is the main point whether or not I can remove the offline host.

Maybe I could fixed that by change the init_fernet.yml file:

node-14:~$ cat .../share/kolla-ansible/ansible/roles/keystone/tasks/init_fernet.yml
---
- name: Waiting for Keystone SSH port to be UP
  wait_for:
    host: "{{ api_interface_address }}"
    port: "{{ keystone_ssh_port }}"
    connect_timeout: 1
  register: check_keystone_ssh_port
  until: check_keystone_ssh_port is success
  retries: 10
  delay: 5

- name: Initialise fernet key authentication
  become: true
  command: "docker exec -t keystone_fernet kolla_keystone_bootstrap {{ keystone_username }} {{ keystone_groupname }}"
  register: fernet_create
  changed_when: fernet_create.stdout.find('localhost | SUCCESS => ') != -1 and (fernet_create.stdout.split('localhost | SUCCESS => ')[1]|from_json).changed
  until: fernet_create.stdout.split()[2] == 'SUCCESS' or fernet_create.stdout.find('Key repository is already initialized') != -1
  retries: 10
  delay: 5
  run_once: True
  delegate_to: "{{ groups['keystone'][0] }}"

- name: Run key distribution
  become: true
  command: docker exec -t keystone_fernet /usr/bin/fernet-push.sh
  run_once: True
  delegate_to: "{{ groups['keystone'][0] }}"

by change the delegate_to: "{{ groups['keystone'][0] }} at the line ? But I can't implement that, anyone can help? THX.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.