Bug #3160

VM Context failed to start IPV6 addr on CentOS 7

Added by Nicolas Belan almost 7 years ago. Updated almost 7 years ago.

Status:ClosedStart date:08/22/2014
Priority:NormalDue date:
Assignee:Javi Fontan% Done:

0%

Category:Context
Target version:Release 4.10
Resolution:fixed Pull request:
Affected Versions:OpenNebula 4.8

Description

I have installed a CentOS 7 from scratch.
I installed one-context RPM for 4.8.0.

I rebooted and 'cat' eth0 configuration:

[root@localhost network-scripts]# cat ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet
NETMASK=255.255.255.128
IPADDR=192.168.0.135
GATEWAY=192.168.0.254

IPV6INIT=yes
IPV6ADDR=2a00:afee:0:f:400:b9ff:fe1e:5c87
IPV6_DEFAULTGW=2a00:afee:0:f::ffff

The IPv6 addr is not set correctly on reboot. Only L-local IP is set (fe80::)

To fix that, I added NM_CONTROLLED=no in 00-network:gen_network_configuration()

ONBOOT=yes
NM_CONTROLLED=no
TYPE=Ethernet

Now, IPv6 is correctly set on reboot.

History

#1 Updated by Ruben S. Montero almost 7 years ago

  • Status changed from Pending to Assigned
  • Assignee set to Javi Fontan
  • Target version set to 67

#2 Updated by Javi Fontan almost 7 years ago

Thanks! I've added the issue to the context repository issue tracker:

https://github.com/OpenNebula/addon-context-linux/issues/3

#3 Updated by Javi Fontan almost 7 years ago

  • Status changed from Assigned to Closed
  • Resolution set to fixed

Fixed in the context packages repository. Will be included in the next context release.

https://github.com/OpenNebula/addon-context-linux/commit/2a9084401ad1e51024d921c77ca2a973c3a1dc44

#4 Updated by Ruben S. Montero almost 7 years ago

  • Target version changed from 67 to Release 4.10

Also available in: Atom PDF