Bug 1577947
Summary: | static network configuration putting prefix into IPADDR instead of PREFIX | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Martin Steigerwald <martin.steigerwald> |
Component: | cloud-init | Assignee: | Ryan McCabe <rmccabe> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | xiachen |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.5 | CC: | huzhao, jeannette9728miller, jgreguske, yacao |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-06-19 04:17:35 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Martin Steigerwald
2018-05-14 13:42:26 UTC
This bug could be reproduced on the old version, cloud-init-0.7.9-24.el7.x86_64, the same behavior as bug description. but this issue is gone on latest version of cloud-init. so close it as CURRENTRELEASE. If anyone find this issue with latest cloud-init please re-open and provide the failing cloud-init version. ----------------------------------------------------- I tested three latest cloud-init for different RHEL, did not find the issue. cloud-init-18.2-1.el7_6.3.x86_64 (rhel 7.6.0.z) cloud-init-18.5-12.el8_2.1.noarch (rhel 8.2.0.z) cloud-init-19.4-4.el8.noarch (rhel 8.3.0) Test Details, Step1. prepare an network-config file, version: 1 config: - type: physical name: eth0 subnets: - type: static address: 192.168.23.14/27 gateway: 192.168.23.1 Step2.launch an VM via NoCloud datasource $ qemu-img create -f qcow2 -o backing_file=rhel-guest-image-8.3-194.x86_64.qcow2 example.qcow2 $ genisoimage -o example_config.iso -V cidata -r -J user-data meta-data network-config $ virt-install -n example -r 512 --import --disk path=./example.qcow2 --disk path=./example_config.iso,device=cdrom --nographics Step3.login VM and check network configuration, the value of IPADDR and NETMASK is correct. [root@myhost network-scripts]# cat ifcfg-eth0 # Created by cloud-init on instance boot automatically, do not edit. # BOOTPROTO=none DEFROUTE=yes DEVICE=eth0 GATEWAY=192.168.23.1 IPADDR=192.168.23.14 NETMASK=255.255.255.224 ONBOOT=yes STARTMODE=auto TYPE=Ethernet USERCTL=no ----------------------------------------------------- BTW, the upstream bug was closed with an confirmation 'no issue with current CentOS 7.6 images' on 2019-08-05. https://bugs.launchpad.net/cloud-init/+bug/1771116 It seems you’re encountering an issue with cloud-init where the static network configuration is incorrectly placing the prefix within the IPADDR field instead of using a separate PREFIX field. This bug was reported as Bug 1577947 and appears to have been addressed in the current release1. https://www.maxim-timeclock.com To resolve this issue, you should ensure that you’re using the latest version of cloud-init where this bug has been fixed. If you’re still experiencing this problem with the latest version, you may need to manually edit the network configuration file to separate the IP address and the prefix into the IPADDR and PREFIX fields, respectively. @admins: I believe comment #3 is spam. If you agree please delete. Feel free to also delete this comment. Thanks, Martin |