FFE ready with all info in the Description.
Subscribed the Release Team, once I get an Ack I can upload.

** Description changed:

+ [FFE]
+ 
+ Debian didn't move at all yet, so I wanted to request an FFE for Artful
+ on this.
+ 
+ This will fix the bug here but many more (see git log of slof).
+ Furthermore this release [1] is the one meant to tag along qemu 2.10, so it 
might be worth in general to pick that up for Artful.
+ 
+ I checked the changes since [2] and they are mostly bug fixes anyway, so it 
is close to not needing an FFE.
+ But standing out of these "mostly fixes", are a few what I'd consider a 
feature:
+ - block write support
+ - New SLOF boot menu
+ - Allow >255 LUNs
+ I'd ask the Release Team to make their own conclusion by looking at [3].
+ 
+ As I said overall the changes are not "too much":
+ - 57 commits
+ - 62 files changed, 1077 insertions(+), 682 deletions(-)
+ - biggest part in terms of LOC is a rework/cleanup in netload
+ - list of changes [4] (no further Changelog file)
+ 
+ Fortunately also the packageing is rather straight forward - small
+ d/rules, very low amount of files in d/* in general.
+ 
+ I prepared an upload, built and tested it.
+ Providing the logs that are required for an FFE:
+ - build at [5]
+ - build-log at [6]
+ - install log at [7]
+ - Extended testing done via the full KVM regression set on powerpc where 
+   the slof is used for guests. Logs are in [8] (overview)
+   Note: the remaining issues around copy-storage and the cross-release 
+   migration are known issues of qemu (bug 1711602) and ipxe (bug 1713490) 
+   and fixed in uploads today, all else is good.
+ 
+ [1]: 
https://github.com/qemu/SLOF/commit/89f519f09bf850918b60526e50409afb663418aa
+ [2]: 
https://github.com/qemu/SLOF/commit/efd65f49929d7db775b26066d538c8120ae3db94
+ [3]: https://github.com/qemu/SLOF
+ [4]: http://paste.ubuntu.com/25423207/
+ [5]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2925
+ [6]: 
https://launchpadlibrarian.net/335009365/buildlog_ubuntu-artful-amd64.slof_20170724+dfsg-0ubuntu1_BUILDING.txt.gz
+ [7]: http://paste.ubuntu.com/25431028/
+ [8]: http://paste.ubuntu.com/25431590/
+ 
+ 
+ ########
+ 
+ 
  ---Problem Description---
  SLOF dhcp request doesn't include client architecture code 93
-  
- Contact Information = Murilo Opsfelder Ara?jo <[email protected]> 
-  
+ 
+ Contact Information = Murilo Opsfelder Ara?jo <[email protected]>
+ 
  ---uname output---
  Linux muriloo-hostos-devel-ppc64le.aus.stglabs.ibm.com 
3.10.0-514.21.1.el7.ppc64le #1 SMP Fri May 26 19:40:01 GMT 2017 ppc64le ppc64le 
ppc64le GNU/Linux
-  
- Machine Type = p8 
-  
+ 
+ Machine Type = p8
+ 
  ---Debugger---
  A debugger is not configured
-  
+ 
  ---Steps to Reproduce---
-  The following patch is necessary to include client architecture code 93 in 
SLOF dhcp requests:
+  The following patch is necessary to include client architecture code 93 in 
SLOF dhcp requests:
  
  https://github.com/aik/SLOF/commit/db35f1b8a2d3e44f4a12ca926359cc2575e98064
  
  commit db35f1b8a2d3e44f4a12ca926359cc2575e98064
  Author: Murilo Opsfelder Araujo <[email protected]>
  Date:   Fri Jun 23 09:23:25 2017 -0300
  
-     lib/Makefile: Pass FLAG to make in SUBDIRS target
-     
-     Some applications, e.g. https://maas.io/, trust on the dhcp code 93
-     option to reply the correct pxelinux.0 file according to client
-     architecture.
-     
-     Today, dhcp.c is compiled without DHCPARCH, which causes it not to
-     send client architecture in the dhcp request, i.e. dhcpd server can
-     reply a pxelinux.0 binary that is not intended for client
-     architecture.
-     
-     This patch makes sure client architecture is sent in the dhcp request.
-     
-     Signed-off-by: Murilo Opsfelder Araujo <[email protected]>
-     Signed-off-by: Alexey Kardashevskiy <[email protected]>
-  
- Userspace tool common name: /usr/share/qemu/slof.bin 
+     lib/Makefile: Pass FLAG to make in SUBDIRS target
  
- Userspace rpm: SLOF 
-  
- The userspace tool has the following bit modes: 64-bit 
+     Some applications, e.g. https://maas.io/, trust on the dhcp code 93
+     option to reply the correct pxelinux.0 file according to client
+     architecture.
  
- Userspace tool obtained from project website:  na 
-  
+     Today, dhcp.c is compiled without DHCPARCH, which causes it not to
+     send client architecture in the dhcp request, i.e. dhcpd server can
+     reply a pxelinux.0 binary that is not intended for client
+     architecture.
+ 
+     This patch makes sure client architecture is sent in the dhcp
+ request.
+ 
+     Signed-off-by: Murilo Opsfelder Araujo <[email protected]>
+     Signed-off-by: Alexey Kardashevskiy <[email protected]>
+ 
+ Userspace tool common name: /usr/share/qemu/slof.bin
+ 
+ Userspace rpm: SLOF
+ 
+ The userspace tool has the following bit modes: 64-bit
+ 
+ Userspace tool obtained from project website:  na
+ 
  *Additional Instructions for Murilo Opsfelder Ara?jo <[email protected]>:
  -Attach ltrace and strace of userspace application.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706248

Title:
  [FFE] SLOF dhcp request doesn't include client architecture code 93

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

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to