Bug List: (1 of 151)
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1139556 - [Cloud init] Extra ip set on NIC when configuring static ip via cloud-init
Summary: [Cloud init] Extra ip set on NIC when configuring static ip via cloud-init
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cloud-init
Version: 7.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: pre-dev-freeze
: ---
Assignee: Lars Kellogg-Stedman
QA Contact: Michael Burman
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-09 08:02 UTC by Michael Burman
Modified: 2016-12-06 19:44 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-06 19:44:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Michael Burman 2014-09-09 08:02:44 UTC 
Description of problem:
When configuring static ip via cloud-init and running VM, the NIC is set with two ip's. One from network service when vm starts and another one from the static ip that is configured via cloud-init.

Version-Release number of selected component (if applicable):
3.5.0-0.10.master.el6ev

How reproducible:
always

Steps to Reproduce:
1. Create new VM and configure static ip on NIC via cloud init(check on boot)
2. Run VM
3. Check ip on NIC

Actual results:
NIC has extra ip.

Expected results:
NIC should have one ip.

Additional info:
Because the network service starts before the cloud init, the NIC set with extra ip. If restarting network service, NIC will be left only with static ip that was configured via cloud-init.
Comment 1 Omer Frenkel 2014-09-14 09:52:06 UTC 
what is the guest os? 
what version of cloud init installed on the vm?
you do not mention in the steps when you install cloud init? is it part of the template?
Comment 2 Michael Burman 2014-09-14 11:04:33 UTC 
cloud-init-0.7.5-1.el7.x86_64 

Guest OS rhel7 and rhel6.5

I'm installing the cloud-init as part of a new VM creation. This VM based on 'neutron-appliance' template and contains relevant neutron services.
Comment 3 Shahar Havivi 2014-09-14 13:47:48 UTC 
1. Can you post the output of the shell that you see the two ips.
2. if its the order of of the services the bug should be assigned to the cloud-init package under Rhel-7.1
Comment 4 Michael Burman 2014-09-14 14:42:13 UTC 
eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:1a:4a:16:88:63 brd ff:ff:ff:ff:ff:ff
    inet 10.35.128.99/24 brd 10.35.128.255 scope global dynamic eth0
       valid_lft 42824sec preferred_lft 42824sec
    inet 10.35.128.196/24 brd 10.35.128.255 scope global secondary eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::21a:4aff:fe16:8863/64 scope link
       valid_lft forever preferred_lft forever

First ip is from network service when vm starts for the first time
Second ip is the static ip that was configured via cloud-init

When restarting network service, only static ip will remain on NIC
Comment 6 Lars Kellogg-Stedman 2014-09-15 14:09:19 UTC 
How are you configuring the static ip address?
Comment 7 Michael Burman 2014-09-15 14:17:00 UTC 
Via the cloud-init 

New VM > Initial Run > Networks > Network checked > Add New > eth0 >
Boot protocol- Static 
Ip address- 
Netmask-
Gateway-
Comment 8 Lars Kellogg-Stedman 2014-09-15 16:03:40 UTC 
I am a little confused.  It sounds like you're using some sort of gui; does this generate a cloud-init user-data script? Can you provide the contents of /var/lib/cloud/instance/user-data.txt?
Comment 9 Michael Burman 2014-09-16 07:33:05 UTC 
Yes i'm using rhevm GUI


[admin@localhost ~]$ sudo cat /var/lib/cloud/instance/user-data.txt
#cloud-config
ssh_pwauth: true
disable_root: 0
output:
  all: '>> /var/log/cloud-init-output.log'
user: admin
password: '1'
chpasswd:
  expire: false
runcmd:
- 'sed -i ''/^datasource_list: /d'' /etc/cloud/cloud.cfg; echo ''datasource_list:
  ["NoCloud", "ConfigDrive"]'' >> /etc/cloud/cloud.cfg'




[admin@localhost ~]$ ip a | grep eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    inet 10.35.128.97/24 brd 10.35.128.255 scope global dynamic eth0
    inet 10.35.128.198/24 brd 10.35.128.255 scope global secondary eth0
Comment 11 Lars Kellogg-Stedman 2016-12-06 19:44:06 UTC 
We are only able to address cloud-init issues that impact functionality in OpenStack environments.
Note You need to log in before you can comment on or make changes to this bug.
Bug List: (1 of 151)