cloud-init status: not started

[J-Snowwite]

Bug report

[root@openeuler-25 ~]# cloud-init status --long
status: not started
extended_status: not started
boot_status_code: enabled-by-generator
detail: Cloud-init enabled by systemd cloud-init-generator
errors: []
recoverable_errors: {}

Steps to reproduce the problem

dnf install -y cloudinit && cloud-init clean -l -s -r

[root@openeuler-25 log]# cloud-init status --long
status: not started
extended_status: not started
boot_status_code: enabled-by-generator
detail: Cloud-init enabled by systemd cloud-init-generator
errors: []
recoverable_errors: {}

Environment details

**OO[root@openeuler-25 log]# cloud-init --version
/usr/bin/cloud-init 25.1
[root@openeuler-25 log]# cat /etc/rel
openEuler release 25.09
NAME="openEuler"
VERSION="25.09"
ID="openEuler"
VERSION_ID="25.09"
PRETTY_NAME="openEuler 25.09"
ANSI_COLOR="0;31"

openEuler release 25.09
cpe:/o:openEuler:openEuler:25.09:ga:server

root@control01:~# docker ps -a |grep nova
1494c16736d8 artifactory.elextec.com:4000/kolla/centos-source-nova-compute:ussuri-2.5.6 "dumb-init --single-…" 14 months ago Up 28 hours nova_compute
6e1ff488d616 artifactory.elextec.com:4000/kolla/centos-source-nova-libvirt:ussuri-fs "dumb-init --single-…" 14 months ago Up 28 hours nova_libvirt
4f7c02a8ff2e artifactory.elextec.com:4000/kolla/centos-source-nova-ssh:ussuri "dumb-init --single-…" 14 months ago Up 28 hours nova_ssh
f6c95e56fd89 artifactory.elextec.com:4000/kolla/centos-source-nova-serialproxy:ussuri-1.0.1 "dumb-init --single-…" 14 months ago Up 28 hours nova_serialproxy
fe86a7ad5999 artifactory.elextec.com:4000/kolla/centos-source-nova-novncproxy:ussuri-2.4.6 "dumb-init --single-…" 14 months ago Up 28 hours nova_novncproxy
333e326df2cf artifactory.elextec.com:4000/kolla/centos-source-nova-conductor:ussuri-2.4.6 "dumb-init --single-…" 14 months ago Up 28 hours nova_conductor
d0f758174c8f artifactory.elextec.com:4000/kolla/centos-source-nova-api:ussuri-2.4.7 "dumb-init --single-…" 14 months ago Up 28 hours nova_api
c7dcff8d22bf artifactory.elextec.com:4000/kolla/centos-source-nova-scheduler:ussuri-1.3 "dumb-init --single-…" 14 months ago Up 28 hours

cloud-init logs

[root@openeuler-25 cloud-init]# cat ds-identify.log
[up 3.05s] ds-identify
policy loaded: mode=search report=false found=all maybe=none notfound=disabled
/etc/cloud/cloud.cfg.d/90_nocloud.cfg set datasource_list: [ NoCloud ]
DMI_PRODUCT_NAME=OpenStack Nova
DMI_SYS_VENDOR=OpenStack Foundation
DMI_PRODUCT_SERIAL=2148443d-822d-4e93-9063-2f96de9b6fe3
DMI_PRODUCT_UUID=2148443d-822d-4e93-9063-2f96de9b6fe3
PID_1_PRODUCT_NAME=unavailable
DMI_CHASSIS_ASSET_TAG=
DMI_BOARD_NAME=unavailable
FS_LABELS=
ISO9660_DEVS=
KERNEL_CMDLINE=BOOT_IMAGE=/vmlinuz-6.6.0-102.0.0.8.oe2509.x86_64 root=UUID=a7901293-e626-495f-ad93-2f3019a7b5a6 ro cgroup_disable=files apparmor=0 crashkernel=512M
VIRT=kvm
UNAME_KERNEL_NAME=Linux
UNAME_KERNEL_VERSION=#1 SMP Tue Sep 23 19:58:30 CST 2025
UNAME_MACHINE=x86_64
DSNAME=
DSLIST=NoCloud
MODE=search
ON_FOUND=all
ON_MAYBE=none
ON_NOTFOUND=disabled
pid=516 ppid=498
is_container=false
single entry in datasource_list (NoCloud) use that.
[up 3.09s] returning 0

