Help Center> Bare Metal Server> Private Image Creation Guide> Creating a Linux Private Image Using virt-manager> FAQ> How Can I Handle the Failure of Data Injection into the BMS Due to the Occasional Start Failure of cloud-init-local?
View PDF

How Can I Handle the Failure of Data Injection into the BMS Due to the Occasional Start Failure of cloud-init-local?

Symptom

For Red Hat 7 and CentOS 7, cloud-init-local may fail to start. After you run systemctl status cloud-init-local.service, the message "OSError: [Errno 2] No such file or directory" is displayed. As a result, data cannot be injected into the BMS.

Solution

If Red Hat 7 or CentOS 7 has a libselinux module earlier than version 2.5.7, a known kernel bug will occasionally cause cloud-init-local start failure (for details of the bug, see https://bugzilla.redhat.com/show_bug.cgi?id=1406520). When creating a Red Hat 7 or CentOS 7 image, you are advised to upgrade libselinux to version 2.5.7 or later by following the instructions in section XenServer.

Parent topic: FAQ