[Bug 2069035] Re: [24.10] Please test secure-boot and lockdown on the 6.10 kernel (s390x) for Oracular
** Changed in: ubuntu-z-systems Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069035 Title: [24.10] Please test secure-boot and lockdown on the 6.10 kernel (s390x) for Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2069035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069129] Re: [UBUNTU 24.04] Cannot find or install the 'crypto-policies' package
Thanks Adrien, I was just also digging into this and found that jammy was the last release where the package existed: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069129/+subscriptions (interesting to see what you are working on instead) Meanwhile I've updated the status of this ticket to Invalid. ** Package changed: linux (Ubuntu) => crypto-policies (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: crypto-policies (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned) ** Changed in: ubuntu-z-systems Status: New => Invalid ** Changed in: crypto-policies (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069129 Title: [UBUNTU 24.04] Cannot find or install the 'crypto-policies' package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2069129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069129] Re: [UBUNTU 24.04] Cannot find or install the 'crypto-policies' package
... and I just found that it got deleted starting with kinetic/22.10 incl. rationale provided by vorlon: https://launchpad.net/ubuntu/+source/crypto-policies/20190816git-1/+publishinghistory -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069129 Title: [UBUNTU 24.04] Cannot find or install the 'crypto-policies' package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2069129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069035] Re: [24.10] Please test secure-boot and lockdown on the 6.10 kernel (s390x) for Oracular
Many thanks Grgo for the test, and the blazing fast turnaround ! ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069035 Title: [24.10] Please test secure-boot and lockdown on the 6.10 kernel (s390x) for Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2069035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052707] Re: [24.04 FEAT] bump powerpc-utils to version 1.3.12
** Changed in: ubuntu-power-systems Assignee: Skipper Bug Screeners (skipper-screen-team) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Changed in: ubuntu-power-systems Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052707 Title: [24.04 FEAT] bump powerpc-utils to version 1.3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2052707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069040] [NEW] Compile glibc for Power9
Public bug reported: The architectural level set for ppc64el is generally Power 9. But it turned out that glibc is still compiled for Power 8. This should be changed to Power 9. ** Affects: ubuntu-power-systems Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Affects: glibc (Ubuntu) Importance: Undecided Assignee: Simon Chopin (schopin) Status: New ** Tags: ppc64el ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069040 Title: Compile glibc for Power9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2069040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069035] Re: [24.10] Please test secure-boot and lockdown on the 6.10 kernel (s390x) for Oracular
** Changed in: ubuntu-z-systems Assignee: (unassigned) => bugproxy (bugproxy) ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: reverse-proxy-bugzilla s390x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069035 Title: [24.10] Please test secure-boot and lockdown on the 6.10 kernel (s390x) for Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2069035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067355] Re: Update s390-tools to (currently latest) v2.33.1 in oracular
I've worked on some more lintian warning, polishing the package a bit more and have now an updated debdiff (just for s390-tools; s390-tools-signed didn't change): https://launchpadlibrarian.net/734514167/s390-tools_2.31.0-0ubuntu5_2.33.1-0ubuntu1.diff.gz and also did a new test build in PPA that is available here: https://launchpad.net/~fheimes/+archive/ubuntu/lp2067355/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067355 Title: Update s390-tools to (currently latest) v2.33.1 in oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2067355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068577] Re: [UBUNTU 24.04] Running sosreport causes the system to crash and produce a dump
On top I've noticed that there are probably nfs shares active in your system (saw that in fstab). There is an open issue with nfs. Would you mind tearing down (and removing nfs) temporarily and for test reasons and run sosreport then again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068577 Title: [UBUNTU 24.04] Running sosreport causes the system to crash and produce a dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2068577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065579] Re: [UBUNTU 22.04] OS guest boot issues on 9p filesystem
** Changed in: ubuntu-z-systems Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065579 Title: [UBUNTU 22.04] OS guest boot issues on 9p filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2065579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068577] Re: [UBUNTU 24.04] Running sosreport causes the system to crash and produce a dump
Thanks for having reported this issue. I tried to recreate this on the systems that I have at hand (which is a z13 in PS/SM mode and a LinuxONE 3 in DPM mode) and ran sosreport twice on both systems in an LPAR, with a default 24.04 install, and after having 24.04 upgraded to the latest level (incl. kernel) with: sudo apt update && sudo apt full-upgrade # and reboot and in none of the four cases sosreport crashed for me. Would you please retry (like my colleagues above already mentioned) with the latest kernel (means after full-upgrade)? Even if I cannot recreate with the GA kernel on my system(s). So I'm now trying to figure out differences between your setup and mine. You sosreport package versions is the same than mine: sosreport (version 4.5.6) Then I though that you may use a filesystem formatted other than ext4, which may cause issues, since the last line that you see seems to be: "Starting 21/74 filesys [Running: block btrfs ebpf filesys]" but the debuginfo tells you that you are also on ext4 (like me). Looks like you system is a IBM z16 Model A01, Machine Type 3931 (that I do not have at hand). Is this really happening for you on an LPAR or in a zVM guest? (since dbginfo also incl. zvm data)? ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: sosreport (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned) ** Changed in: ubuntu-z-systems Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068577 Title: [UBUNTU 24.04] Running sosreport causes the system to crash and produce a dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2068577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068577] Re: [UBUNTU 24.04] Running sosreport causes the system to crash and produce a dump
** Package changed: linux (Ubuntu) => sosreport (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-z-systems Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068577 Title: [UBUNTU 24.04] Running sosreport causes the system to crash and produce a dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2068577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064321] Re: Power guest secure boot with key management: kernel portion
Hello, is there already a list of (kernel) commits that are required? (So that we can check whether they are incl. in the Ubuntu kernel or not; and in case not do the submissions to the Ubuntu kernel team.) ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064321 Title: Power guest secure boot with key management: kernel portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064345] Re: Power guest secure boot with key management: userspace portion
Since this is about a new ppc64el specific tool ("secvarctl", that does not yet
exists in LP),
I'll marked this ticket as temp. affecting "powerpc-utils", until we have a
first upload.
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
(unassigned)
** Package changed: linux (Ubuntu) => powerpc-utils (Ubuntu)
** Changed in: powerpc-utils (Ubuntu)
Assignee: (unassigned) => Patricia Domingues (patriciasd)
** Changed in: ubuntu-power-systems
Importance: Undecided => High
** Changed in: powerpc-utils (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064345
Title:
Power guest secure boot with key management: userspace portion
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064345/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064345] Re: Power guest secure boot with key management: userspace portion
I'm assuming that this is the upstream repository of 'secvarctl': https://github.com/open-power/secvarctl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064345 Title: Power guest secure boot with key management: userspace portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062556] Re: [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest!
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062556 Title: [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2062556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065579] Re: [UBUNTU 22.04] OS guest boot issues on 9p filesystem
Please let me jump in (for TZ reasons).
The patch "debian/patches/ubuntu/lp-2065579-9pfs-allow-sockets.patch"
(as always referenced in debin/changelog) that Sergio created and that
is incl. in the PPA build is this:
From: Sergio Durigan Junior
Date: Thu, 30 May 2024 16:45:56 -0400
Subject: hw/9pfs/9p-util.h: Also allow sockets to be opened
Forwarded: not-needed
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2065579
---
hw/9pfs/9p-util.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/9pfs/9p-util.h b/hw/9pfs/9p-util.h
index ff32179..a3df012 100644
--- a/hw/9pfs/9p-util.h
+++ b/hw/9pfs/9p-util.h
@@ -47,7 +47,8 @@ static inline int close_if_special_file(int fd)
close_preserve_errno(fd);
return -1;
}
-if (!S_ISREG(stbuf.st_mode) && !S_ISDIR(stbuf.st_mode)) {
+if (!S_ISREG(stbuf.st_mode) && !S_ISDIR(stbuf.st_mode)
+&& !S_ISSOCK(stbuf.st_mode)) {
error_report_once(
"9p: broken or compromised client detected; attempt to open "
"special file (i.e. neither regular file, nor directory)"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065579
Title:
[UBUNTU 22.04] OS guest boot issues on 9p filesystem
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2065579/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067355] Re: Update s390-tools to (currently latest) v2.33.1 in oracular
Test build is available in PPA lp2067355: https://launchpad.net/~fheimes/+archive/ubuntu/lp2067355 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067355 Title: Update s390-tools to (currently latest) v2.33.1 in oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2067355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067355] Re: Update s390-tools to (currently latest) v2.33.1 in oracular
** Patch added: "debdiff_s390-tools-signed_from_2.31.0-0ubuntu5_to_2.33.1-0ubuntu1.diff" https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/2067355/+attachment/5784042/+files/debdiff_s390-tools-signed_from_2.31.0-0ubuntu5_to_2.33.1-0ubuntu1.diff ** Changed in: s390-tools (Ubuntu) Status: New => In Progress ** Changed in: s390-tools-signed (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-z-systems Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067355 Title: Update s390-tools to (currently latest) v2.33.1 in oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2067355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067355] Re: Update s390-tools to (currently latest) v2.33.1 in oracular
** Attachment added: "debdiff_s390-tools_from_2.31.0-0ubuntu5_to_2.33.1-0ubuntu1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/2067355/+attachment/5784041/+files/debdiff_s390-tools_from_2.31.0-0ubuntu5_to_2.33.1-0ubuntu1.diff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067355 Title: Update s390-tools to (currently latest) v2.33.1 in oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2067355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067383] Re: [Ubuntu 24.04] hotplug of 68 or more cpus is making the guest shutoff!
** Summary changed: - [Ubuntu24.04] hotplug of 68 or more cpus is making the guest shutoff! + [Ubuntu 24.04] hotplug of 68 or more cpus is making the guest shutoff! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067383 Title: [Ubuntu 24.04] hotplug of 68 or more cpus is making the guest shutoff! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2067383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067383] Re: [Ubuntu24.04] hotplug of 68 or more cpus is making the guest shutoff!
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Changed in: qemu (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => (unassigned) ** Changed in: ubuntu-power-systems Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067383 Title: [Ubuntu24.04] hotplug of 68 or more cpus is making the guest shutoff! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2067383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044104] Re: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set
Okay, thanks Vineeth for jumping in! In other words this will become unblocked once we have s390-tools >= 2.33.0 in, which I am currently working on (v2.33.1 - based on LP#2067355). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044104 Title: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2044104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067355] [NEW] Update s390-tools to (currently latest) v2.33.1 in oracular
Public bug reported: There was recently a new s390-tools version published that comes with some new features and a tool, originally in C - now rewritten in Rust. This new s390-tools version 2.33.1 should be incl. in oracular, even if there might be another update. But it's good and reasonable to have this version in, to be able to test the changes and tools and to avoid that work piles up. https://github.com/ibm-s390-linux/s390-tools/releases/tag/v2.33.1 (https://github.com/ibm-s390-linux/s390-tools/releases/tag/v2.33.0) ** Affects: ubuntu-z-systems Importance: Medium Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Affects: s390-tools (Ubuntu) Importance: Medium Assignee: Frank Heimes (fheimes) Status: New ** Affects: s390-tools-signed (Ubuntu) Importance: Medium Assignee: Frank Heimes (fheimes) Status: New ** Tags: s390x ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Also affects: s390-tools-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => Medium ** Changed in: s390-tools (Ubuntu) Importance: Undecided => Medium ** Changed in: s390-tools-signed (Ubuntu) Importance: Undecided => Medium ** Changed in: s390-tools-signed (Ubuntu) Assignee: (unassigned) => Frank Heimes (fheimes) ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067355 Title: Update s390-tools to (currently latest) v2.33.1 in oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2067355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044104] Re: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set
Hi Peter, is this now incl. in s390-tools v2.33.0 https://github.com/ibm-s390-linux/s390-tools/releases/tag/v2.33.0 and what I read as: "chzdev: Add --is-owner to identify files created by zdev" ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044104 Title: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2044104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038583] Re: Turning COMPAT_32BIT_TIME off on s390x
Hi Stefan (in reply to LP comment #18: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038583/comments/18), this is now tracked here: LP#2067350 (https://bugs.launchpad.net/bugs/2067350) since it is a bit more effort than just removing libc6-s390 and libc6-dev-s390, due to their reverse dependencies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038583 Title: Turning COMPAT_32BIT_TIME off on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2038583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067350] [NEW] Removal of 31-bit (s390) glibc packages
Public bug reported: Last cycle there was the effort to turn off COMPAT_32BIT_TIME on s390x (but also on other architectures, LP#2038583). Based on this effort it was agreed to not only turn off 32-bit time but 32-bit (for the mainframe platform, that is technically 31-bit) entirely. Two major 31-bit “left-overs” for the mainframe platform are the 31-bit glibc packages (libc6-s390, libc6-dev-s390). This should be cleaned-up and these should now be removed (and their build disabled) to reach a clean 64-bit s390x system. But the reverse dependency situation is like follows: $ reverse-depends --list libc6-s390 -r oracular -a s390x gcc-snapshot lib32asan5 lib32asan6 lib32asan8 lib32atomic1 lib32gcc-s1 lib32gfortran5 lib32go14 lib32go16 lib32go19 lib32go21 lib32go22 lib32go23 lib32gomp1 lib32gphobos1 lib32gphobos2 lib32gphobos3 lib32gphobos4 lib32gphobos5 lib32gphobos76 lib32itm1 lib32objc4 lib32stdc++6 lib32stdc++6-10-dbg lib32stdc++6-11-dbg lib32stdc++6-12-dbg lib32stdc++6-13-dbg lib32stdc++6-14-dbg lib32stdc++6-9-dbg lib32ubsan1 lib32z1 libc6-dev-s390 oaklisp $ reverse-depends libc6-s390 -r oracular -a s390x Reverse-Depends === * gcc-snapshot * lib32asan5 * lib32asan6 * lib32asan8 * lib32atomic1 * lib32gcc-s1 * lib32gfortran5 * lib32go14 * lib32go16 * lib32go19 * lib32go21 * lib32go22 * lib32go23 * lib32gomp1 * lib32gphobos1 * lib32gphobos2 * lib32gphobos3 * lib32gphobos4 * lib32gphobos5 * lib32gphobos76 * lib32itm1 * lib32objc4 * lib32stdc++6 * lib32stdc++6-10-dbg * lib32stdc++6-11-dbg * lib32stdc++6-12-dbg * lib32stdc++6-13-dbg * lib32stdc++6-14-dbg * lib32stdc++6-9-dbg * lib32ubsan1 * lib32z1 * libc6-dev-s390 * oaklisp But since kernel dropped support for 31-bit (32-bit) executables, starting with Ubuntu kernel 6.8 (LP#2038583, esp. comment #7 and #11) these libraries should be removed, too. ** Affects: ubuntu-z-systems Importance: Undecided Status: New ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Tags: rls-oo-incoming s390 s390x ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Tags added: rls-oo-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067350 Title: Removal of 31-bit (s390) glibc packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2067350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2050017] Re: [24.04 FEAT] [SEC2339] HSM protected signing support for Apache httpd for openSSL 3.0 with PKCS #11 provider
Yes, I thought about https://launchpad.net/~ahasenack/+archive/ubuntu/apache2-modssl- provider-support/ But we can also copy it to another PPA or I can re-create it based on your, if you prefer not to leave yours. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2050017 Title: [24.04 FEAT] [SEC2339] HSM protected signing support for Apache httpd for openSSL 3.0 with PKCS #11 provider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2050017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059303 Title: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2059303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
Thank you Steffen once again! I'm updating the tags accordingly ... ** Tags removed: verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-focal verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059303 Title: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2059303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2050017] Re: [24.04 FEAT] [SEC2339] HSM protected signing support for Apache httpd for openSSL 3.0 with PKCS #11 provider
The IBM team agreed upon the proposal to let's go with the PPA solution for now, until upstream accepted (and reconsider in this case). (So I think I'm updating the status of this ticket to 'Opinion'.) ** Changed in: ubuntu-z-systems Status: Triaged => Opinion ** Changed in: apache2 (Ubuntu) Status: Triaged => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2050017 Title: [24.04 FEAT] [SEC2339] HSM protected signing support for Apache httpd for openSSL 3.0 with PKCS #11 provider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2050017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059303 Title: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2059303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045250] Re: pam_lastlog doesn't handle localtime_r related errors properly
Hello Boris, unfortunately no, not really any further actions - as of now. The problem is that bringing it into M, J and F would require a testplan, and with that a stable reproducer that we do not have (and couldn't find - even at looking at this bug in other distros). So it was first of all decided to pick it up for noble (since at that time this problem was looked at, noble was still in development). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045250 Title: pam_lastlog doesn't handle localtime_r related errors properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2045250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056173] Re: dotnet 8/s390x (8.0.2 runtime / 8.0.102 SDK) feedback
** Also affects: dotnet8 (Ubuntu) Importance: Undecided Status: New ** Changed in: dotnet8 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056173 Title: dotnet 8/s390x (8.0.2 runtime / 8.0.102 SDK) feedback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2056173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065579] Re: [UBUNTU 22.04] OS guest boot issues on 9p filesystem
** Package changed: linux (Ubuntu) => qemu (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: qemu (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065579 Title: [UBUNTU 22.04] OS guest boot issues on 9p filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2065579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064530] Re: Include support for .NET 8 for Ubuntu on Power
** Changed in: ubuntu-power-systems Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064530 Title: Include support for .NET 8 for Ubuntu on Power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056373] Re: Problems with HVCS and hotplugging
** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056373 Title: Problems with HVCS and hotplugging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062556] Re: [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest!
Many thanks for your confirmation Kowshik Jois. With that I'm updating the tags accordingly (and set them to verification done). ** Tags removed: verification-needed-noble-linux ** Tags added: verification-done-noble-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062556 Title: [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2062556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2050017] Re: [24.04 FEAT] [SEC2339] HSM protected signing support for Apache httpd for openSSL 3.0 with PKCS #11 provider
** Summary changed: - [FFe] [24.04 FEAT] [SEC2339] HSM protected signing support for Apache httpd for openSSL 3.0 with PKCS #11 provider + [24.04 FEAT] [SEC2339] HSM protected signing support for Apache httpd for openSSL 3.0 with PKCS #11 provider ** Description changed: - Feature Freeze Exception (FFe): - --- - - Since the work on this request may take a little longer and noble's FF is - today, this request got transferred into a feature freeze exception (FFe). - The driver for this is the need to update mod_ssl in Apache2 to support openssl 3.x providers, since engines are deprecated in openssl 3.x. This new functionality (openssl provider support) is required for the use case that one wants to protect the private key of a httpd server by using a PKCS#11 based (HSM based) private key for the server instead of using a clear key. This would subsequently open business opportunity esp. on the s390x platform. The diff/delta in the 2.5.x/trunk CHANGES file (https://github.com/apache/httpd/blob/trunk/CHANGES) is: " *) mod_ssl: Support loading certificates and private keys from the PKCS#11 OpenSSL engine. [Anderson Sasaki , Joe Orton] " In addition the reference to Revision 1914365 seems to be useful reference, that provides further details: https://svn.apache.org/viewvc?view=revision=1914365 Once backports for 2.4.x are available: - a test build in PPA will be done (and a build log can be provided) - install and upgrade tests will be done (and an install log can be provided) The new package should not break any other packages that depend on it, since there are no changes in the dependencies (or package meta data in general) expected. A description of a sample setup, incl. all affected components, can be taken from here: https://www.ibm.com/docs/en/linux-on-z?topic=linuxone-libp11-engine (The sample is based on RHEL, but except the patches discussed here, this generally applies to other distributions as well). 'Figure - 1' provides a graphical representation of the overall use case setup. The above sample setup does incl. test steps; look for 'Testing' --> 'Test with Apache web server' (Test uses "httpd -X" and "openssl s_client".) Once an Ubuntu based Apache 2.4.x test build for noble is available, and the logs (see above are available) the 'ubuntu-release' team can finally be subscribed. __ Enable an E2E use case that allows to configure an Apache webserver to protect its private keys with an HSM that is addressable via an PKCS #11 (signing) provider configured for an openSSL 3.0 library. Accepted for httpd > 2.4.58, see https://svn.apache.org/viewvc?view=revision=1914365 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2050017 Title: [24.04 FEAT] [SEC2339] HSM protected signing support for Apache httpd for openSSL 3.0 with PKCS #11 provider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2050017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Can we collaborate with Debian better?
There is a little bit more on "removing packages" here: https://wiki.ubuntu.com/UbuntuDevelopment/PackageArchive#Removing_Packages So it's actually a 'must' to have a LP bug for getting a package removed. BR, Frank On Sun, May 5, 2024 at 7:32 PM Simon Quigley wrote: > Hi Dima, > > As a Debian Developer myself, I understand your concerns. Processes in > this respect could be slightly better, but it also comes down to the > differences between the two distributions. More detailed responses inline. > > On 5/2/24 10:56 AM, Dima Kogan wrote: > > Hello. > > > > I'm a Debian developer, and contribute to Ubuntu only indirectly: by my > > contributions to Debian being automatically pulled into Ubuntu. But > > since Ubuntu has more users than Debian, most of MY users use the Ubuntu > > packages. So I'd like to talk about improving the links between the two > > projects. In particular: > > Ubuntu and Debian package maintenance responsibilities are slightly > different; in Ubuntu, members of the Core Developers team are > collectively responsible for the packages in the Main and Restricted > components, and Masters of the Universe are collectively responsible for > packages in the Universe and Multiverse. The ratio of "maintainers > holding responsibility":"packages to be maintained" is much lower in > Ubuntu than it is in Debian. > > Once a package has landed in the Ubuntu archive, Ubuntu Developers now > collectively hold responsibility for that package. We ease much of this > work by autosyncing packages without deltas to Ubuntu in the first half > of each cycle; that being said, we sometimes drive major transitions in > Ubuntu before Debian, to align with our release cycle. > > Many Ubuntu Developers (myself included) are trained to give as much > back to Debian as we possibly can. If we fix a package that both exists > in Debian and has the same bug, we are encouraged to send that fix > upstream to the Debian bug tracker (or upstream itself, or both) to > ensure less friction when we have to merge new changes from Debian. Some > teams within Ubuntu do not follow this process at all, but I would > consider them the exception rather than the rule. > > The Debian maintainers of a package are not responsible for how their > packages are used in Ubuntu, that's Ubuntu's responsibility. That being > said, it is best practice to collaborate as much as we reasonably can, > with the time we are given. > > > 1. Debian and Ubuntu both have separate bug trackers. But for most > > Ubuntu packages, there's no "Ubuntu" maintainer: there's just the > > indirect one from Debian. In this case (which is most packages), it's > > unhelpful for the Ubuntu bug tracker to exist as a separate thing. If > > it must exist as a separate thing, those bugs should be forwarded > > automatically to the Debian bug tracker. And updates (including > > status updates) should be ingested back into the Ubuntu tracker. For > > my packages I do try to manually look at the Ubuntu bug reports, but > > I have no rights to close those bugs on launchpad. Probably I can > > sign up somewhere, but as the DEBIAN developer, I shouldn't need to > > do that. > > I disagree with this approach. Ubuntu and Debian are not ABI-compatible; > Ubuntu has a slightly different toolchain than Debian, and there are > core differences in e.g. dpkg. Not all Ubuntu bugs are Debian bugs, not > all Ubuntu teams want their bugs sent up to Debian, and many Debian > Maintainers don't care about Ubuntu. This is a reality of maintaining > separate distributions. > > In some common cases, yes this seems reasonable, we should forward bugs > to Debian. That being said, the first step is making sure the bug > actually exists in the Debian-built version of the package, which is not > always the case. > > Generally, I do think we can be better about triaging our bugs and > sending what we can up to Debian. That being said, I disagree with the > solution of completely automating it. > > > 2. As I just discovered, when Ubuntu rebuilds the archive for a release, > > packages that FTBFS are silently dropped. There's no bug report on > > either of the two bug trackers. I'm upstream for a project that has > > been excluded from 24.04 because of this gap in the process. There > > really should be a bug report filed, so that the problem can be fixed > > before the release (what Debian does for their releases). And this > > should be filed on the Debian bug tracker, if that's where the > > maintenance happens. > > This entirely falls on the Ubuntu Archive Administrators. To my > understanding as an Ubuntu Developer, if we want a package removed, it > is best practice to either have a Debian removal bug or an Ubuntu > removal bug explaining the rationale. Whether this is enforced is up to > the Archive Administrator doing the removal, since the only known public > documentation says nothing about filing bugs: >
[Bug 2061913] Re: FTBFS ppc64el obj_basic_integration/TEST5 crashed
I've just found this statement at the upstream github project and want to reference the info here: https://github.com/pmem/pmdk " Experimental Support for PowerPC There is initial support for ppc64le processors provided. It is currently not validated nor maintained. Thus, this architecture should not be used in a production environment. The on-media pool layout is tightly attached to the page size of 64KiB used by default on ppc64le, so it is not interchangeable with different page sizes, includes those on other architectures. For more information on this port, contact Rajalakshmi Srinivasaraghavan (ra...@linux.ibm.com) or Lucas Magalhães (lucm...@gmail.com). " ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => bugproxy (bugproxy) ** Summary changed: - FTBFS ppc64el obj_basic_integration/TEST5 crashed + PMDK FTBFS on ppc64el obj_basic_integration/TEST5 crashed ** Tags added: reverse-proxy-bugzilla -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061913 Title: PMDK FTBFS on ppc64el obj_basic_integration/TEST5 crashed To manage notifications about this bug go to: https://bugs.launchpad.net/pmdk/+bug/2061913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064530] Re: Include support for .NET 8 for Ubuntu on Power
Hi Seth, this request came in via the Bugzilla-to-LP bridge, and the default for packages (if unknown to BZ, or for other reasons) is "linux (Ubuntu)". We (the PE IBM Squad) usually update this when we triage the incoming bugs - and I was a bit late (since we have a pub. holiday today), but already changed it in parallel when you've added your comment. I'm already in contact with the dotnet tool-chain team on this. And yes, it will be needed to get it into oracular first (before we can think of getting it into noble). ** Description changed: == Comment: #0 - JAMIE L. DOLAN - 2024-05-01 12:19:47 == This is a bug to track adding the feature of .NET 8 to Ubuntu 24.04 - This has already been added for s390x - - Customer survey showed strong interest in .NET on Linux on Power, having .NET on Ubuntu on Power will help in adoption of .NET on Power + - Customer survey showed strong interest in .NET on Linux on Power, having .NET on Ubuntu on Power will help in adoption of .NET on Power as well as pushing Ubuntu for Power. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064530 Title: Include support for .NET 8 for Ubuntu on Power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064530] Re: Include support for .NET 8 for Ubuntu on Power
** Also affects: dotnet8 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: dotnet8 (Ubuntu Oracular) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064530 Title: Include support for .NET 8 for Ubuntu on Power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2064530] Re: Include support for .NET 8 for Ubuntu on Power
** Package changed: linux (Ubuntu) => dotnet8 (Ubuntu) ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Changed in: dotnet8 (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => (unassigned) -- 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/2064530 Title: Include support for .NET 8 for Ubuntu on Power Status in The Ubuntu-power-systems project: New Status in dotnet8 package in Ubuntu: New Bug description: == Comment: #0 - JAMIE L. DOLAN - 2024-05-01 12:19:47 == This is a bug to track adding the feature of .NET 8 to Ubuntu 24.04 - This has already been added for s390x - Customer survey showed strong interest in .NET on Linux on Power, having .NET on Ubuntu on Power will help in adoption of .NET on Power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064530/+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
[Bug 2064530] Re: Include support for .NET 8 for Ubuntu on Power
** Package changed: linux (Ubuntu) => dotnet8 (Ubuntu) ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Changed in: dotnet8 (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064530 Title: Include support for .NET 8 for Ubuntu on Power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2016860] Re: Error/crash while trying to wipe disk during 23.04+ install
Based on the recent ISO, QA Tracker and installation tests around the 24.04 release, this issues got solved and it did not happened anymore with recent images, hence I'm closing this LP bug. ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released ** Changed in: subiquity Status: Fix Committed => Fix Released ** Changed in: subiquity (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2016860 Title: Error/crash while trying to wipe disk during 23.04+ install To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2016860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2009495] Re: [Ubuntu 22.04] smc_run does not work, libsmc-preload.so cannot be preloaded
** Changed in: ubuntu-z-systems Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2009495 Title: [Ubuntu 22.04] smc_run does not work, libsmc-preload.so cannot be preloaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2009495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
Hi @seth-arnold,
I am not in-depth familiar with security related updates (since they happen
rarely for me, and if private-security are handled by the security team anyway).
"
My assumption is that these package updates should be published first to
-updates for autopkgtest testing, and once they have passed testing and phased
to users, then we should republish these updates to -security so that they are
available to all users. Does this sound correct?
"
There are no autopkgtests (for historical reasons and since lot's of functions
in that package req. the hw to be configured in a certain way, which cannot
guaranteed by the build systems), but the packages get (and already got)
already manually tested upfront, with focus on the changes (according to test
plan in SRU justification).
"
This is much easier to execute if the updates have been built in a PPA with
only -security enabled, and not -updates. (The -security pocket is built with
only packages from -release and -security, not -updates.) Do packages built in
such a PPA exist?
"
I've now kicked off build in a -security only PPA here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp2059303-sec
(so yes, they build there, but it'll take a while until published)
"
The SRU workflow asks for packages to be either uploaded with dput to the queue
or debdiffs provided. I see some debdiffs here, but some additional work was
performed after most of the debdiffs were uploaded.
"
The changes are some broken URL references in some quilt patch headers, I've
fixed those.
"
Are the posted debdiffs something that the SRU team should work with? The
Ubuntu Sponsors team was added around three weeks ago, before much of the work
was done, it's entirely possible that this has fallen off their radar as a
result. (And, the general hustle of responding to the xz-utils issue, release
time goals, etc.)
"
I think the debdiffs should be taken (as usual).
It's difficult to get SRUs processed around release times.
One concern I have is that copying the packages might not work, since there is
a bootloader component that is signed, and the signing key is based on the
location where the package is build.
Hence a package build in PPA will be signed with the PPA key and not with the
official ('production') key
and so copying it over from PPA to archive will probably mess up things.
So I believe the debdiffs need to be the base for an upload (by a
sponsor), then build for the archives (that will ensure signing with the
proper key), then published on -proposed, verified there and then
eventually released.
(I'm attaching the debdiffs again, with fixed urls)
** Attachment added: "debdiffs.tgz"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/2059303/+attachment/5769649/+files/debdiffs.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059303
Title:
[UBUNTU 20.04] SE-tooling: New IBM host-key subject locality
(s390-tools)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2059303/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056485] Re: Behaviour of socat in Ubuntu 20.04 unexpected
With that I'm closing this LP bug by updating it to Won't Fix. (This does not mean that fixes will never be possible or done at all, 'Won't Fix' in this case indicates that the workaround / alternative fix was not desired, hence was not chosen; and it was taken in lieu of a better status.) ** Changed in: ubuntu-power-systems Status: In Progress => Won't Fix ** Changed in: socat (Ubuntu Focal) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056485 Title: Behaviour of socat in Ubuntu 20.04 unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Touch-packages] [Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image
** Changed in: ubuntu-z-systems
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2060311
Title:
Setting "optional: true" to overcome he timeout "Job systemd-networkd-
wait-online" does no longer work with latest noble image
Status in Netplan:
In Progress
Status in Ubuntu on IBM z Systems:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in netplan.io source package in Noble:
Fix Released
Status in systemd source package in Noble:
Invalid
Bug description:
Especially on s390x (but not limited to s390x) it's often the case that a
system has network devices that are not necessarily connected during boot-up
and one gets such a 2 min timeout:
"Job systemd-networkd-wait-online. Start running (1min 59s / no limit)"
In the past I could avoid that by setting "optional: true" post-install (no
perfect, but worked),
but this does no longer seem to work using the latest noble ISO image (Apr
5th).
Setting 'optional: true' in /etc/netplan/50-cloud-init.yaml looks like
this for me:
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
enP1p0s0:
optional: true
dhcp4: true
enP1p0s0d1:
optional: true
dhcp4: true
enP2p0s0:
optional: true
dhcp4: true
enP2p0s0d1:
optional: true
dhcp4: true
encc000: {}
version: 2
vlans:
encc000.2653:
addresses:
- 10.11.12.15/24
gateway4: 10.11.12.1
id: 2653
link: encc000
nameservers:
addresses:
- 10.11.12.1
... can be set fine (also --dry-run does not moan, except about
dhcp4).
This worked in the past on noble, but also on older Ubuntu releases
like jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2060311/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image
** Changed in: ubuntu-z-systems Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060311 Title: Setting "optional: true" to overcome he timeout "Job systemd-networkd- wait-online" does no longer work with latest noble image To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2060311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056485] Re: Behaviour of socat in Ubuntu 20.04 unexpected
Hello @Jamie, thanks for your answer and feedback. Your decision is understood. @Robie Based on this, there is no need to follow the alternative approach anymore, and I think this SRU request can be recalled and I would like to ask you to reject socat from the focal unapproved queue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056485 Title: Behaviour of socat in Ubuntu 20.04 unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2062556] Re: [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest!
I just had a look at noble's master-next tree:
$ git remote get-url origin
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble
$ git branch
* master-next
and found that commit 19c1ceeca8ed is already applied:
$ git log --oneline | grep -n "block: Fix page refcounts for unaligned buffers
in __bio_release_pages"
300:19c1ceeca8ed block: Fix page refcounts for unaligned buffers in
__bio_release_pages()
but not yet tagged with (incl. in) any version:
$ git tag --contains 19c1ceeca8ed
$
This is probably because it just came in via upstream stable updates:
$ git show 19c1ceeca8ed | sed '/^diff --git/q'
commit 19c1ceeca8ed31d207859e659482ee83ea1959f5
Author: Tony Battersby
Date: Thu Feb 29 13:08:09 2024 -0500
block: Fix page refcounts for unaligned buffers in __bio_release_pages()
BugLink: https://bugs.launchpad.net/bugs/2060531
[ Upstream commit 38b43539d64b2fa020b3b9a752a986769f87f7a6 ]
Fix an incorrect number of pages being released for buffers that do not
start at the beginning of a page.
Fixes: 1b151e2435fc ("block: Remove special-casing of compound pages")
Cc: sta...@vger.kernel.org
Signed-off-by: Tony Battersby
Tested-by: Greg Edwards
Link:
https://lore.kernel.org/r/86e592a9-98d4-4cff-a646-0c0084328...@cybernetics.com
Signed-off-by: Jens Axboe
Signed-off-by: Sasha Levin
Signed-off-by: Paolo Pisati
diff --git a/block/bio.c b/block/bio.c
And since the lastest tagged Ubuntu kernel version in master-next is:
Ubuntu-6.8.0-31.31
$ git log --oneline | grep -n $(git describe --tags --abbrev=0)
1170:7fdb45c9bbbc (tag: Ubuntu-6.8.0-31.31) UBUNTU: Ubuntu-6.8.0-31.31
commit 19c1ceeca8ed will be automatically part of the next/upcoming
Ubuntu kernel (> Ubuntu-6.8.0-31.31).
With that I'm updating the status of this bug to Fix Committed.
** Changed in: ubuntu-power-systems
Status: New => Fix Committed
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
(unassigned)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-power-systems
Importance: Undecided => High
--
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/2062556
Title:
[Ubuntu-24.04] Hugepage memory is not getting released even after
destroying the guest!
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Bug description:
---Problem Description---
Hugepages memory is not getting released even after destroying the guest
Machine Type = P10 Denali LPAR
---uname output---
Linux ubuntu2404lp3 6.8.0-22-generic #22-Ubuntu SMP Thu Apr 4 22:47:57 UTC
2024 ppc64le ppc64le ppc64le GNU/Linux
---Steps to Reproduce---
1. Create a guest which is backed by hugepages.
2. Destroy the guest
3. execute "free -h" or "cat /proc/meminfo" to see that Hugepage memory is
still getting held.
HugePages_Total: 20480
HugePages_Free:20419
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize: 2048 kB
Hugetlb:41943040 kB
DirectMap4k: 0 kB
DirectMap64k:52428800 kB
DirectMap2M: 0 kB
DirectMap1G: 0 kB
root@ubuntu2404lp3:~# virsh list --all
Id Name State
---
-ramlp2g1 shut off
-ramlp2g2 shut off
-ramlp2g3 shut off
-ramlp3g3 shut off
root@ubuntu2404lp3:~# free -h
totalusedfree shared buff/cache
available
Mem:48Gi43Gi 4.6Gi 2.6Mi 277Mi
4.6Gi
Swap: 8.0Gi 243Mi 7.8Gi
root@ubuntu2404lp3:~#
This is an issue created by commit 1b151e2435fc ("block: Remove
special-casing of compound pages") that moved the direct-io hugetlb handling
from compound pages to folios.
Following commit has been proposed and merged into 6.9-rc1 which fixes this
issue.
38b43539d64b2fa020b3b9a752a986769f87f7a6("block: Fix page refcounts for
unaligned buffers in __bio_release_pages()")
So the same needs to be backported to the Ubuntu24.04 kernel as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2062556/+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
[Bug 2062556] Re: [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest!
I just had a look at noble's master-next tree:
$ git remote get-url origin
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble
$ git branch
* master-next
and found that commit 19c1ceeca8ed is already applied:
$ git log --oneline | grep -n "block: Fix page refcounts for unaligned buffers
in __bio_release_pages"
300:19c1ceeca8ed block: Fix page refcounts for unaligned buffers in
__bio_release_pages()
but not yet tagged with (incl. in) any version:
$ git tag --contains 19c1ceeca8ed
$
This is probably because it just came in via upstream stable updates:
$ git show 19c1ceeca8ed | sed '/^diff --git/q'
commit 19c1ceeca8ed31d207859e659482ee83ea1959f5
Author: Tony Battersby
Date: Thu Feb 29 13:08:09 2024 -0500
block: Fix page refcounts for unaligned buffers in __bio_release_pages()
BugLink: https://bugs.launchpad.net/bugs/2060531
[ Upstream commit 38b43539d64b2fa020b3b9a752a986769f87f7a6 ]
Fix an incorrect number of pages being released for buffers that do not
start at the beginning of a page.
Fixes: 1b151e2435fc ("block: Remove special-casing of compound pages")
Cc: sta...@vger.kernel.org
Signed-off-by: Tony Battersby
Tested-by: Greg Edwards
Link:
https://lore.kernel.org/r/86e592a9-98d4-4cff-a646-0c0084328...@cybernetics.com
Signed-off-by: Jens Axboe
Signed-off-by: Sasha Levin
Signed-off-by: Paolo Pisati
diff --git a/block/bio.c b/block/bio.c
And since the lastest tagged Ubuntu kernel version in master-next is:
Ubuntu-6.8.0-31.31
$ git log --oneline | grep -n $(git describe --tags --abbrev=0)
1170:7fdb45c9bbbc (tag: Ubuntu-6.8.0-31.31) UBUNTU: Ubuntu-6.8.0-31.31
commit 19c1ceeca8ed will be automatically part of the next/upcoming
Ubuntu kernel (> Ubuntu-6.8.0-31.31).
With that I'm updating the status of this bug to Fix Committed.
** Changed in: ubuntu-power-systems
Status: New => Fix Committed
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
(unassigned)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-power-systems
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062556
Title:
[Ubuntu-24.04] Hugepage memory is not getting released even after
destroying the guest!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2062556/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2062556] Re: [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest!
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
--
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/2062556
Title:
[Ubuntu-24.04] Hugepage memory is not getting released even after
destroying the guest!
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
---Problem Description---
Hugepages memory is not getting released even after destroying the guest
Machine Type = P10 Denali LPAR
---uname output---
Linux ubuntu2404lp3 6.8.0-22-generic #22-Ubuntu SMP Thu Apr 4 22:47:57 UTC
2024 ppc64le ppc64le ppc64le GNU/Linux
---Steps to Reproduce---
1. Create a guest which is backed by hugepages.
2. Destroy the guest
3. execute "free -h" or "cat /proc/meminfo" to see that Hugepage memory is
still getting held.
HugePages_Total: 20480
HugePages_Free:20419
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize: 2048 kB
Hugetlb:41943040 kB
DirectMap4k: 0 kB
DirectMap64k:52428800 kB
DirectMap2M: 0 kB
DirectMap1G: 0 kB
root@ubuntu2404lp3:~# virsh list --all
Id Name State
---
-ramlp2g1 shut off
-ramlp2g2 shut off
-ramlp2g3 shut off
-ramlp3g3 shut off
root@ubuntu2404lp3:~# free -h
totalusedfree shared buff/cache
available
Mem:48Gi43Gi 4.6Gi 2.6Mi 277Mi
4.6Gi
Swap: 8.0Gi 243Mi 7.8Gi
root@ubuntu2404lp3:~#
This is an issue created by commit 1b151e2435fc ("block: Remove
special-casing of compound pages") that moved the direct-io hugetlb handling
from compound pages to folios.
Following commit has been proposed and merged into 6.9-rc1 which fixes this
issue.
38b43539d64b2fa020b3b9a752a986769f87f7a6("block: Fix page refcounts for
unaligned buffers in __bio_release_pages()")
So the same needs to be backported to the Ubuntu24.04 kernel as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2062556/+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
[Bug 2062556] Re: [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest!
** Also affects: ubuntu-power-systems Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062556 Title: [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2062556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2050019] Re: [24.04 FEAT] [SEC2353] zcrypt: extend error recovery to deal with device scans
** Changed in: ubuntu-z-systems Status: In Progress => Fix Released -- 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/2050019 Title: [24.04 FEAT] [SEC2353] zcrypt: extend error recovery to deal with device scans Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: The error recovery of a crypto request currently fails if a device is not available or the device is not completely setup and bound if the device has been discovered due to a bus scan. If, during request handling, a device is lost and a bus scan is triggered the DD must wait for the bus scan (including the device binding) to complete before giving up on reties. This item is important to support life guest relocation where the APQN sets on the source and target guests differ. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2050019/+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
[Bug 2050019] Re: [24.04 FEAT] [SEC2353] zcrypt: extend error recovery to deal with device scans
** Changed in: ubuntu-z-systems Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2050019 Title: [24.04 FEAT] [SEC2353] zcrypt: extend error recovery to deal with device scans To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2050019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2051835] Re: [24.04 FEAT] Memory hotplug vmem pages (s390x)
** Changed in: ubuntu-z-systems Status: In Progress => Fix Released -- 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/2051835 Title: [24.04 FEAT] Memory hotplug vmem pages (s390x) Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: The current s390 specific memory hotplug backend allocates 'struct page' management structures for all standby memory regions, when those standby regions are detected at ipl time. The reason for this is, that setting standby online memory is supposed to succeed especially in memory constrained environments, since lack of free memory is likely the reason why additional memory is brought online. If in such cases 'struct pages' would have to be allocated before memory could be brought up, this would likely fail, and contradict the whole rationale of memory hotplug. However pre-allocating memory for 'struct pages' comes with the downside that for highly unbalanced ratios of online/standby memory a system might even fail to ipl, because there is not enough memory available for all possible struct pages which are required for standby memory. The idea is to improve the situation: when standby memory is brought online, the memory for struct pages (and maybe other management structures) required for this new memory area should be taken from the online memory, instead of pre-allocating them. This would solve the problems with unbalanced ratios as described above. Note: there are intentions to tell customers that they should always define the maximum size of standby memory for their LPAR activation profiles. This would allow for maximum flexibility for all LPARs during runtime, given that the amount of standby memory cannot be changed during runtime. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2051835/+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
[Bug 2051835] Re: [24.04 FEAT] Memory hotplug vmem pages (s390x)
** Changed in: ubuntu-z-systems Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051835 Title: [24.04 FEAT] Memory hotplug vmem pages (s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2051835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
I've noticed that Vasily's commit has meanwhile landed in linux-next, so I took it from there and applied it to noble master-next, but it failed due to changed context. Hence I did a bit of backporting work and got now it in. I triggered appropriate kernel test builds here: https://launchpad.net/~fheimes/+archive/ubuntu/lp2060217 -- 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/2060217 Title: NFSv4 fails to mount in noble/s390x Status in Release Notes for Ubuntu: New Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Triaged Status in nfs-utils package in Ubuntu: Invalid Bug description: https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/s390x Looks like it has been failing for a long time already. Log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/s390x/n/nfs-utils/20240404_145924_ef255@/log.gz 339s autopkgtest [14:41:04]: test local-server-client: [--- 340s Killed 340s autopkgtest [14:41:05]: test process requested reboot with marker boot1 364s autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds... 372s FAIL: nfs_home not mounted 373s autopkgtest [14:41:38]: test local-server-client: ---] 373s local-server-client FAIL non-zero exit status 1 and 934s autopkgtest [14:50:59]: test kerberos-mount: [--- 935s Initializing database '/var/lib/krb5kdc/principal' for realm 'DEP8', 935s master key name 'K/M@DEP8' 935s Authenticating as principal root/admin@DEP8 with password. 935s Principal "nfs/nfs-server.dep8@DEP8" created. 935s Authenticating as principal root/admin@DEP8 with password. 935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 935s Authenticating as principal root/admin@DEP8 with password. 935s Principal "host/nfs-server.dep8@DEP8" created. 935s Authenticating as principal root/admin@DEP8 with password. 935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 936s exporting *:/storage 938s mount.nfs: mount system call failed for /mnt 938s umount: /mnt: not mounted. 938s autopkgtest [14:51:02]: test kerberos-mount: ---] 939s kerberos-mount FAIL non-zero exit status 32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2060217/+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
[Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
I've noticed that Vasily's commit has meanwhile landed in linux-next, so I took it from there and applied it to noble master-next, but it failed due to changed context. Hence I did a bit of backporting work and got now it in. I triggered appropriate kernel test builds here: https://launchpad.net/~fheimes/+archive/ubuntu/lp2060217 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060217 Title: NFSv4 fails to mount in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062118] Re: autopkgtests fail on s390x (segfault)
Is it know if 'Test: trace pid events filter' also ended up in a segfault on earlier versions, e.g. 1.7.0-1 / mantic? (Probably not, looks like the test suite is only triggered during build starting with 1.8.0-1ubuntu1 / noble...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062118 Title: autopkgtests fail on s390x (segfault) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2062118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062118] Re: autopkgtests fail on s390x (segfault)
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => bugproxy (bugproxy) ** Tags added: reverse-proxy-bugzilla -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062118 Title: autopkgtests fail on s390x (segfault) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2062118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
** Description changed: SRU Justification: [ Impact ] * Symptom: * There is an issue with the Secure Execution (SE) tooling, especially the new IBM host-key subject locality, that leads to the fact that on April 24 (z15) / March 29 (z16) users will notice that the tooling for Secure execution will no longer detect that the provided IBM signing key for that generation is a valid IBM signing key. * The error message will contain "no IBM signing key found" or similar. The respective tool will reject creating an encrypted request/image as it could not verify the host-key for its validity. * This affects the genprotimg, pvattest, and pvsecret tools. (Please notice that these tools got introduced over time with different s390-tools versions that belong to different Ubuntu releases). * Problem: * The new IBM signing keys no longer contain 'Poughkeepsie' as 'subject locality' and 'Armonk' is used. * The SE tooling checks, beside other things, for the subject in the IBM signing key. * If the subject is not the expected one, the certificate is not recognized as a valid IBM signing key. And without a valid IBM signing key, the host-key verification cannot succeed and users cannot build trustable SE images and attestation or add-secret requests. * Solution: * Mitigations are available upstream. * The fixes allow Armonk as additional locality in the subject and allow potential mismatches in the locality of revocation list or host-key issuer subject that may still contain Poughkeepsie instead of Armonk. [ Test Plan ] * The testing is required for all three affected tools: genprotimg, pvattest, and pvsecret - * Obtain a (z15) Host-key document e.g. via the official channel -see: https://www.ibm.com/docs/en/linux-on-systems?topic=execution-obtain-host-key-document + * Obtain a (z15) Host-key document e.g. via the official channel + see: https://www.ibm.com/docs/en/linux-on-systems?topic=execution-obtain-host-key-document - * Get a signing key (z15) + intermediate certificate -see: https://www.ibm.com/docs/en/linux-on-systems?topic=execution-verify-host-key-document + * Get a signing key (z15) + intermediate certificate + see: https://www.ibm.com/docs/en/linux-on-systems?topic=execution-verify-host-key-document - * (optional) verify that the signing key is a new one -check for: Locality Armonk -$ openssl x509 -text -in international_business_machines_corporation.crt | grep Subject -Subject: C = US, ST = New York, L = Armonk, O = International Business Machines Corporation, OU = IBM Z Host Key Signing Service, CN = International Business Machines Corporation -Here "L" **must** be Armonk, and not Poughkeepsie! + * (optional) verify that the signing key is a new one + check for: Locality Armonk + $ openssl x509 -text -in international_business_machines_corporation.crt | grep Subject + Subject: C = US, ST = New York, L = Armonk, O = International Business Machines Corporation, OU = IBM Z Host Key Signing Service, CN = International Business Machines Corporation + Here "L" **must** be Armonk, and not Poughkeepsie! - * Run the tools (if available, depends on the s390-tools version): -The fixed tools will accept the cert chain and exit with exit code 0 -and the output generated. -The non-fixed will print n error message, abort, and report exit != 0 + * Run the tools (if available, depends on the s390-tools version): + The fixed tools will accept the cert chain and exit with exit code 0 + and the output generated. + The non-fixed will print n error message, abort, and report exit != 0 - * $ genprotimg: genprotimg -o tmp -i /boot/vmlinuz-$(uname -r) -k ~/hostkey.crt --cert ~/international_business_machines_corporation.crt --cert ~/DigiCertCA.crt -# BEFORE_FIX: -Failed to verify host-key document: please specify at least one IBM Z signing key -# AFTER_FIX: -# exit code 0 + * $ genprotimg: genprotimg -o tmp -i /boot/vmlinuz-$(uname -r) -k ~/hostkey.crt --cert ~/international_business_machines_corporation.crt --cert ~/DigiCertCA.crt + # BEFORE_FIX: + Failed to verify host-key document: please specify at least one IBM Z signing key + # AFTER_FIX: + # exit code 0 - * $ pvattest create -VVV -o tmp --arpk arpk -k ~/hostkey.crt --cert ~/international_business_machines_corporation.crt --cert ~/DigiCertCA.crt -# BEFORE_FIX: -ERROR: Creating the attestation request failed: -Specify at least one IBM Z signing key -# AFTER_FIX: -# exit code 0 + * $ pvattest create -VVV -o tmp --arpk arpk -k ~/hostkey.crt --cert ~/international_business_machines_corporation.crt --cert ~/DigiCertCA.crt + # BEFORE_FIX: + ERROR: Creating the attestation request failed: +
[Bug 2048917] Re: [needs-packaging] Intel Integrated Performance Primitives - ipp-crypto
** Also affects: ipp-crypto (Ubuntu) Importance: Undecided Status: New ** Changed in: ipp-crypto (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048917 Title: [needs-packaging] Intel Integrated Performance Primitives - ipp-crypto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2048917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
Cool, thanks a lot Steffen! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059303 Title: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2059303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Touch-packages] [Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image
I gave ~ppa5 a try on my s390x system.
If I set all interfaces to "optional: true" (incl. encc000), but except
encc000.2653, I don't face the timeout anymore. But if I UNset
"optional: true" for encc000 on top, I tap into the timeout again.
In the past it was okay to NOT have "optional: true" set for both:
encc000 and encc000.2653 (and I found that logical, since both
interfaces are needed in a VLAN context).
Knowing now what's missing, I could live with that (even if it's a
change in behavior).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2060311
Title:
Setting "optional: true" to overcome he timeout "Job systemd-networkd-
wait-online" does no longer work with latest noble image
Status in Netplan:
In Progress
Status in Ubuntu on IBM z Systems:
New
Status in netplan.io package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Status in netplan.io source package in Noble:
Confirmed
Status in systemd source package in Noble:
Confirmed
Bug description:
Especially on s390x (but not limited to s390x) it's often the case that a
system has network devices that are not necessarily connected during boot-up
and one gets such a 2 min timeout:
"Job systemd-networkd-wait-online. Start running (1min 59s / no limit)"
In the past I could avoid that by setting "optional: true" post-install (no
perfect, but worked),
but this does no longer seem to work using the latest noble ISO image (Apr
5th).
Setting 'optional: true' in /etc/netplan/50-cloud-init.yaml looks like
this for me:
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
enP1p0s0:
optional: true
dhcp4: true
enP1p0s0d1:
optional: true
dhcp4: true
enP2p0s0:
optional: true
dhcp4: true
enP2p0s0d1:
optional: true
dhcp4: true
encc000: {}
version: 2
vlans:
encc000.2653:
addresses:
- 10.11.12.15/24
gateway4: 10.11.12.1
id: 2653
link: encc000
nameservers:
addresses:
- 10.11.12.1
... can be set fine (also --dry-run does not moan, except about
dhcp4).
This worked in the past on noble, but also on older Ubuntu releases
like jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2060311/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image
I gave ~ppa5 a try on my s390x system. If I set all interfaces to "optional: true" (incl. encc000), but except encc000.2653, I don't face the timeout anymore. But if I UNset "optional: true" for encc000 on top, I tap into the timeout again. In the past it was okay to NOT have "optional: true" set for both: encc000 and encc000.2653 (and I found that logical, since both interfaces are needed in a VLAN context). Knowing now what's missing, I could live with that (even if it's a change in behavior). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060311 Title: Setting "optional: true" to overcome he timeout "Job systemd-networkd- wait-online" does no longer work with latest noble image To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2060311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
Marc and me, we had a side discussion and finally found the missing commits and have a proper build for focal. The build is available here: https://launchpad.net/~fheimes/+archive/ubuntu/lp205930 and the debdiff(s) attached. ** Attachment added: "debdiff_focal.tgz" https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/2059303/+attachment/5766321/+files/debdiff_focal.tgz ** Changed in: s390-tools (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: s390-tools-signed (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059303 Title: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2059303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
Hi Marc, I've added f5744b95db9, but I unfortunately still get the build errors: https://launchpadlibrarian.net/724893134/buildlog_ubuntu-focal-s390x.s390-tools_2.12.0-0ubuntu3.9_BUILDING.txt.gz (search for "error:") -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059303 Title: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2059303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
** Description changed: SRU Justification: [ Impact ] - * Symptom: + * Symptom: -* There is an issue with the Secure Execution (SE) tooling, - especially the new IBM host-key subject locality, - that leads to the fact that on April 24 (z15) / March 29 (z16) - users will notice that the tooling for Secure execution will no - longer detect that the provided IBM signing key for that generation - is a valid IBM signing key. + * There is an issue with the Secure Execution (SE) tooling, + especially the new IBM host-key subject locality, + that leads to the fact that on April 24 (z15) / March 29 (z16) + users will notice that the tooling for Secure execution will no + longer detect that the provided IBM signing key for that generation + is a valid IBM signing key. -* The error message will contain "no IBM signing key found" or similar. - The respective tool will reject creating an encrypted request/image - as it could not verify the host-key for its validity. + * The error message will contain "no IBM signing key found" or similar. + The respective tool will reject creating an encrypted request/image + as it could not verify the host-key for its validity. -* This affects the genprotimg, pvattest, and pvsecret tools. - (Please notice that these tools got introduced over time with different - s390-tools versions that belong to different Ubuntu releases). + * This affects the genprotimg, pvattest, and pvsecret tools. + (Please notice that these tools got introduced over time with different + s390-tools versions that belong to different Ubuntu releases). - * Problem: + * Problem: -* The new IBM signing keys no longer contain 'Poughkeepsie' as - 'subject locality' and 'Armonk' is used. + * The new IBM signing keys no longer contain 'Poughkeepsie' as + 'subject locality' and 'Armonk' is used. -* The SE tooling checks, beside other things, for the subject in the - IBM signing key. + * The SE tooling checks, beside other things, for the subject in the + IBM signing key. -* If the subject is not the expected one, the certificate is not - recognized as a valid IBM signing key. - And without a valid IBM signing key, the host-key verification - cannot succeed and users cannot build trustable SE images and - attestation or add-secret requests. + * If the subject is not the expected one, the certificate is not + recognized as a valid IBM signing key. + And without a valid IBM signing key, the host-key verification + cannot succeed and users cannot build trustable SE images and + attestation or add-secret requests. - * Solution: + * Solution: -* Mitigations are available upstream. + * Mitigations are available upstream. -* The fixes allow Armonk as additional locality in the subject - and allow potential mismatches in the locality of revocation list - or host-key issuer subject that may still contain Poughkeepsie - instead of Armonk. + * The fixes allow Armonk as additional locality in the subject + and allow potential mismatches in the locality of revocation list + or host-key issuer subject that may still contain Poughkeepsie + instead of Armonk. [ Test Plan ] - * + * The testing is required for all three affected tools: + genprotimg, pvattest, and pvsecret - * The testing is required for all three affected tools: -genprotimg, pvattest, and pvsecret + * Obtain a (z15) Host-key document e.g. via the official channel +see: https://www.ibm.com/docs/en/linux-on-systems?topic=execution-obtain-host-key-document - * Without the fixed code, but with the new IBM signing keys -(that have 'Armonk' as 'subject locality'), users will get a msgs like: -"no IBM signing key found" -and the validation will fail. + * Get a signing key (z15) + intermediate certificate +see: https://www.ibm.com/docs/en/linux-on-systems?topic=execution-verify-host-key-document - * With the patches included, the validation will succeed. + * (optional) verify that the signing key is a new one +check for: Locality Armonk +$ openssl x509 -text -in international_business_machines_corporation.crt | grep Subject +Subject: C = US, ST = New York, L = Armonk, O = International Business Machines Corporation, OU = IBM Z Host Key Signing Service, CN = International Business Machines Corporation +Here "L" **must** be Armonk, and not Poughkeepsie! + + * Run the tools (if available, depends on the s390-tools version): +The fixed tools will accept the cert chain and exit with exit code 0 +and the output generated. +The non-fixed will print n error message, abort, and report exit != 0 + + * $ genprotimg: genprotimg -o tmp -i /boot/vmlinuz-$(uname -r) -k ~/hostkey.crt --cert
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
For focal the commit d14e7593cc6
(https://github.com/ibm-s390-linux/s390-tools/commit/d14e7593cc6380911ca42b09e11c53477ae13d5c)
does not properly build and the logs show a few errors:
https://launchpadlibrarian.net/723098720/buildlog_ubuntu-focal-s390x.s390-tools_2.12.0-0ubuntu3.8_BUILDING.txt.gz
(search for "error:")
"
utils/crypto.c: In function ‘x509_armonk_locality_fixup’:
utils/crypto.c:770:22: error: passing argument 1 of ‘X509_NAME_dup’ discards
‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]
770 | ret = X509_NAME_dup(name);
| ^~~~
In file included from /usr/include/openssl/pem.h:17,
from utils/crypto.c:17:
/usr/include/openssl/x509.h:482:12: note: expected ‘X509_NAME *’ {aka ‘struct
X509_name_st *’} but argument is of type ‘const X509_NAME *’ {aka ‘const struct
X509_name_st *’}
482 | X509_NAME *X509_NAME_dup(X509_NAME *xn);
|^
utils/crypto.c: In function ‘quirk_X509_STORE_ctx_get1_crls’:
utils/crypto.c:888:8: error: implicit declaration of function
‘Pv_X509_STORE_CTX_get1_crls’; did you mean ‘X509_STORE_CTX_get1_crls’?
[-Werror=implicit-function-declaration]
888 | ret = Pv_X509_STORE_CTX_get1_crls(ctx, subject);
|^~~
|X509_STORE_CTX_get1_crls
utils/crypto.c:888:8: error: nested extern declaration of
‘Pv_X509_STORE_CTX_get1_crls’ [-Werror=nested-externs]
utils/crypto.c:888:6: error: assignment to ‘STACK_OF_X509_CRL_autoptr’ {aka
‘struct stack_st_X509_CRL *’} from ‘int’ makes pointer from integer without a
cast [-Werror=int-conversion]
888 | ret = Pv_X509_STORE_CTX_get1_crls(ctx, subject);
| ^
utils/crypto.c:902:7: error: assignment to ‘STACK_OF_X509_CRL_autoptr’ {aka
‘struct stack_st_X509_CRL *’} from ‘int’ makes pointer from integer without a
cast [-Werror=int-conversion]
902 | ret = Pv_X509_STORE_CTX_get1_crls(ctx, fixed_subject);
| ^
utils/crypto.c:913:7: error: assignment to ‘STACK_OF_X509_CRL_autoptr’ {aka
‘struct stack_st_X509_CRL *’} from ‘int’ makes pointer from integer without a
cast [-Werror=int-conversion]
913 | ret = Pv_X509_STORE_CTX_get1_crls(ctx, fixed_subject);
| ^
utils/crypto.c:925:6: error: assignment to ‘STACK_OF_X509_CRL_autoptr’ {aka
‘struct stack_st_X509_CRL *’} from ‘int’ makes pointer from integer without a
cast [-Werror=int-conversion]
925 | ret = Pv_X509_STORE_CTX_get1_crls(ctx, fixed_subject);
| ^
"
and
"
utils/crypto.c: In function ‘x509_armonk_locality_fixup’:
utils/crypto.c:770:22: error: passing argument 1 of ‘X509_NAME_dup’ discards
‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]
770 | ret = X509_NAME_dup(name);
| ^~~~
In file included from /usr/include/openssl/pem.h:17,
from utils/crypto.c:17:
/usr/include/openssl/x509.h:482:12: note: expected ‘X509_NAME *’ {aka ‘struct
X509_name_st *’} but argument is of type ‘const X509_NAME *’ {aka ‘const struct
X509_name_st *’}
482 | X509_NAME *X509_NAME_dup(X509_NAME *xn);
|^
utils/crypto.c: In function ‘quirk_X509_STORE_ctx_get1_crls’:
utils/crypto.c:888:8: error: implicit declaration of function
‘Pv_X509_STORE_CTX_get1_crls’; did you mean ‘X509_STORE_CTX_get1_crls’?
[-Werror=implicit-function-declaration]
888 | ret = Pv_X509_STORE_CTX_get1_crls(ctx, subject);
|^~~
|X509_STORE_CTX_get1_crls
utils/crypto.c:888:8: error: nested extern declaration of
‘Pv_X509_STORE_CTX_get1_crls’ [-Werror=nested-externs]
utils/crypto.c:888:6: error: assignment to ‘STACK_OF_X509_CRL_autoptr’ {aka
‘struct stack_st_X509_CRL *’} from ‘int’ makes pointer from integer without a
cast [-Werror=int-conversion]
888 | ret = Pv_X509_STORE_CTX_get1_crls(ctx, subject);
| ^
utils/crypto.c:902:7: error: assignment to ‘STACK_OF_X509_CRL_autoptr’ {aka
‘struct stack_st_X509_CRL *’} from ‘int’ makes pointer from integer without a
cast [-Werror=int-conversion]
902 | ret = Pv_X509_STORE_CTX_get1_crls(ctx, fixed_subject);
| ^
utils/crypto.c:913:7: error: assignment to ‘STACK_OF_X509_CRL_autoptr’ {aka
‘struct stack_st_X509_CRL *’} from ‘int’ makes pointer from integer without a
cast [-Werror=int-conversion]
913 | ret = Pv_X509_STORE_CTX_get1_crls(ctx, fixed_subject);
| ^
utils/crypto.c:925:6: error: assignment to ‘STACK_OF_X509_CRL_autoptr’ {aka
‘struct stack_st_X509_CRL *’} from ‘int’ makes pointer from integer without a
cast [-Werror=int-conversion]
925 | ret = Pv_X509_STORE_CTX_get1_crls(ctx, fixed_subject);
| ^
utils/crypto.c: In function ‘x509_armonk_locality_fixup’:
utils/crypto.c:770:22: error: passing argument 1 of ‘X509_NAME_dup’ discards
‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]
770 | ret = X509_NAME_dup(name);
| ^~~~
In file included
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
s390-tools and s390-tools-signed debdiffs for 22.04/jammy ** Attachment added: "debdiff_jammy.tgz" https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/2059303/+attachment/5765796/+files/debdiff_jammy.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059303 Title: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2059303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
Hi Steffen, many thanks for the tests, that's highly appreciated! I'm glad to see that we are fine with noble, mantic and jammy. It was btw. good to pick the version from the noble archive, since it's in beta). (And btw. we usually do not alter DISTRELEASE in common.mak.) I'm uploading first of all the debdiffs for mantic and jammy (to not loose much time), and will investigate focal in a bit... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059303 Title: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2059303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
s390-tools and s390-tools-signed debdiffs for 23.10/mantic ** Attachment added: "debdiff_mantic.tgz" https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/2059303/+attachment/5765782/+files/debdiff_mantic.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059303 Title: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2059303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060020] Re: [Ubuntu-24.04]: Unable to bring up a guest with 1GB RAM using virt-install
Ok, this came out of the discussions. With that I'm closing this bug ... ** Changed in: virtinst (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-power-systems Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060020 Title: [Ubuntu-24.04]: Unable to bring up a guest with 1GB RAM using virt- install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2060020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056485] Re: Behaviour of socat in Ubuntu 20.04 unexpected
Well, to me it looks like socat is like a Swiss army knife, where some features are popular and are used often, but others are very rarely used. Also please consider potential reactions of users that run into this (or similar cases): 1) (trivial) Users notice this problem (or not) and don't do anything. We would not become aware of a problem, hence nothing will be done. Things are probably less important and critical. 2) Users notice this problem and work around this, but do not open a bug. It is fixed for that particular user, and this user is well aware about the bug, since it got fixed by him/her; but this is not the desired reaction, since a bug should have been opened on top to report this. 3) Users notice this problem (and work around this or not), and open a bug. This is (imho) the desired behavior - due to the report and with that the ask to get it fixed. And with an update on the bug, they'll get a notification. Item 3) might cause an adjustment on their side once a fix got rolled out, but will protect for upgrade regressions. The fact that a package wasn't modified for a while does not necessarily mean that no modifications were needed. In this case here, several users reported this (way) earlier in LP: #1883957, and (I think) are waiting for a fix, and we do not know all their use cases, hence it's virtually impossible to have workarounds in place for all potential cases (we only have the needed details for just one: LP#1883957, but shouldn't limit ourselves to this). So I am still an advocate for getting things fixed where they are broken and believe that this also helps to reduce risk, compared to touching more/other components and at the end maybe not being able cover everything. The idea of using LP2056485_SOCAT_BEHAVIOUR could work, but might again lead to other risks, like cases where user may switch accounts, but in a way that they loose previously set environment variables etc. - I personally would consider that as more risky and overkill. But the final decision is of course at the SRU team. Meanwhile I've modified the patched package to just cover the two hunks that are related to the TERMIOS_PH_ALL test case - if we will go that route or not. Just try to speed up things in case this will be the way to go ... (since this is about a customer case) (Btw. I have marked LP#1883957 as dup of LP#2056485, because as partner/customer case LP#2056485 came in via the BZ-2-LP-bridge and will cause issues otherwise. But I've referenced both bugs in the changelog, see debdiff - it's probably not the best way, but want to ensure that people who reported this will be notified in case of a fix. If there is a better way, I am happy t adapt it ...) PPA test build (with minimized patch for test case): https://launchpad.net/~fheimes/+archive/ubuntu/lp2056485-3 (build includes successful tests) The updated debdiff is attached. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056485 Title: Behaviour of socat in Ubuntu 20.04 unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883957] Re: socat-1.7.3.3 (focal) termios options incorrectly applied to the second address
*** This bug is a duplicate of bug 2056485 *** https://bugs.launchpad.net/bugs/2056485 ** This bug has been marked a duplicate of bug 2056485 Behaviour of socat in Ubuntu 20.04 unexpected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883957 Title: socat-1.7.3.3 (focal) termios options incorrectly applied to the second address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/socat/+bug/1883957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2060807] Re: [UBUNTU 24.04] s390x: clone clobbers r7
*** This bug is a duplicate of bug 2055175 ***
https://bugs.launchpad.net/bugs/2055175
I strongly believe that this is a duplicate of LP#2055175, which is
meanwhile Fix Released and should be included in the latest noble/24.04
daily images.
glibc in noble (release) is currently (Apr 10th) 2.39-0ubuntu8
and
glibc 2.39-0ubuntu7 changelog incl:
- S390: Do not clobber r7 in clone [BZ #31402] (LP: #2055175)
So I consider this as duplicate and closed/Fix Released.
Please feel free to object, in case you think this is not fixed or if
there is another issue.
** Package changed: linux (Ubuntu) => glibc (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Also affects: glibc (Ubuntu Noble)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Changed in: glibc (Ubuntu Noble)
Status: New => Fix Released
** Changed in: ubuntu-z-systems
Status: New => Fix Released
** Changed in: glibc (Ubuntu Noble)
Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)
** This bug has been marked a duplicate of bug 2055175
[UBUNTU 23.10] s390x: clone clobbers r7
--
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/2060807
Title:
[UBUNTU 24.04] s390x: clone clobbers r7
Status in Ubuntu on IBM z Systems:
Fix Released
Status in glibc package in Ubuntu:
Fix Released
Status in glibc source package in Noble:
Fix Released
Bug description:
=== Description by ===
On s390x, if clone is called with NULL for child-function or stack argument,
then r7 is clobbered. This bug is needed for glibc 2.37, 2.38, 2.39. Please
pick the committed bugfix.
See
- glibc bugzilla:
Bug 31402 - clone (NULL, NULL, ...) clobbers %r7 register on s390{,x}
https://sourceware.org/bugzilla/show_bug.cgi?id=31402
- glibc-commit on master:
S390: Do not clobber r7 in clone [BZ #31402]
https://sourceware.org/git/?p=glibc.git;a=commit;h=02782fd12849b6673cb5c2728cb750e8ec295aa3
- glibc-commit on release/2.37/master:
https://sourceware.org/git/?p=glibc.git;a=commit;h=9a1bdd7df731a4bc60f72dbdc1b849e02cfa9c34
- glibc-commit on release/2.38/master:
https://sourceware.org/git/?p=glibc.git;a=commit;h=ee4806e978467d705b26ccb7dfddb9e0a710f8e4
- glibc-commit on release/2.39/master:
https://sourceware.org/git/?p=glibc.git;a=commit;h=e0910f1d3278f05439fb434ee528fc9be1b6bd5e
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2060807/+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
[Bug 2060807] Re: [UBUNTU 24.04] s390x: clone clobbers r7
*** This bug is a duplicate of bug 2055175 *** https://bugs.launchpad.net/bugs/2055175 I strongly believe that this is a duplicate of LP#2055175, which is meanwhile Fix Released and should be included in the latest noble/24.04 daily images. glibc in noble (release) is currently (Apr 10th) 2.39-0ubuntu8 and glibc 2.39-0ubuntu7 changelog incl: - S390: Do not clobber r7 in clone [BZ #31402] (LP: #2055175) So I consider this as duplicate and closed/Fix Released. Please feel free to object, in case you think this is not fixed or if there is another issue. ** Package changed: linux (Ubuntu) => glibc (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Also affects: glibc (Ubuntu Noble) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Changed in: glibc (Ubuntu Noble) Status: New => Fix Released ** Changed in: ubuntu-z-systems Status: New => Fix Released ** Changed in: glibc (Ubuntu Noble) Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned) ** This bug has been marked a duplicate of bug 2055175 [UBUNTU 23.10] s390x: clone clobbers r7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060807 Title: [UBUNTU 24.04] s390x: clone clobbers r7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2060807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
** Changed in: ubuntu-z-systems Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059303 Title: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2059303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058944] Re: [UBUNTU 24.04] dbginfo.sh: updates required for /bin/dash shell
** Changed in: ubuntu-z-systems Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058944 Title: [UBUNTU 24.04] dbginfo.sh: updates required for /bin/dash shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2058944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Tags added: s390x ** Changed in: ubuntu-z-systems Assignee: (unassigned) => bugproxy (bugproxy) -- 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/2060217 Title: NFSv4 fails to mount in noble/s390x Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Status in nfs-utils package in Ubuntu: Triaged Bug description: https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/s390x Looks like it has been failing for a long time already. Log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/s390x/n/nfs-utils/20240404_145924_ef255@/log.gz 339s autopkgtest [14:41:04]: test local-server-client: [--- 340s Killed 340s autopkgtest [14:41:05]: test process requested reboot with marker boot1 364s autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds... 372s FAIL: nfs_home not mounted 373s autopkgtest [14:41:38]: test local-server-client: ---] 373s local-server-client FAIL non-zero exit status 1 and 934s autopkgtest [14:50:59]: test kerberos-mount: [--- 935s Initializing database '/var/lib/krb5kdc/principal' for realm 'DEP8', 935s master key name 'K/M@DEP8' 935s Authenticating as principal root/admin@DEP8 with password. 935s Principal "nfs/nfs-server.dep8@DEP8" created. 935s Authenticating as principal root/admin@DEP8 with password. 935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 935s Authenticating as principal root/admin@DEP8 with password. 935s Principal "host/nfs-server.dep8@DEP8" created. 935s Authenticating as principal root/admin@DEP8 with password. 935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 936s exporting *:/storage 938s mount.nfs: mount system call failed for /mnt 938s umount: /mnt: not mounted. 938s autopkgtest [14:51:02]: test kerberos-mount: ---] 939s kerberos-mount FAIL non-zero exit status 32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2060217/+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
[Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Tags added: s390x ** Changed in: ubuntu-z-systems Assignee: (unassigned) => bugproxy (bugproxy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060217 Title: NFSv4 fails to mount in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Touch-packages] [Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image
I see (deep in my mind I remember that such a discussion happened or at
least started somewhere).
Just notice that one interface is still _not_ optional, here in my case:
encc000
And the behavior changed recently, with the above config I didn not hit
the timeout in the past (even with earlier noble daily images).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2060311
Title:
Setting "optional: true" to overcome he timeout "Job systemd-networkd-
wait-online" does no longer work with latest noble image
Status in Netplan:
New
Status in Ubuntu on IBM z Systems:
New
Status in systemd package in Ubuntu:
New
Bug description:
Especially on s390x (but not limited to s390x) it's often the case that a
system has network devices that are not necessarily connected during boot-up
and one gets such a 2 min timeout:
"Job systemd-networkd-wait-online. Start running (1min 59s / no limit)"
In the past I could avoid that by setting "optional: true" post-install (no
perfect, but worked),
but this does no longer seem to work using the latest noble ISO image (Apr
5th).
Setting 'optional: true' in /etc/netplan/50-cloud-init.yaml looks like
this for me:
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
enP1p0s0:
optional: true
dhcp4: true
enP1p0s0d1:
optional: true
dhcp4: true
enP2p0s0:
optional: true
dhcp4: true
enP2p0s0d1:
optional: true
dhcp4: true
encc000: {}
version: 2
vlans:
encc000.2653:
addresses:
- 10.11.12.15/24
gateway4: 10.11.12.1
id: 2653
link: encc000
nameservers:
addresses:
- 10.11.12.1
... can be set fine (also --dry-run does not moan, except about
dhcp4).
This worked in the past on noble, but also on older Ubuntu releases
like jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2060311/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
Hi Steffen, thanks for checking the updated packages. Indeed, I had to restart the build of the s390-tools-signed packages for mantic/23.10, /jammy/22.04 and focal/20.04. These build will be complete in an hour or so (so well before Monday). Since the updates need to be done starting with the newest to oldest, a test on noble/24.04 would be most important. Do you have a mantic/23.10 or jammy/22.04 test system over? In this case you should be able to upgrade to noble/24.04 in just a few minutes. First of all ensure that your current system (mantic or jammy) is up-to- date with: sudo apt update && && sudo apt full-upgrade (with a potential reboot) You should then be able to upgrade with: sudo do-release-upgrade -d (or in case you are brave enough - but on a test/dev system ;-) : sudo do-release-upgrade --quiet --devel-release --frontend=DistUpgradeViewNonInteractive && sudo reboot ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059303 Title: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2059303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056485] Re: Behaviour of socat in Ubuntu 20.04 unexpected
** Changed in: socat (Ubuntu Focal) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056485 Title: Behaviour of socat in Ubuntu 20.04 unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`
Fantastic, thanks for re-testing and confirming! Closing this ticket as Fix Released. ** Changed in: ubuntu-power-systems Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image
I see (deep in my mind I remember that such a discussion happened or at least started somewhere). Just notice that one interface is still _not_ optional, here in my case: encc000 And the behavior changed recently, with the above config I didn not hit the timeout in the past (even with earlier noble daily images). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060311 Title: Setting "optional: true" to overcome he timeout "Job systemd-networkd- wait-online" does no longer work with latest noble image To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2060311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046439] Re: Wrong code execution of s390x code with qemu TCG
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046439 Title: Wrong code execution of s390x code with qemu TCG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2046439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`
Fantastic, thanks for re-testing and confirming! Closing this ticket as Fix Released. ** Changed in: ubuntu-power-systems Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+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
[Bug 2055175] Re: [UBUNTU 23.10] s390x: clone clobbers r7
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055175 Title: [UBUNTU 23.10] s390x: clone clobbers r7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2055175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
Builds finally completed: noble: https://launchpad.net/~fheimes/+archive/ubuntu/lp2059303 mantic, jammy, focal: https://launchpad.net/~fheimes/+archive/ubuntu/test -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059303 Title: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2059303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056485] Re: Behaviour of socat in Ubuntu 20.04 unexpected
Thanks for having a look at this SRU. The general compile of the socat code works after just having commit 5ebf36038f39 "Under certain circumstances, options of the first address were applied to the second address" applied. However, the build also triggers a huge amount of tests, and one, test case 385 'TERMIOS_PH_ALL', is related to this modification and starts to fail. (Btw. this is roughly like the case you mentioned that "affected users of 20.04 may rely on the current behaviour".) Hence a fix is needed to make the 'TERMIOS_PH_ALL' test case work again. And I think this is also reasonable for other (non-test) cases. This was meanwhile upstream fixed "as part of" 9de26f1d0528 "minor corrections, not affecting binaries" (not a great commit msg). The commit 9de26f1d0528 covers different aspects, that are not well documented in the commit description. For this case the modification (as part of 9de26f1d0528) in Makefile.in (and obviously in CHANGES). are not needed. And even the hunks in test.sh: @@ -183,7 +183,7 @@ and @@ -13020,7 +13020,7 @@ are not relevant for the 'TERMIOS_PH_ALL' test case. Only the hunks: @@ -13057,8 +13057,10 @@ and @@ -13066,6 +13068,7 @@ (Whereas hunk '@@ -13066,6 +13068,7 @@' is again not absolutely required for a fixed test.) So yes, the patch could be minimized, for example to cover only: @@ -13057,8 +13057,10 @@ and @@ -13066,6 +13068,7 @@ Well, I thought about this, but from other work (esp. in the kernel area) I've learned (and I generally agree with that) that it is better to stick to entire upstream commits/patches (if possible) for the reason of future maintainability. I think this can be helpful if further patches (due to other bugs are needed) and will reduce risk as well, since the patch is like upstream, means tested like this and incl. like this in never versions. However, if you insist of having this patch minimized; I can do that of course. I think it's close to a philosophical question what is best to do in case "users of 20.04 relying on the current behaviour". I personally believe that since the behavior is wrong, that it needs to be corrected. Please notice that the behavior is correct in all releases newer than focal - means if not fixing this now with an upgrade, things will break at least after a dist-upgrade. Working around this in mkvterm might make the situation (imho) not a lot better (or even worse) and would introduce modification at another place (and would be for focal only, and mkvterm code in never releases might diverge). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056485 Title: Behaviour of socat in Ubuntu 20.04 unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
** Description changed:
+ SRU Justification:
+
+ [ Impact ]
+
+ * Symptom:
+
+* There is an issue with the Secure Execution (SE) tooling,
+ especially the new IBM host-key subject locality,
+ that leads to the fact that on April 24 (z15) / March 29 (z16)
+ users will notice that the tooling for Secure execution will no
+ longer detect that the provided IBM signing key for that generation
+ is a valid IBM signing key.
+
+* The error message will contain "no IBM signing key found" or similar.
+ The respective tool will reject creating an encrypted request/image
+ as it could not verify the host-key for its validity.
+
+* This affects the genprotimg, pvattest, and pvsecret tools.
+ (Please notice that these tools got introduced over time with different
+ s390-tools versions that belong to different Ubuntu releases).
+
+ * Problem:
+
+* The new IBM signing keys no longer contain 'Poughkeepsie' as
+ 'subject locality' and 'Armonk' is used.
+
+* The SE tooling checks, beside other things, for the subject in the
+ IBM signing key.
+
+* If the subject is not the expected one, the certificate is not
+ recognized as a valid IBM signing key.
+ And without a valid IBM signing key, the host-key verification
+ cannot succeed and users cannot build trustable SE images and
+ attestation or add-secret requests.
+
+ * Solution:
+
+* Mitigations are available upstream.
+
+* The fixes allow Armonk as additional locality in the subject
+ and allow potential mismatches in the locality of revocation list
+ or host-key issuer subject that may still contain Poughkeepsie
+ instead of Armonk.
+
+ [ Test Plan ]
+
+ *
+
+ * The testing is required for all three affected tools:
+genprotimg, pvattest, and pvsecret
+
+ * Without the fixed code, but with the new IBM signing keys
+(that have 'Armonk' as 'subject locality'), users will get a msgs like:
+"no IBM signing key found"
+and the validation will fail.
+
+ * With the patches included, the validation will succeed.
+
+ [ Where problems could occur ]
+
+ * The tools genprotimg, pvattest, and pvsecret tools are affected.
+Since they got introduced over time with different s390-tools versions
+that belong to different Ubuntu releases, it's important to figure out the
+commits/patches that are required for each release.
+
+ * The refactoring commit f6c6f0cc712433221fb0588c754e0d09884453dd
+("rust/pv/test: Code + Certificate refactoring") is needed
+for noble and mantic, but needs several adjustments due to context changes.
+The code could be negatively affected and the build might even break.
+(A test build in PPA mitigates such issues.)
+
+ * As host host-key issuer subject now Poughkeepsie and Armonk is allowed.
+If the conditional statements are not properly coded, either Poughkeepsie
+or Armonk might be allowed, which would fails in case the opposite is used.
+(Testing if the IBM signing key is valid will mitigate this.)
+
+ * In worst case a broken detection of the host-key issuer subject may lead
+to positive validations, regardless of the subject content.
+(Testing if the IBM signing key is valid will mitigate this.)
+
+ * A test build for all affected Ubuntu releases (N, M, J and F) succeeded
+and is available via this PPA:
+https://launchpad.net/~fheimes/+archive/ubuntu/lp2059303
+
+ * These test packages will be pre-tested by IBM.
+
+ * This affected Secure Execution (SE) functionality only on s390x.
+No other tools that are part of the s390-tools packages are affected
+(or got modified in any way).
+
+ [ Other Info ]
+
+ * Secure Execution (SE) was introduced with in Ubuntu Server for s390x
+with 20.04 LTS, hence 20.04 LTS and higher is affected.
+
+ * And with that the s390-tools versions that are still in service:
+2.12.0-0ubuntu3.7 | focal-updates
+2.20.0-0ubuntu3.2 | jammy-updates
+2.29.0-0ubuntu2.1 | mantic-updates
+2.30.0-0ubuntu1 | noble-updates / 2.31.0-0ubuntu4 | noble-proposed
+
+ * The following commits / patches need to be applied to the following
+s390-tools versions:
+* f6c6f0cc712433221fb0588c754e0d09884453dd
+ ("rust/pv/test: Code + Certificate refactoring")
+ to noble, mantic
+* 1a3d0b74f7819f5e087e6ecbf3ec879a05a88bbc
+ ("rust/pv: Support `Armonk` in IBM signing key subject")
+ to noble, mantic
+* d14e7593cc6380911ca42b09e11c53477ae13d5c
+ ("genprotimg: support `Armonk` in IBM signing key subject")
+ to noble, mantic, jammy, focal
+* d7c95265cdb6217b0203efa5893c3a27838af63c
+ ("libpv: Support `Armonk` in IBM signing key subject")
+ to noble, mantic, jammy
+* 2b5e7b049123aff094c7de79ba57a5df09471b2e
+ ("pvattest: Fix root-ca parsing")
+ to noble, mantic, jammy
+ __
+
Description: SE-tooling: New IBM
[Bug 2060108] Re: greenlet 3.0.3 fails to build on ppc64el (and riscv64)
** Changed in: python-greenlet (Ubuntu) Assignee: (unassigned) => bugproxy (bugproxy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060108 Title: greenlet 3.0.3 fails to build on ppc64el (and riscv64) To manage notifications about this bug go to: https://bugs.launchpad.net/greenlet/+bug/2060108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060108] [NEW] greenlet 3.0.3 fails to build on ppc64el (and riscv64)
Public bug reported: greenlet 3.0.3 fails to build on riscv64 and ppc64el: complete build logs at https://launchpad.net/ubuntu/+source/python-greenlet/3.0.3-0ubuntu2 riscv64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fno- omit-frame-pointer -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fdebug-prefix-map=/<>=/usr/src/python- greenlet-3.0.3-0ubuntu2 -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC -I/usr/include/python3.11 -c /<>/src/greenlet/greenlet.cpp -o build/temp.linux-riscv64-cpython-311/<>/src/greenlet/greenlet.o -Os So the reason is that recent Linux distros decided to build with -fno- omit-frame-pointer by default. Apparently both the riscv64 and the ppc64el implementations cannot cope with that. The issue can be reproduce by adding -fno-omit-frame-pointer to the build flags. https://launchpad.net/ubuntu/+source/python-greenlet/3.0.3-0ubuntu4 _ There is also this upstream github issue: https://github.com/python-greenlet/greenlet/issues/395 ** Affects: greenlet Importance: Unknown Status: Unknown ** Affects: ubuntu-power-systems Importance: Undecided Assignee: bugproxy (bugproxy) Status: Triaged ** Affects: python-greenlet (Ubuntu) Importance: Undecided Status: New ** Tags: ppc64el reverse-proxy-bugzilla ** Also affects: python-greenlet (Ubuntu) Importance: Undecided Status: New ** Description changed: greenlet 3.0.3 fails to build on riscv64 and ppc64el: complete build logs at https://launchpad.net/ubuntu/+source/python-greenlet/3.0.3-0ubuntu2 riscv64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fno- omit-frame-pointer -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fdebug-prefix-map=/<>=/usr/src/python- greenlet-3.0.3-0ubuntu2 -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC -I/usr/include/python3.11 -c /<>/src/greenlet/greenlet.cpp -o build/temp.linux-riscv64-cpython-311/<>/src/greenlet/greenlet.o -Os So the reason is that recent Linux distros decided to build with -fno- omit-frame-pointer by default. Apparently both the riscv64 and the ppc64el implementations cannot cope with that. The issue can be reproduce by adding -fno-omit-frame-pointer to the build flags. + + https://launchpad.net/ubuntu/+source/python-greenlet/3.0.3-0ubuntu4 ** Tags added: reverse-proxy-bugzilla ** Description changed: greenlet 3.0.3 fails to build on riscv64 and ppc64el: complete build logs at https://launchpad.net/ubuntu/+source/python-greenlet/3.0.3-0ubuntu2 riscv64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fno- omit-frame-pointer -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fdebug-prefix-map=/<>=/usr/src/python- greenlet-3.0.3-0ubuntu2 -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC -I/usr/include/python3.11 -c /<>/src/greenlet/greenlet.cpp -o build/temp.linux-riscv64-cpython-311/<>/src/greenlet/greenlet.o -Os So the reason is that recent Linux distros decided to build with -fno- omit-frame-pointer by default. Apparently both the riscv64 and the ppc64el implementations cannot cope with that. The issue can be reproduce by adding -fno-omit-frame-pointer to the build flags. https://launchpad.net/ubuntu/+source/python-greenlet/3.0.3-0ubuntu4 + _ + + There is also this upstream github issue: + https://github.com/python-greenlet/greenlet/issues/395 ** Bug watch added: github.com/python-greenlet/greenlet/issues #395 https://github.com/python-greenlet/greenlet/issues/395 ** Also affects: greenlet via https://github.com/python-greenlet/greenlet/issues/395 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060108 Title: greenlet 3.0.3 fails to build on ppc64el (and riscv64) To manage notifications about this bug go to: https://bugs.launchpad.net/greenlet/+bug/2060108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059303] Re: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools)
Meanwhile I've navigated through the challenges in noble and have a successful PPA build here: launchpad.net/~fheimes/+archive/ubuntu/lp2059303 and the s390-tools and the s390-tools-signed debdiffs attached. ** Attachment added: "debdiffs.tgz" https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/2059303/+attachment/5761332/+files/debdiffs.tgz ** Changed in: s390-tools (Ubuntu Noble) Assignee: (unassigned) => Frank Heimes (fheimes) ** Changed in: s390-tools-signed (Ubuntu Noble) Assignee: (unassigned) => Frank Heimes (fheimes) ** Changed in: s390-tools (Ubuntu Noble) Status: New => In Progress ** Changed in: s390-tools-signed (Ubuntu Noble) Status: New => In Progress ** Changed in: s390-tools-signed (Ubuntu Noble) Importance: Undecided => High ** Changed in: s390-tools (Ubuntu Noble) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059303 Title: [UBUNTU 20.04] SE-tooling: New IBM host-key subject locality (s390-tools) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2059303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060020] Re: [Ubuntu-24.04]: Unable to bring up a guest with 1GB RAM using virt-install
Oh sorry, I just noticed that the ppc64el ISO was NOT updated and is still from March 28th, means it still has the -11 kernel inside. We need to investigate why it wasn't updated - and why there is no daily from April 1st and 2nd ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060020 Title: [Ubuntu-24.04]: Unable to bring up a guest with 1GB RAM using virt- install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2060020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