[root@openeuler-25 cloud-init]# cd /var/log/
[root@openeuler-25 log]# ll
总计 11896
drwxr-xr-x. 2 root root 4096 12月15日 16:54 anaconda
drwx------. 2 root root 4096 12月15日 17:16 audit
-rw-rw----. 1 root utmp 2688 12月15日 18:00 btmp
drwxr-xr-x. 2 chrony chrony 4096 9月16日 13:53 chrony
-rw-------. 1 root root 13114 12月17日 17:10 cron
-rw-r--r--. 1 root root 433868 12月17日 17:06 dnf.librepo.log
-rw-r--r--. 1 root root 353516 12月17日 17:06 dnf.log

[J-Snowwite]

下面有一个完整的排查过程

1、情况
[root@fedora43 ~]# cloud-init status --long
status: not started
extended_status: not started
boot_status_code: enabled-by-generator
detail: Cloud-init enabled by systemd cloud-init-generator
errors: []
recoverable_errors: {}
2、调试初始化--正常进行初始化
[root@fedora43 ~]# cloud-init --debug init
2025-12-12 01:56:13,450 - signal_handler.py[INFO]: Signal state [0] - default way of handling signal was previously in use.
2025-12-12 01:56:13,450 - signal_handler.py[INFO]: Signal state [0] - default way of handling signal was previously in use.
| |
+----[SHA256]-----+
[root@fedora43 ~]#
3、查看数据源--查询所有数据源
[root@fedora43 ~]# cloud-init query -a
{
"_beta_keys": [
"subplatform"
],
],
"python_version": "3.14.0",
"region": null,
"subplatform": "metadata (http://169.254.169.254)",
"system_platform": "Linux-6.17.1-300.fc43.x86_64-x86_64-with-glibc2.42",
"variant": "fedora"
},
"variant": "fedora",
"vendordata": ""
}
4、数据采集--说明数据采集正常
[root@fedora43 ~]# cloud-id
openstack

[root@fedora43 ~]# curl -v http://169.254.169.254/

• Trying 169.254.169.254:80...
• Connected to 169.254.169.254 (169.254.169.254) port 80
• using HTTP/1.x

GET / HTTP/1.1
Host: 169.254.169.254
User-Agent: curl/8.15.0
Accept: /

• Request completely sent off
  < HTTP/1.1 200 OK
  < Content-Type: text/plain; charset=UTF-8
  < Content-Length: 98
  < Date: Fri, 12 Dec 2025 01:55:03 GMT
  5、查看启动过程--下述情况说明 generator已经成功的引导cloud-init.target启动了
  [root@host-10-99-0-125 ~]# cd /run/cloud-init/
  [root@host-10-99-0-125 cloud-init]# ll
  总计 12
  -rw-r--r--. 1 root root 37 12月18日 14:58 cloud.cfg
  -rw-r--r--. 1 root root 319 12月18日 14:58 cloud-init-generator.log
  -rw-r--r--. 1 root root 1470 12月18日 14:58 ds-identify.log
  -rw-r--r--. 1 root root 0 12月18日 14:58 enabled

[root@host-10-99-0-125 cloud-init]# cat cloud.cfg
datasource_list: [ OpenStack, None ]

