[Bug 1324558] Re: SRU for biosdevname returns identical names for two different devices.

[Jorge Niedbalski]

** Description changed:

  SRU justification :
  
  The 'addslot' function can return the same value for two or more
  interfaces (same dev->index_in_slot), causing the interfaces on a given
  PCI slot get same port number. This could trigger a rename to a
- different name space (such as rename*) presented on LP : #1284043.
+ different name space (such as rename*) presented on LP: #1284043.
  
  Example problematic behavior:
  
  # biosdevname -i em1
  em1
  # biosdevname -i em2
  em3
  # biosdevname -i em3
  em4
  # biosdevname -i rename3
  em2
  
  Another customer points:
  
  On first reboot the names are different. eth0 renamed to p4p1 and eth1 renamed to p4p2
  then on next reboot eth0 renamed to p4p1 and eth1 renamed to rename3
  
- 
  Impact :
  
  Without this SRU customer will experience erroneous output from
  biosdevname ( renamed interfaces) as noticed on LP: #293633 and LP:
  #1284043
  
  Fix :
  
  Apply patches from upstream
  https://bugzilla.redhat.com/show_bug.cgi?id=782145
  
  Test Case :
- 
  
  1) Having one or more PCI ethernet cards attached
  2) Having one or more onboard ethernet cards.
  3) Run biosdevname -d and notice the renamed interfaces.
  
  I f you get some rename* interfaces this bug isn't fixed, if you can see
  the correct bios hardware names associated with the interface, it's
  fixed.
  
  Regression :
  
  None expected
  
  Description of the problem :
  
  See justification

** Description changed:

  SRU justification :
  
  The 'addslot' function can return the same value for two or more
  interfaces (same dev->index_in_slot), causing the interfaces on a given
  PCI slot get same port number. This could trigger a rename to a
  different name space (such as rename*) presented on LP: #1284043.
  
  Example problematic behavior:
  
  # biosdevname -i em1
  em1
  # biosdevname -i em2
  em3
  # biosdevname -i em3
  em4
  # biosdevname -i rename3
  em2
  
  Another customer points:
  
  On first reboot the names are different. eth0 renamed to p4p1 and eth1 renamed to p4p2
  then on next reboot eth0 renamed to p4p1 and eth1 renamed to rename3
  
  Impact :
  
  Without this SRU customer will experience erroneous output from
- biosdevname ( renamed interfaces) as noticed on LP: #293633 and LP:
+ biosdevname ( renamed interfaces) as noticed on LP: #1293633 and LP:
  #1284043
  
  Fix :
  
  Apply patches from upstream
  https://bugzilla.redhat.com/show_bug.cgi?id=782145
  
  Test Case :
  
  1) Having one or more PCI ethernet cards attached
  2) Having one or more onboard ethernet cards.
  3) Run biosdevname -d and notice the renamed interfaces.
  
  I f you get some rename* interfaces this bug isn't fixed, if you can see
  the correct bios hardware names associated with the interface, it's
  fixed.
  
  Regression :
  
  None expected
  
  Description of the problem :
  
  See justification

** Description changed:

  SRU justification :
  
  The 'addslot' function can return the same value for two or more
  interfaces (same dev->index_in_slot), causing the interfaces on a given
  PCI slot get same port number. This could trigger a rename to a
  different name space (such as rename*) presented on LP: #1284043.
  
  Example problematic behavior:
  
  # biosdevname -i em1
  em1
  # biosdevname -i em2
  em3
  # biosdevname -i em3
  em4
  # biosdevname -i rename3
  em2
  
  Another customer points:
  
  On first reboot the names are different. eth0 renamed to p4p1 and eth1 renamed to p4p2
  then on next reboot eth0 renamed to p4p1 and eth1 renamed to rename3
  
  Impact :
  
  Without this SRU customer will experience erroneous output from
  biosdevname ( renamed interfaces) as noticed on LP: #1293633 and LP:
  #1284043
  
  Fix :
  
  Apply patches from upstream
  https://bugzilla.redhat.com/show_bug.cgi?id=782145
  
  Test Case :
  
- 1) Having one or more PCI ethernet cards attached
- 2) Having one or more onboard ethernet cards.
+ 1) Have one or more PCI ethernet cards attached
+ 2) Have one or more onboard ethernet cards available.
  3) Run biosdevname -d and notice the renamed interfaces.
  
- I f you get some rename* interfaces this bug isn't fixed, if you can see
+ If you get some rename* interfaces this bug isn't fixed, if you can see
  the correct bios hardware names associated with the interface, it's
  fixed.
  
  Regression :
  
  None expected
  
  Description of the problem :
  
  See justification

** Changed in: biosdevname (Ubuntu)
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1324558

Title:
  SRU for biosdevname returns identical names for two different devices.

Status in “biosdevname” package in Ubuntu:
  In Progress

Bug description:
  SRU justification :

  The 'addslot' function can return the same value for two or more
  interfaces (same dev->index_in_slot), causing the interfaces on a
  given PCI slot get same port number. This could trigger a rename to a
  different name space (such as rename*) presented on LP: #1284043.

  Example problematic behavior:

  # biosdevname -i em1
  em1
  # biosdevname -i em2
  em3
  # biosdevname -i em3
  em4
  # biosdevname -i rename3
  em2

  Another customer points:

  On first reboot the names are different. eth0 renamed to p4p1 and eth1 renamed to p4p2
  then on next reboot eth0 renamed to p4p1 and eth1 renamed to rename3

  Impact :

  Without this SRU customer will experience erroneous output from
  biosdevname ( renamed interfaces) as noticed on LP: #1293633 and LP:
  #1284043

  Fix :

  Apply patches from upstream
  https://bugzilla.redhat.com/show_bug.cgi?id=782145

  Test Case :

  1) Have one or more PCI ethernet cards attached
  2) Have one or more onboard ethernet cards available.
  3) Run biosdevname -d and notice the renamed interfaces.

  If you get some rename* interfaces this bug isn't fixed, if you can
  see the correct bios hardware names associated with the interface,
  it's fixed.

  Regression :

  None expected

  Description of the problem :

  See justification

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/biosdevname/+bug/1324558/+subscriptions