Bug 2663 - [Anolis 23 Preview][x86_64/aarch64]nmcli 命令失效
Summary: [Anolis 23 Preview][x86_64/aarch64]nmcli 命令失效
Status: CLOSED BYDESIGN
Alias: None
Product: Anolis OS 23
Classification: Anolis OS
Component: BaseOS Packages (show other bugs) BaseOS Packages
Version: 23.0
Hardware: All Linux
: P3-Medium S3-normal
Target Milestone: ---
Assignee: xuchunmei
QA Contact: bolong_tbl
URL:
Whiteboard:
Keywords:
: 2662 (view as bug list)
Depends on:
Blocks:
 
Reported: 2022-10-30 23:04 UTC by yunmeng365524
Modified: 2022-11-01 20:29 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description yunmeng365524 2022-10-30 23:04:22 UTC
Description of problem:
nmcli 命令失效

Version-Release number of selected component (if applicable):
[root@iZbp14ub0x084rkaiux0krZ test-results]# cat /etc/os-release
NAME="Anolis OS"
VERSION="23"
ID="anolis"
VERSION_ID="23"
PLATFORM_ID="platform:an23"
PRETTY_NAME="Anolis OS 23"
ANSI_COLOR="0;31"
HOME_URL="https://openanolis.cn/"
BUG_REPORT_URL="https://bugzilla.openanolis.cn/"

[root@iZbp14ub0x084rkaiux0krZ test-results]# uname -a
Linux iZbp14ub0x084rkaiux0krZ 5.10.134-12.1.an23.x86_64 #1 SMP Thu Oct 13 11:38:24 CST 2022 x86_64 GNU/Linux

How reproducible:
安装NetworkManager的包后,执行nmcli 的命令如:nmcli -s 显示,但是报错。
[root@iZbp14ub0x084rkaiux0krZ test-results]# nmcli -s
Error: Could not create NMClient object: Could not connect: Connection refused.
[root@iZbp14ub0x084rkaiux0krZ test-results]# rpm -q NetworkManager
NetworkManager-1.36.2-2.an23.x86_64

Steps to Reproduce:
同上

Actual results:
命令执行失败

Expected results:
命令执行成功

Additional info:
早期的23版本执行OK:
[root@iZbp12nj7zzd2hcr70xlilZ ~]# nmcli -s
eth0: connected to Wired connection 1
        "Red Hat Virtio"
        ethernet (virtio_net), 00:16:3E:18:35:BB, hw, mtu 1500
        ip4 default
        inet4 172.16.0.219/24
        route4 172.16.0.0/24 metric 100
        route4 default via 172.16.0.253 metric 100
        inet6 fe80::ee8f:7d7e:f269:7a9d/64
        route6 fe80::/64 metric 1024

lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
        servers: 100.100.2.136 100.100.2.138
        interface: eth0

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
[root@iZbp12nj7zzd2hcr70xlilZ ~]# uname -a
Linux iZbp12nj7zzd2hcr70xlilZ 5.17.0-1.an23.x86_64 #1 SMP PREEMPT Tue Apr 12 16:43:09 CST 2022 x86_64 GNU/Linux
[root@iZbp12nj7zzd2hcr70xlilZ ~]# rpm -q NetworkManager
NetworkManager-1.36.2-2.an23.x86_64
Comment 1 xuchunmei alibaba_cloud_group 2022-10-31 11:06:02 UTC
就一台测试环境有异常,并且该环境上dbus-broker服务也异常起不来。
nmcli报错的问题是由于dbus-broker服务异常导致。
Comment 2 xuchunmei alibaba_cloud_group 2022-11-01 16:06:39 UTC
经过分析,是测试环境执行了如下操作导致:
dbus-daemon --config-file=/usr/share/dbus-1/system.conf --fork --print-address
killall -9 dbus-daemon
rm -rf /run/dbus/pid

Anolis OS 23上默认的dbus服务是dbus-broker,默认场景下enabled的是dbus-broker,原先的anolis7/8上使用的dbus-daemon默认是disable。
执行上述dbus-daemon后破坏了系统dbus服务,从而导致一系列的异常。
可以先stop dbus-broker,再手动执行dbus-daemon,但是这也会导致dbus服务中断,上述命令执行完成后再启动dbus-broker服务,dbus服务中断还是会导致其他依赖dbus的服务异常,比如NetworkManager和firewalld,在重新启动dbus-broker后,需要重启这些受影响的服务。

建议对系统服务的测试,遵循系统服务的测试方法,比如服务起停,手动启动进程的方法需慎重。
Comment 3 happy_orange alibaba_cloud_group 2022-11-01 16:19:52 UTC
*** Bug 2662 has been marked as a duplicate of this bug. ***
Comment 4 xuchunmei alibaba_cloud_group 2022-11-01 17:16:25 UTC
*** Bug 2662 has been marked as a duplicate of this bug. ***
Comment 5 yunmeng365524 2022-11-01 20:29:11 UTC
[root@localhost anuser]# uname -a
Linux localhost.localdomain 5.10.134-12.1.an23.x86_64 #1 SMP Thu Oct 13 11:38:24 CST 2022 x86_64 GNU/Linux
[root@localhost anuser]# nmcli -s
eth0: connected to Wired connection 1
        "Red Hat Virtio"
        ethernet (virtio_net), 00:16:3E:1B:86:FF, hw, mtu 1500
        ip4 default
        inet4 172.16.3.44/24
        route4 172.16.3.0/24 metric 100
        route4 default via 172.16.3.253 metric 100
        inet6 fe80::75f4:22c:8fe:79fc/64
        route6 fe80::/64 metric 1024

lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
        servers: 100.100.2.136 100.100.2.138
        interface: eth0

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
[root@localhost anuser]#