[root@host-10-99-0-125 cloud-init]# cat cloud-init-generator.log
/usr/lib/systemd/system-generators/cloud-init-generator normal=/run/systemd/generator early=/run/systemd/generator.early late=/run/systemd/generator.late
checking for datasource
ds-identify rc=0
enabled via /run/systemd/generator.early/multi-user.target.wants/cloud-init.target -> /lib/systemd/system/cloud-init.target

[root@host-10-99-0-125 cloud-init]# cat ds-identify.log
[up 3.09s] ds-identify
policy loaded: mode=search report=false found=all maybe=none notfound=disabled
........
Found single datasource: OpenStack
[up 3.15s] returning 0
6、查看启动的进程状态，以及cloudinit的日志
[root@host-10-99-0-125 cloud-init]# systemctl list-unit-files | grep cloud
cloud-config.service enabled disabled
cloud-final.service enabled disabled
cloud-init-hotplugd.service static -
cloud-init-local.service enabled disabled
cloud-init-main.service disabled disabled
cloud-init-network.service enabled disabled
cloud-init-hotplugd.socket disabled disabled
cloud-config.target static -
cloud-init.target enabled-runtime disabled

[root@host-10-99-0-125 cloud-init]# ll /var/log/cloud*
ls: 无法访问 '/var/log/cloud*': No such file or directory

这里启动的顺序是，只有上一个服务完成后，才会运行下一个服务
main
└─ local
└─ network
└─ config
└─ final
基于上述信息，可以确认，操作系统在启动之初已经启动了generator，然后generator检查了 数据源等选项，确认服务正常运行
PS：systemd generator 是一种：在 systemd 启动时运行的小程序，用来动态生成 unit 文件

然后通过查看/var/log/下面，没有发现cloudinit日志，可以确认cloud-init并没有启动，通过服务可以看到存在
cloud-init-main.service disabled disabled
7、将所有涉及到cloudinit的服务全部设置为 enable，再次运行
[root@host-10-99-0-125 cloud-init]# systemctl enable cloud-init-hotplugd.service cloud-init-main.service cloud-init-hotplugd.socket cloud-config.target cloud-init.target
Created symlink /etc/systemd/system/cloud-init.target.wants/cloud-init-main.service → /usr/lib/systemd/system/cloud-init-main.service.
Created symlink /etc/systemd/system/cloud-config.target.wants/cloud-init-hotplugd.socket → /usr/lib/systemd/system/cloud-init-hotplugd.socket.

[root@host-10-99-0-125 cloud-init]# cloud-init clean -l -s -r
8、查看状态--发现还是没有启动成功--cloud-init-main.service正常启动，那么就是在这个地方没有启动后续进程的，因为在这里是启动所有后续服务的节点
[root@host-10-99-0-125 ~]# cloud-init status --long
status: not started
extended_status: not started
boot_status_code: enabled-by-generator
detail: Cloud-init enabled by systemd cloud-init-generator
errors: []
recoverable_errors: {}

[root@host-10-99-0-125 ~]# ll /var/log/cloud*
ls: 无法访问 '/var/log/cloud*': No such file or directory

[root@host-10-99-0-125 ~]# systemctl status cloud-init-main.service
● cloud-init-main.service - Cloud-init: Single Process
Loaded: loaded (/usr/lib/systemd/system/cloud-init-main.service; enabled; preset: disabled)
Active: active (running) since Thu 2025-12-18 15:14:43 CST; 1min 36s ago
Main PID: 723 (cloud-init)
Status: "Waiting on external services to complete before starting the local stage."
Tasks: 1
Memory: 56.7M ()
CGroup: /system.slice/cloud-init-main.service
└─723 /usr/bin/python3 /usr/bin/cloud-init --all-stages

12月 18 15:14:41 localhost systemd[1]: Starting Cloud-init: Single Process...
12月 18 15:14:43 localhost systemd[1]: Started Cloud-init: Single Process.
9、查看服务启动条件
[root@host-10-99-0-125 ~]# cat /usr/lib/systemd/system/cloud-init-main.service
[Unit]
Description=Cloud-init: Single Process

