DevStack(OpenStack)环境下Ubuntu 22.04 LTS虚拟机systemd-resolved.service启动失败求助
DevStack(OpenStack)环境下Ubuntu 22.04 LTS虚拟机systemd-resolved.service启动失败求助
各位大佬好,我遇到了一个棘手的问题,想请大家帮忙排查下:
最近我在服务器上部署了DevStack(OpenStack发行版),并且上传了Ubuntu官方的Ubuntu Server 20.04 LTS和22.04 LTS云镜像。现在的情况是,20.04版本的虚拟机一切正常,systemd-resolved.service运行良好,能正常ping通外网;但22.04版本的虚拟机里,这个服务始终启动失败,执行sudo systemctl status systemd-resolved.service得到的报错信息如下:
ubuntu@test:~$ sudo systemctl status systemd-resolved.service × systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2023-04-05 14:53:46 UTC; 47s ago Docs: man:systemd-resolved.service(8) man:org.freedesktop.resolve1(5) https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 569 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=1/FAILURE) Main PID: 569 (code=exited, status=1/FAILURE) Error: 99 (Cannot assign requested address) CPU: 79ms Apr 05 14:53:46 test systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE Apr 05 14:53:46 test systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Apr 05 14:53:46 test systemd[1]: Failed to start Network Name Resolution. Apr 05 14:53:46 test systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Apr 05 14:53:46 test systemd[1]: Stopped Network Name Resolution. Apr 05 14:53:46 test systemd[1]: systemd-resolved.service: Start request repeated too quickly. Apr 05 14:53:46 test systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Apr 05 14:53:46 test systemd[1]: Failed to start Network Name Resolution.
我已经做了以下尝试,但都没能解决问题:
- 在本地主机用multipass创建了Ubuntu 22.04 LTS的虚拟机,
systemd-resolved.service启动完全正常;但把这个multipass生成的镜像上传到OpenStack后,还是出现同样的启动失败问题 - 在OpenStack里启动一台运行正常的Ubuntu 20.04 LTS虚拟机,通过
sudo do-release-upgrade -d升级到22.04版本后,systemd-resolved.service再次出现了相同的启动失败情况
我现在完全摸不着头绪,既缺乏DevStack相关的排查经验,对systemd的细节也不太熟悉,不知道该从哪里入手寻找线索。希望有经验的大佬能给点思路或者解决方案,万分感谢!
备注:内容来源于stack exchange,提问作者Michal16511
相关产品推荐
相关产品推荐

