Public bug reported:
I am using cloud-init v19.1 where I am passing config drive from nova layer
while VM deployment.
On a RHEL8 environment, I am observing IPv4 interfaces not coming up. We are
setting NM_CONTROLLED = no in the interface files and since RHEL8 recommends to
use NetworkManager to configure network and create connectivity it is failing.
we are setting NM_CONTROLLED = no using the code
iface_defaults = tuple([
('ONBOOT', True),
('USERCTL', False),
('NM_CONTROLLED', False),
('BOOTPROTO', 'none'),
('STARTMODE', 'auto'),
])
under the file [1] . Due to which the Network Manager is not able to
handle the interfaces
[1] cloudinit/net/sysconfig.py
Making ('NM_CONTROLLED', True) fixes the issue.
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1894837
Title:
RHEL8 ipv4 IPs not getting set
Status in cloud-init:
New
Bug description:
I am using cloud-init v19.1 where I am passing config drive from nova layer
while VM deployment.
On a RHEL8 environment, I am observing IPv4 interfaces not coming up. We are
setting NM_CONTROLLED = no in the interface files and since RHEL8 recommends to
use NetworkManager to configure network and create connectivity it is failing.
we are setting NM_CONTROLLED = no using the code
iface_defaults = tuple([
('ONBOOT', True),
('USERCTL', False),
('NM_CONTROLLED', False),
('BOOTPROTO', 'none'),
('STARTMODE', 'auto'),
])
under the file [1] . Due to which the Network Manager is not able to
handle the interfaces
[1] cloudinit/net/sysconfig.py
Making ('NM_CONTROLLED', True) fixes the issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1894837/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