After=systemd-remount-fs.service
Before=cloud-init-local.service
Before=shutdown.target
Conflicts=shutdown.target
RequiresMountsFor=/var/lib/cloud
ConditionPathExists=!/etc/cloud/cloud-init.disabled
这个条件的意思就是不存在/etc/cloud/cloud-init.disabled这个文件，就通过
ConditionKernelCommandLine=!cloud-init=disabled
这个条件的意思就是在内核参数中没有cloud-init=disabled，就通过
ConditionEnvironment=!KERNEL_CMDLINE=cloud-init=disabled
这个条件的意思就是，如果 存在环境变量 KERNEL_CMDLINE，并且其内容包含 cloud-init=disabled → 条件失败

[Service]
Type=notify
ExecStart=/usr/bin/cloud-init --all-stages
KillMode=process
TasksMax=infinity
TimeoutStartSec=infinity

Output needs to appear in instance console output

StandardOutput=journal+console

[Install]
WantedBy=cloud-init.target

将 ConditionEnvironment=!KERNEL_CMDLINE=cloud-init=disabled 注释掉，添加一个空返回 ConditionEnvironment=

Condition 检查
↓（失败）
ExecStart 根本不会被执行
↓
/usr/bin/cloud-init 从未运行
↓
Python 日志系统没初始化
10、继续检查状态，发现在等待external services,等待的是其他服务，在初始化之前只会等待拉取的元数据，那么检查下配置文件是否存在
datasource_list: [ OpenStack ]--如果存在此配置就跳过<前面因为存在数据源，所以不修改>
[root@host-10-99-0-125 ~]# rm -rf /var/lib/cloud /var/log/cloud* && cloud-init clean -l -s -r

[root@host-10-99-0-125 ~]# cloud-init status --long
status: not started
extended_status: not started
boot_status_code: enabled-by-generator
detail: Cloud-init enabled by systemd cloud-init-generator
errors: []
recoverable_errors: {}

[root@host-10-99-0-125 ~]# systemctl status cloud-init-main.service
● cloud-init-main.service - Cloud-init: Single Process
Loaded: loaded (/usr/lib/systemd/system/cloud-init-main.service; enabled; preset: disabled)
Active: active (running) since Thu 2025-12-18 15:28:30 CST; 11min ago
Main PID: 718 (cloud-init)
Status: "Waiting on external services to complete before starting the local stage."
Tasks: 1
Memory: 56.8M ()
CGroup: /system.slice/cloud-init-main.service
└─718 /usr/bin/python3 /usr/bin/cloud-init --all-stages

12月 18 15:28:28 localhost systemd[1]: Starting Cloud-init: Single Process...
12月 18 15:28:30 localhost systemd[1]: Started Cloud-init: Single Process.
11、检查cloud-init-local.service，需要其进行了local阶段的初始化，发现存在sh: 行 1: nc: 未找到命令，且没有其他执行过程
[root@host-10-99-0-125 ~]# systemctl status cloud-init-local.service
● cloud-init-local.service - Cloud-init: Local Stage (pre-network)
Loaded: loaded (/usr/lib/systemd/system/cloud-init-local.service; enabled; preset: disabled)
Active: active (exited) since Thu 2025-12-18 15:42:55 CST; 3min 12s ago
Process: 776 ExecStart=sh -c echo "start" | nc -U /run/cloud-init/share/local.sock | sh (code=exited, status=0/SUCCESS)
Main PID: 776 (code=exited, status=0/SUCCESS)

12月 18 15:42:55 localhost systemd[1]: Starting Cloud-init: Local Stage (pre-network)...
12月 18 15:42:55 localhost sh[778]: sh: 行 1: nc: 未找到命令
12月 18 15:42:55 localhost systemd[1]: Finished Cloud-init: Local Stage (pre-network).

