> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-openstack/5.8/troubleshooting/linux-kvm/troubleshooting-ipissue-selinux.md).

# Troubleshooting IP Address Assignment for Scientific Linux 6.x

Scientific Linux 6.x EPEL supports cloud-init version 0.7.4. This version of cloud-init has two known issues related to IP assignment to virtual machines (VM).

a) [Parse error for ifcfg-eth0](https://bugs.launchpad.net/cloud-init/+bug/1448594) - If the image or snapshot that the VM is being created from has existing static network configuration, cloud-init may not assign it a new IP address due to an error parsing its network interfaces.

b) Network assignment fails if the network is already up [\[1\]](https://bugs.launchpad.net/cloud-init/+bug/1275098)[\[2\]](https://bugs.launchpad.net/cloud-init/+bug/1225922) - if after booting up a VM already has an IP address assigned to it, cloud-init fails to re-assign a new IP address to the VM.

The attached update to cloud-init 0.7.4 (cloud-init-0.7.4-2.noarch.rpm) addresses both these issues.

You will need to first uninstall any existing version of cloud-init installed on your VM, before installing the provided rpm. Follow these instructions for that process:

{% tabs %}
{% tab title="Scientific Linux" %}

```none
yum erase cloud-init
yum install ./cloud-init-0.7.4-2.noarch.rpm
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform9.com/managed-openstack/5.8/troubleshooting/linux-kvm/troubleshooting-ipissue-selinux.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.