[Kernel-packages] [Bug 1646805] Comment bridged from LTC Bugzilla

2019-04-10 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2019-04-10 05:45 EDT---
Requires Firmware update on top - this effort is ongoing and will be tracked by 
a seperate LP-Bugziila

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1646805

Title:
  MAC address needs to be unique and unchanged during entire netboot
  process

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Currently the MAC address is not solely used to id the machine or system.
  It is at the moment used to id the interface that the MAC represents.
  (At a very early state in the process the MAC address is missing or only 
available from inside the partition.)

  The minimum PXE boot requirements need to be satisfied in general.
  The boot loader is part of the firmware and not loaded from the server.
  So that means the firmware needs to provide the MAC address.
  But the MAC address is not available at that time, so it's not available 
upfront.

  MaaS is using the same MAC address for the initial DHCP request as for the 
network boot.
  Hence an initially known MAC address is required that needs to be static and 
doesn't change (on subsequent boots for that instance).

  There might be an IBM internal ticket already open for this - please
  check.

  Furthermore the firmware needs to requests files like this:
  pxelinux.cfg/01-88-99-aa-bb-cc-dd
  pxelinux.cfg/default
  And BOOTIF support is required:
  See 'petitboot doesn't handle ipappend in pxelinux.cfg'
  https://bugs.launchpad.net/tasty-taco/+bug/1322307
  for reference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1646805/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1646805] Comment bridged from LTC Bugzilla

2019-04-05 Thread bugproxy
--- Comment From schwe...@de.ibm.com 2019-04-05 05:06 EDT---
Hi Frank, sorry to say, but this patch does not apply to IBMZ Firmware at all.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1646805

Title:
  MAC address needs to be unique and unchanged during entire netboot
  process

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Currently the MAC address is not solely used to id the machine or system.
  It is at the moment used to id the interface that the MAC represents.
  (At a very early state in the process the MAC address is missing or only 
available from inside the partition.)

  The minimum PXE boot requirements need to be satisfied in general.
  The boot loader is part of the firmware and not loaded from the server.
  So that means the firmware needs to provide the MAC address.
  But the MAC address is not available at that time, so it's not available 
upfront.

  MaaS is using the same MAC address for the initial DHCP request as for the 
network boot.
  Hence an initially known MAC address is required that needs to be static and 
doesn't change (on subsequent boots for that instance).

  There might be an IBM internal ticket already open for this - please
  check.

  Furthermore the firmware needs to requests files like this:
  pxelinux.cfg/01-88-99-aa-bb-cc-dd
  pxelinux.cfg/default
  And BOOTIF support is required:
  See 'petitboot doesn't handle ipappend in pxelinux.cfg'
  https://bugs.launchpad.net/tasty-taco/+bug/1322307
  for reference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1646805/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1646805] Comment bridged from LTC Bugzilla

2019-04-04 Thread bugproxy
--- Comment From schwe...@de.ibm.com 2019-04-04 05:48 EDT---
Just to make sure: This bugzilla does not apply to Network under DPM neither on 
z13 nor on z14 machines.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1646805

Title:
  MAC address needs to be unique and unchanged during entire netboot
  process

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Currently the MAC address is not solely used to id the machine or system.
  It is at the moment used to id the interface that the MAC represents.
  (At a very early state in the process the MAC address is missing or only 
available from inside the partition.)

  The minimum PXE boot requirements need to be satisfied in general.
  The boot loader is part of the firmware and not loaded from the server.
  So that means the firmware needs to provide the MAC address.
  But the MAC address is not available at that time, so it's not available 
upfront.

  MaaS is using the same MAC address for the initial DHCP request as for the 
network boot.
  Hence an initially known MAC address is required that needs to be static and 
doesn't change (on subsequent boots for that instance).

  There might be an IBM internal ticket already open for this - please
  check.

  Furthermore the firmware needs to requests files like this:
  pxelinux.cfg/01-88-99-aa-bb-cc-dd
  pxelinux.cfg/default
  And BOOTIF support is required:
  See 'petitboot doesn't handle ipappend in pxelinux.cfg'
  https://bugs.launchpad.net/tasty-taco/+bug/1322307
  for reference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1646805/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1646805] Comment bridged from LTC Bugzilla

2019-03-15 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2019-03-15 06:25 EDT---
IBM Bugzilla status -> closed, Fix Released for disco

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1646805

Title:
  MAC address needs to be unique and unchanged during entire netboot
  process

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Currently the MAC address is not solely used to id the machine or system.
  It is at the moment used to id the interface that the MAC represents.
  (At a very early state in the process the MAC address is missing or only 
available from inside the partition.)

  The minimum PXE boot requirements need to be satisfied in general.
  The boot loader is part of the firmware and not loaded from the server.
  So that means the firmware needs to provide the MAC address.
  But the MAC address is not available at that time, so it's not available 
upfront.

  MaaS is using the same MAC address for the initial DHCP request as for the 
network boot.
  Hence an initially known MAC address is required that needs to be static and 
doesn't change (on subsequent boots for that instance).

  There might be an IBM internal ticket already open for this - please
  check.

  Furthermore the firmware needs to requests files like this:
  pxelinux.cfg/01-88-99-aa-bb-cc-dd
  pxelinux.cfg/default
  And BOOTIF support is required:
  See 'petitboot doesn't handle ipappend in pxelinux.cfg'
  https://bugs.launchpad.net/tasty-taco/+bug/1322307
  for reference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1646805/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1646805] Comment bridged from LTC Bugzilla

2019-03-11 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2018-12-12 05:40
EDT---

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1646805

Title:
  MAC address needs to be unique and unchanged during entire netboot
  process

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Currently the MAC address is not solely used to id the machine or system.
  It is at the moment used to id the interface that the MAC represents.
  (At a very early state in the process the MAC address is missing or only 
available from inside the partition.)

  The minimum PXE boot requirements need to be satisfied in general.
  The boot loader is part of the firmware and not loaded from the server.
  So that means the firmware needs to provide the MAC address.
  But the MAC address is not available at that time, so it's not available 
upfront.

  MaaS is using the same MAC address for the initial DHCP request as for the 
network boot.
  Hence an initially known MAC address is required that needs to be static and 
doesn't change (on subsequent boots for that instance).

  There might be an IBM internal ticket already open for this - please
  check.

  Furthermore the firmware needs to requests files like this:
  pxelinux.cfg/01-88-99-aa-bb-cc-dd
  pxelinux.cfg/default
  And BOOTIF support is required:
  See 'petitboot doesn't handle ipappend in pxelinux.cfg'
  https://bugs.launchpad.net/tasty-taco/+bug/1322307
  for reference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1646805/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp