fail_unable_to_start_service_octavia-interface

Fail Unable to start service octavia-interface

이강우 2024/10/01 05:25

kolla-ansible에서 octavia 배포중 아래와 같은 오류가 발생하는 경우가 있다.

TASK [octavia : Restart octavia-interface.service if required] *****************************************************************************************************************
fatal: [r9-control2]: FAILED! => {"changed": false, "msg": "Unable to start service octavia-interface: Job for octavia-interface.service failed because the control process exited with error code.\nSee \"systemctl status octavia-interface.service\" and \"journalctl -xeu octavia-interface.service\" for details.\n"}
fatal: [r9-control3]: FAILED! => {"changed": false, "msg": "Unable to start service octavia-interface: Job for octavia-interface.service failed because the control process exited with error code.\nSee \"systemctl status octavia-interface.service\" and \"journalctl -xeu octavia-interface.service\" for details.\n"}
fatal: [r9-control1]: FAILED! => {"changed": false, "msg": "Unable to start service octavia-interface: Job for octavia-interface.service failed because the control process exited with error code.\nSee \"systemctl status octavia-interface.service\" and \"journalctl -xeu octavia-interface.service\" for details.\n"}

PLAY RECAP *********************************************************************************************************************************************************************
localhost                  : ok=4    changed=0    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   
r9-compute1                : ok=59   changed=0    unreachable=0    failed=0    skipped=60   rescued=0    ignored=0   
r9-compute2                : ok=53   changed=0    unreachable=0    failed=0    skipped=60   rescued=0    ignored=0   
r9-control1                : ok=311  changed=27   unreachable=0    failed=1    skipped=254  rescued=0    ignored=0   
r9-control2                : ok=204  changed=7    unreachable=0    failed=1    skipped=242  rescued=0    ignored=0   
r9-control3                : ok=204  changed=7    unreachable=0    failed=1    skipped=242  rescued=0    ignored=0   

결론부터 말하자면 대상 노드에 dhclient명령어가 없기때문에 발생하는 오류이다.
노드의 /var/log/messages내용을 확인해보면 아래와 같다.

/var/log/messages
Oct  1 13:59:03 r9-control1 systemd[1]: Stopped Octavia Interface Creator.
Oct  1 13:59:03 r9-control1 systemd[1]: Starting Octavia Interface Creator...
Oct  1 13:59:03 r9-control1 systemd[201458]: octavia-interface.service: Failed to locate executable /sbin/dhclient: No such file or directory
Oct  1 13:59:03 r9-control1 systemd[201458]: octavia-interface.service: Failed at step EXEC spawning /sbin/dhclient: No such file or directory
Oct  1 13:59:03 r9-control1 systemd[1]: octavia-interface.service: Main process exited, code=exited, status=203/EXEC
Oct  1 13:59:03 r9-control1 systemd[1]: octavia-interface.service: Failed with result 'exit-code'.
Oct  1 13:59:03 r9-control1 systemd[1]: Failed to start Octavia Interface Creator.
Oct  1 13:59:03 r9-control1 systemd[1]: octavia-interface.service: Scheduled restart job, restart counter is at 5.
Oct  1 13:59:03 r9-control1 systemd[1]: Stopped Octavia Interface Creator.
Oct  1 13:59:03 r9-control1 systemd[1]: octavia-interface.service: Start request repeated too quickly.
Oct  1 13:59:03 r9-control1 systemd[1]: octavia-interface.service: Failed with result 'exit-code'.
Oct  1 13:59:03 r9-control1 systemd[1]: Failed to start Octavia Interface Creator.

로그 내용처럼 /sbin/dhclient 명령어가 없어 발생하는 오류이다.
해결법은 dhcp-client패키지를 설치하면 된다.

[root@r9-control1 log]# dnf -y install dhcp-client
로그인하면 댓글을 남길 수 있습니다.
  • fail_unable_to_start_service_octavia-interface.txt
  • 마지막으로 수정됨: 2024/10/01 05:25
  • 저자 koov