[root@host-10-99-0-125 ~]# dnf install -y nc
Last metadata expiration check: 0:59:35 ago on 2025年12月18日 星期四 14时57分46秒.
Installed:
libssh2-1.11.0-4.oe2509.x86_64 nmap-2:7.94-9.oe2509.x86_64
Complete!

[root@host-10-99-0-125 ~]# rm -rf /var/lib/cloud /var/log/cloud* && cloud-init clean -l -s -r
12、检查状态
[root@test123 ~]# cloud-init status --long
status: done
extended_status: done
boot_status_code: enabled-by-generator
last_update: Thu, 01 Jan 1970 00:00:13 +0000
detail: DataSourceOpenStackLocal [net,ver=2]
errors: []
recoverable_errors: {}

[root@test123 ~]# cloud-init analyze show
-- Boot Record 01 --
The total time elapsed since completing an event is printed after the "@" character.
The time the event takes is printed after the "+" character.

Starting stage: init-local
|->no cache found @00.26400s +00.00000s |->found local data from DataSourceOpenStackLocal @00.30300s +03.66900s
Finished stage: (init-local) 04.34100 seconds

Starting stage: init-network
|->restored from cache with run check: DataSourceOpenStackLocal [net,ver=2] @04.89600s +00.00000s |->setting up datasource @04.96300s +00.00000s
|->reading and applying user-data @04.99200s +00.00800s |->reading and applying vendor-data @05.00000s +00.00000s
|->reading and applying vendor-data2 @05.00000s +00.00000s |->activating datasource @05.02700s +00.00400s
|->config-seed_random ran successfully and took 0.005 seconds @05.07700s +00.00500s |->config-growpart ran successfully and took 0.005 seconds @05.08200s +00.00500s
|->config-resizefs ran successfully and took 0.042 seconds @05.08800s +00.04100s |->config-mounts ran successfully and took 0.098 seconds @05.12900s +00.09900s
|->config-set_hostname ran successfully and took 0.002 seconds @05.22800s +00.00300s |->config-update_hostname ran successfully and took 0.005 seconds @05.23100s +00.00500s
|->config-users_groups ran successfully and took 0.113 seconds @05.23600s +00.11400s |->config-ssh ran successfully and took 0.518 seconds @05.35000s +00.51800s
|`->config-set_passwords ran successfully and took 0.006 seconds @05.86800s +00.00600s
Finished stage: (init-network) 01.01900 seconds

Starting stage: modules-config
|->restored from cache with run check: DataSourceOpenStackLocal [net,ver=2] @06.08100s +00.00000s Starting stage: modules-config |->config-locale ran successfully and took 0.008 seconds @06.12000s +00.00800s
Finished stage: (modules-config) 00.03200 seconds

Starting stage: modules-final
|->restored from cache with run check: DataSourceOpenStackLocal [net,ver=2] @06.22200s +00.00300s Starting stage: modules-final |->config-reset_rmc ran successfully and took 0.004 seconds @06.28400s +00.00500s
|->config-scripts_vendor ran successfully and took 0.004 seconds @06.28900s +00.00400s |->config-scripts_per_once ran successfully and took 0.004 seconds @06.29300s +00.00400s
|->config-scripts_per_boot ran successfully and took 0.000 seconds @06.29700s +00.00000s |->config-scripts_per_instance ran successfully and took 0.004 seconds @06.29700s +00.00400s
|->config-scripts_user ran successfully and took 0.004 seconds @06.30100s +00.00400s |->config-ssh_authkey_fingerprints ran successfully and took 0.014 seconds @06.30500s +00.01400s
|->config-keys_to_console ran successfully and took 0.056 seconds @06.32000s +00.05800s |->config-install_hotplug ran successfully and took 0.004 seconds @06.37800s +00.00500s
|`->config-final_message ran successfully and took 0.018 seconds @06.38300s +00.01700s
Finished stage: (modules-final) 00.16300 seconds

Total Time: 5.55500 seconds

1 boot records analyzed