yahoo-eng-team team mailing list archive

[Miguel Angel <1871326@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Hello,

I think there is a bug in version 19.4-33-gbb4131a2-0ubuntu1~18.04.1,
because with version 18.2-14-g6d48d265-0ubuntu1 it works correctly.

In case you need to improve this check in your next update.

Steps I've followed:
- I set up a virtual machine in openstack with Ubuntu 18.04 and with the associated NVIDIA (PF) and Mellanox (VF) PCI
- I installed Mellanox Driver (5.0-1)
- All right so far
- I created a new image in glance and raised a new machine with this new image.

Problem:
- It doesn't assign the ip to the new machine, and thus doesn't start the network
- Looking at the logs I found that cloud-init gives a problem:
RuntimeError: duplicate mac found! both 'lo' and 'ib0' have mac '00:00:00:00:00'

Solution:
After a lot of looking I think there's a bug in the new version of cloud-init in how it checks MACs (version 19.4-33-gbb4131a2-0ubuntu1~18.04.1)
With the previous version it works correctly (18.2-14-g6d48d265-0ubuntu1)

Opinion:
Infiniband MACs are much longer than ethernet MACs:
MAC lo: 00:00:00:00:00
MAC eth0: fa:16:3e:20:9e:61
MAC infiniband ib0: 20:00:05:87:fe:80:00:00:00:00:00:00:00:00:00:00:00:00 

I believe that Cloud-init should identify only a part of the MAC of an infiniband card and not the whole MAC.
Comparing it to the others results in the error that the MAC is duplicated and this error leads to incorrect initialization of all network cards.
I think you can correct this error by comparing the entire MAC and not just a single piece.

Greetings

** Affects: cloud-init
     Importance: Undecided
         Status: New


** Tags: cloud-init duplicate infiniband mac

** Description changed:

  Hello,
  
  I think there is a bug in version 19.4-33-gbb4131a2-0ubuntu1~18.04.1,
  because with version 18.2-14-g6d48d265-0ubuntu1 it works correctly.
  
  In case you need to improve this check in your next update.
  
- 
  Steps I've followed:
  - I set up a virtual machine in openstack with Ubuntu 18.04 and with the associated NVIDIA (PF) and Mellanox (VF) PCI
  - I installed Mellanox Driver (5.0-1)
  - All right so far
  - I created a new image in glance and raised a new machine with this new image.
  
- 
  Problem:
  - It doesn't assign the ip to the new machine, and thus doesn't start the network
  - Looking at the logs I found that cloud-init gives a problem:
  RuntimeError: duplicate mac found! both 'lo' and 'ib0' have mac '00:00:00:00:00'
  
- 
  Solution:
  After a lot of looking I think there's a bug in the new version of cloud-init in how it checks MACs (version 19.4-33-gbb4131a2-0ubuntu1~18.04.1)
- With the previous version it works correctly (18.2-14-g6d48d265-0ubuntu1) 
- 
+ With the previous version it works correctly (18.2-14-g6d48d265-0ubuntu1)
  
  Opinion:
  Infiniband MACs are much longer than ethernet MACs:
  MAC lo: 00:00:00:00:00
  MAC eth0: fa:16:3e:20:9e:61
- MAC infiniband ib0: 20:00:05:87:fe:80:00:00:00:00:00:00:00:00:00:00:00:00 My 
+ MAC infiniband ib0: 20:00:05:87:fe:80:00:00:00:00:00:00:00:00:00:00:00:00 My
  
  I believe that Cloud-init should identify only a part of the MAC of an infiniband card and not the whole MAC.
  Comparing it to the others results in the error that the MAC is duplicated and this error leads to incorrect initialization of all network cards.
  I think you can correct this error by comparing the entire MAC and not just a single piece.
  
  Greetings
- 
- MANuñez

** Description changed:

  Hello,
  
  I think there is a bug in version 19.4-33-gbb4131a2-0ubuntu1~18.04.1,
  because with version 18.2-14-g6d48d265-0ubuntu1 it works correctly.
  
  In case you need to improve this check in your next update.
  
  Steps I've followed:
  - I set up a virtual machine in openstack with Ubuntu 18.04 and with the associated NVIDIA (PF) and Mellanox (VF) PCI
  - I installed Mellanox Driver (5.0-1)
  - All right so far
  - I created a new image in glance and raised a new machine with this new image.
  
  Problem:
  - It doesn't assign the ip to the new machine, and thus doesn't start the network
  - Looking at the logs I found that cloud-init gives a problem:
  RuntimeError: duplicate mac found! both 'lo' and 'ib0' have mac '00:00:00:00:00'
  
  Solution:
  After a lot of looking I think there's a bug in the new version of cloud-init in how it checks MACs (version 19.4-33-gbb4131a2-0ubuntu1~18.04.1)
  With the previous version it works correctly (18.2-14-g6d48d265-0ubuntu1)
  
  Opinion:
  Infiniband MACs are much longer than ethernet MACs:
  MAC lo: 00:00:00:00:00
  MAC eth0: fa:16:3e:20:9e:61
- MAC infiniband ib0: 20:00:05:87:fe:80:00:00:00:00:00:00:00:00:00:00:00:00 My
+ MAC infiniband ib0: 20:00:05:87:fe:80:00:00:00:00:00:00:00:00:00:00:00:00 
  
  I believe that Cloud-init should identify only a part of the MAC of an infiniband card and not the whole MAC.
  Comparing it to the others results in the error that the MAC is duplicated and this error leads to incorrect initialization of all network cards.
  I think you can correct this error by comparing the entire MAC and not just a single piece.
  
  Greetings

-- 
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/1871326

Title:
  Duplicate mac on infiniband card, when not correct (v19.4-33)

Status in cloud-init:
  New

Bug description:
  Hello,

  I think there is a bug in version 19.4-33-gbb4131a2-0ubuntu1~18.04.1,
  because with version 18.2-14-g6d48d265-0ubuntu1 it works correctly.

  In case you need to improve this check in your next update.

  Steps I've followed:
  - I set up a virtual machine in openstack with Ubuntu 18.04 and with the associated NVIDIA (PF) and Mellanox (VF) PCI
  - I installed Mellanox Driver (5.0-1)
  - All right so far
  - I created a new image in glance and raised a new machine with this new image.

  Problem:
  - It doesn't assign the ip to the new machine, and thus doesn't start the network
  - Looking at the logs I found that cloud-init gives a problem:
  RuntimeError: duplicate mac found! both 'lo' and 'ib0' have mac '00:00:00:00:00'

  Solution:
  After a lot of looking I think there's a bug in the new version of cloud-init in how it checks MACs (version 19.4-33-gbb4131a2-0ubuntu1~18.04.1)
  With the previous version it works correctly (18.2-14-g6d48d265-0ubuntu1)

  Opinion:
  Infiniband MACs are much longer than ethernet MACs:
  MAC lo: 00:00:00:00:00
  MAC eth0: fa:16:3e:20:9e:61
  MAC infiniband ib0: 20:00:05:87:fe:80:00:00:00:00:00:00:00:00:00:00:00:00 

  I believe that Cloud-init should identify only a part of the MAC of an infiniband card and not the whole MAC.
  Comparing it to the others results in the error that the MAC is duplicated and this error leads to incorrect initialization of all network cards.
  I think you can correct this error by comparing the entire MAC and not just a single piece.

  Greetings

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1871326/+subscriptions