[Bug 2054395] Re: [sru] sos upstream 4.7.0

[Mauricio Faria de Oliveira]

Autopkgtests for oracular/cockpit/s390x passed with a retry,
that should unblock the oracular-proposed migration shortly.

316-1build1 sosreport/4.7.0-0ubuntu12024-05-22
15:19:06 UTC 0h 04m 29s  mfo pass
1bc3dca3-467e-430b-b336-fe8c1f19b6d5

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

Title:
  [sru] sos upstream 4.7.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064686] Re: Add "oracular" as a known Ubuntu distribution

[Mauricio Faria de Oliveira]

The autopkgtests failures for mantic/jammy/focal have cleared up with retries. 
Proceeding with the release of these series.

lintian [mantic/armhf]
2.116.3ubuntu3.2lintian/2.116.3ubuntu3.2
2024-05-20 22:46:45 UTC 0h 32m 13s  mfo pass
ef360a32-853b-4225-aab0-7b2445e499e0

lintian-brush [jammy/armhf]
0.120ubuntu1lintian/2.114.0ubuntu1.4
2024-05-20 22:15:19 UTC 0h 17m 06s  mfo pass
cbddec24-fc02-4c40-99f8-37331e953bab

pkg-perl-tools [jammy/armhf]
0.65lintian/2.114.0ubuntu1.4
2024-05-20 22:16:22 UTC 0h 15m 27s  mfo pass
b4ef28b4-c44d-4c60-9b27-3cb6e7e81a2b

libconfig-model-dpkg-perl [focal/armhf]
2.132   lintian/2.62.0ubuntu2.4 
2024-05-20 22:14:18 UTC 0h 12m 36s  mfo pass
4435c140-c91b-4bd2-a158-08f310140c2f

lintian-brush [focal/armhf]
0.60ubuntu1 lintian/2.62.0ubuntu2.4 
2024-05-20 22:18:48 UTC 0h 26m 37s  mfo pass
7bd01272-cdc3-441d-b08c-4d0c836ac8f1

@ 
https://ubuntu-archive-team.ubuntu.com/proposed-migration/mantic/update_excuses.html#lintian

lintian (2.116.3ubuntu3.1 to 2.116.3ubuntu3.2)

Migration status for lintian (2.116.3ubuntu3.1 to 
2.116.3ubuntu3.2): BLOCKED: Needs an approval (either due to a freeze, the 
source suite or a manual hint)
Issues preventing migration:
Not touching package due to block request by freeze (please contact 
ubuntu-release if update is needed)
Additional info:
17 days old 

@ https://ubuntu-archive-team.ubuntu.com/proposed-
migration/jammy/update_excuses.html#lintian

lintian (2.114.0ubuntu1.3 to 2.114.0ubuntu1.4)

Migration status for lintian (2.114.0ubuntu1.3 to 
2.114.0ubuntu1.4): BLOCKED: Needs an approval (either due to a freeze, the 
source suite or a manual hint)
Issues preventing migration:
Not touching package due to block request by freeze (please contact 
ubuntu-release if update is needed)
Additional info:
17 days old 

@ https://ubuntu-archive-team.ubuntu.com/proposed-
migration/focal/update_excuses.html#lintian

lintian (2.62.0ubuntu2.3 to 2.62.0ubuntu2.4)

Migration status for lintian (2.62.0ubuntu2.3 to 2.62.0ubuntu2.4): 
BLOCKED: Needs an approval (either due to a freeze, the source suite or a 
manual hint)
Issues preventing migration:
Not touching package due to block request by freeze (please contact 
ubuntu-release if update is needed)
Additional info:
17 days old

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

Title:
  Add "oracular" as a known Ubuntu distribution

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064686] Re: Add "oracular" as a known Ubuntu distribution

[Mauricio Faria de Oliveira]

The verification for noble/mantic/jammy/focal look good; thanks!

However, the autopkgtests failures for mantic/jammy/focal aren't clear.
I retried them, as apparently they are infrastructure related timeouts/issues.
I'll check later if still on shift.

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

Title:
  Add "oracular" as a known Ubuntu distribution

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064686] Update Released

[Mauricio Faria de Oliveira]

The verification of the Stable Release Update for lintian has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Add "oracular" as a known Ubuntu distribution

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060745] Update Released

[Mauricio Faria de Oliveira]

The verification of the Stable Release Update for nbd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  nbd-client fails to connect Error: Socket failed: Connection refused

To manage notifications about this bug go to:
https://bugs.launchpad.net/nbd/+bug/2060745/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060745] Re: nbd-client fails to connect Error: Socket failed: Connection refused

[Mauricio Faria de Oliveira]

Verificaton done on noble-proposed.

Thanks for the detailed test steps!
(I updated the last command from 'nbd-client -d nbd0' to 'nbd-client nbd0',
which reflects the test step without the fix, in 'Now, trigger the problem').

Environment:
---

lxc launch ubuntu:noble --vm mfo-noble-vm
lxc shell mfo-noble-vm  
apt update -y && apt install -y nbd-client nbd-server

modprobe nbd
truncate -s 1T /vol-0.img

cat /etc/nbdtab
nbd0 localhost vol0
EOF

Before:
---

# dpkg -s nbd-client | grep Version:
Version: 1:3.26.1-1build1

# nbd-client nbd0
Error: Socket failed: Connection refused

After:
---

sed '/^Suites: .*noble-updates/ s/$/ noble-proposed/' -i 
/etc/apt/sources.list.d/ubuntu.sources
apt update && apt install -y -t noble-proposed nbd-client nbd-server

# apt policy nbd-client
nbd-client:
  Installed: 1:3.26.1-1ubuntu0.1
  Candidate: 1:3.26.1-1ubuntu0.1
  Version table:
 *** 1:3.26.1-1ubuntu0.1 100
100 http://archive.ubuntu.com/ubuntu noble-proposed/universe amd64 
Packages
100 /var/lib/dpkg/status
 1:3.26.1-1build1 500
500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages


# dpkg -s nbd-client | grep Version:
Version: 1:3.26.1-1ubuntu0.1

# nbd-client nbd0
Connected /dev/nbd0

** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble

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

Title:
  nbd-client fails to connect Error: Socket failed: Connection refused

To manage notifications about this bug go to:
https://bugs.launchpad.net/nbd/+bug/2060745/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060745] Re: nbd-client fails to connect Error: Socket failed: Connection refused

[Mauricio Faria de Oliveira]

** Description changed:

  [ Impact ]
  
  nbdtab uses a port of 0 by default which is not sensible. This means
  that if you do not set a default port in nbdtab, it will fail.
  
  You will see an error such as: Error: Socket failed: Connection refused
  
  [ Test Plan ]
  
  $ lxc launch ubuntu:noble n-vm --vm
  $ lxc shell n-vm
  # apt update -y && apt install -y nbd-client nbd-server
  # dpkg -s nbd-client | grep Version:
  Version: 1:3.26.1-1build1
  # modprobe nbd
  # truncate -s 1T /vol-0.img
  # cat > /etc/nbd-server/conf.d/exports.conf << _EOF_
  [vol0]
  exportname = /vol-0.img
  _EOF_
  # systemctl restart nbd-server.service
  
  Verify that NBD is working properly:
  
  # nbd-client localhost /dev/nbd0 -name vol0
  
  It should work.
  
  To clean it up:
  
  # nbd-client -d /dev/nbd0
  
  Now, trigger the problem:
  
  # cat >> /etc/nbdtab << _EOF_
  nbd0 localhost vol0
  _EOF_
  # nbd-client nbd0
  
  You should see the error:
  
  # nbd-client nbd0
  Error: Socket failed: Connection refused
  
  Test the fix:
  # add-apt-repository -y ppa:mitchdz/lp2060745-nbd-port-fix
  # apt update -y && apt upgrade -y
  # dpkg -s nbd-client | grep Version:
  Version: 1:3.26.1-1ubuntu0.1~noble1
- # nbd-client -d /dev/nbd0
+ # nbd-client /dev/nbd0
  < no errors here>
  
  [ Where problems could occur ]
  * This changes the default port, so issues using custom ports could arise. 
This seems unlikely since it is a one line change that should get overridden.

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

Title:
  nbd-client fails to connect Error: Socket failed: Connection refused

To manage notifications about this bug go to:
https://bugs.launchpad.net/nbd/+bug/2060745/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063820] Re: rtl8812au-dkms DKMS FTBFS wrt Linux 6.8

[Mauricio Faria de Oliveira]

This SRU is blocked on the upload to the Development Release, as per [1] 
(comment #2).
If that is not possible or needed, please explain. Marking Oracular as 
Incomplete. Thanks!

[1]
https://wiki.ubuntu.com/StableReleaseUpdates#Development_Release_Fixed_First

** Changed in: rtl8812au (Ubuntu Oracular)
   Status: New => Triaged

** Changed in: rtl8812au (Ubuntu Oracular)
   Status: Triaged => Incomplete

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

Title:
  rtl8812au-dkms DKMS FTBFS wrt Linux 6.8

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2062177] Update Released

[Mauricio Faria de Oliveira]

The verification of the Stable Release Update for remmina has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Remmina crashes after RDP connection

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063383] Re: [SRU] Ubuntu Unity takes 90 seconds to log out

[Mauricio Faria de Oliveira]

Marking this SRU as verification-failed per comments
- #4 (partial failure with applications running) and 
- #5 (failure even without applications running).

The partial failure would seem like a regression too,
since the bug description says that the fix / change
acts 'effectively and immediately', not conditionally
on running applications:

> gnome-session-quit should be invoked when the systemd unit shuts down, 
> which acts effectively and immediately.

Please revert the tag flip if there are other reasons. Thanks!


** Tags removed: verification-needed-noble
** Tags added: verification-failed-noble

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

Title:
  [SRU] Ubuntu Unity takes 90 seconds to log out

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2063383/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2042844] Re: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in AboutToShow

[Mauricio Faria de Oliveira]

Verification pending for noble-proposed
(blocks combined SRU release for bugs 2059818, 2059819, 2042844)

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

Title:
  JS ERROR: Gio.DBusError:
  GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in
  AboutToShow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2042844/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen

[Mauricio Faria de Oliveira]

Verification pending for noble-proposed
(blocks combined SRU release for bugs 2059818, 2059819, 2042844)

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

Title:
  Regression: Jammy to Noble, right clicking on some icons shows
  dropdown on left side of screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061214] Re: [SRU] Software Sources is not compatible with deb822

[Mauricio Faria de Oliveira]

This SRU is pending verification for noble-proposed and autopkgtests
regressions to be cleared up.

I looked the autopkgtests regressions, and some seem to be temporary
conditions on the infrastructure, thus I just triggered retries for all
tests/archs.

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

Title:
  [SRU] Software Sources is not compatible with deb822

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one

[Mauricio Faria de Oliveira]

This SRU is pending clarification about the verification tags flip
(comments 23, 12, 7) and other questions (comment 23).

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

Title:
  obsolete out-of-tree ivsc dkms in favor of in-tree one

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054799] Re: [SRU] Issue with Project administration at Cloud Admin level

[Mauricio Faria de Oliveira]

Attaching the error image linked in the bug description for archival
purposes:

"""
Expectation: Get a table with the users assigned to this project.
Result: Get an error - https://i.imgur.com/TminwUy.png [attached]
"""

** Attachment added: "TminwUy.png"
   
https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/2054799/+attachment/5779444/+files/TminwUy.png

** Description changed:

  [Impact]
  
  We are not able to see the list of users and groups assigned to a
  project in Horizon.
  
  [Test Case]
  
  Please refer to [Test steps] section below.
  
  [Regression Potential]
  
  The fix ed768ab is already in the upstream main, stable/2024.1,
  stable/2023.2 branches, so it is a clean backport and might be helpful
  for deployments using dashboard.
  
- 
  [Others]
  
  Original Bug Description Below
  ===
  
  We are not able to see the list of users assigned to a project in Horizon.
  Scenario:
  - Log in as Cloud Admin
  - Set Domain Context (k8s)
  - Go to projects section
  - Click on project Permissions_Roles_Test
  - Go to Users
  
  Expectation: Get a table with the users assigned to this project.
- Result: Get an error - https://i.imgur.com/TminwUy.png
+ Result: Get an error - https://i.imgur.com/TminwUy.png [attached]
  
  [Test steps]
  
  1, Create an ordinary openstack test env with horizon.
  
  2, Prepared some test data (eg: one domain k8s, one project k8s, and one
  user k8s-admain with the role k8s-admin-role)
  
  openstack domain create k8s
  openstack role create k8s-admin-role
  openstack project create --domain k8s k8s
  openstack user create --project-domain k8s --project k8s --domain k8s 
--password password k8s-admin
  openstack role add --user k8s-admin --user-domain k8s --project k8s 
--project-domain k8s k8s-admin-role
  $ openstack role assignment list --project k8s --names
  
++---+---+-+++---+
  | Role   | User  | Group | Project | Domain | System | 
Inherited |
  
++---+---+-+++---+
  | k8s-admin-role | k8s-admin@k8s |   | k8s@k8s ||| False  
   |
  
++---+---+-+++---+
  
  3, Log in horizon dashboard with admin user(eg:
  admin/openstack/admin_domain).
  
  4, Click 'Identity -> Domains' to set domain context to the domain
  'k8s'.
  
  5, Click 'Identity -> Project -> k8s project -> Users'.
  
  6, This is the result, it said 'Unable to disaply the users of this
  project' - https://i.imgur.com/TminwUy.png
  
  7, These are some logs
  
  ==> /var/log/apache2/error.log <==
  [Fri Feb 23 10:03:12.201024 2024] [wsgi:error] [pid 47342:tid 
140254008985152] [remote 10.5.3.120:58978] Recoverable error: 
'e900b8934d11458b8eb9db21671c1b11'
  ==> /var/log/apache2/ssl_access.log <==
  10.5.3.120 - - [23/Feb/2024:10:03:11 +] "GET 
/identity/07123041ee0544e0ab32e50dde780afd/detail/?tab=project_details__users 
HTTP/1.1" 200 1125 
"https://10.5.3.120/identity/07123041ee0544e0ab32e50dde780afd/detail/; 
"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) 
Chrome/119.0.0.0 Safari/537.36"
  
  [Some Analyses]
  
  This action will call this function in horizon [1].
  This function will firstly get a list of users (api.keystone.user_list) [2], 
then role assignment list (api.keystone.get_project_users_roles) [3].
  Without setting domain context, this works fine.
  However, if setting domain context, the project displayed is in a different 
domain.
  The user list from [2] only contains users of the user's own domain, while 
the role assignment list [3] includes users in another domain since the project 
is in another domain.
  
  From horizon's debug log, here is an example of user list:
  {"users": [{"email": "juju@localhost", "id": 
"8cd8f92ac2f94149a91488ad66f02382", "name": "admin", "domain_id": 
"103a4eb1712f4eb9873240d5a7f66599", "enabled": true, "password_expires_at": 
null, "options": {}, "links": {"self": 
"https://192.168.1.59:5000/v3/users/8cd8f92ac2f94149a91488ad66f02382"}}], 
"links": {"next": null, "self": "https://192.168.1.59:5000/v3/users;, 
"previous": null}}
  
  Here is an example of role assignment list:
  {"role_assignments": [{"links": {"assignment": 
"https://192.168.1.59:5000/v3/projects/82e250e8492b49a1a05467994d33ea1b/users/a70745ed9ac047ad88b917f24df3c873/roles/f606fafcb4fd47018aeffec2b07b7e84"},
 "scope": {"project": {"id": "82e250e8492b49a1a05467994d33ea1b"}}, "user": 
{"id": "a70745ed9ac047ad88b917f24df3c873"}, "role": {"id": 
"f606fafcb4fd47018aeffec2b07b7e84"}}, {"links": {"assignment": 
"https://192.168.1.59:5000/v3/projects/82e250e8492b49a1a05467994d33ea1b/users/fd7a79e2a4044c17873c08daa9ed37a1/roles/b936a9d998be4500900a5a9174b16b42"},
 "scope": {"project": {"id": "82e250e8492b49a1a05467994d33ea1b"}}, "user": 
{"id": "fd7a79e2a4044c17873c08daa9ed37a1"}, "role": {"id": 

[Bug 2054799] Re: [SRU] Issue with Project administration at Cloud Admin level

[Mauricio Faria de Oliveira]

Commit ed768ab50713 (proposed for Ubuntu SRUs & Cloud Archive) isn't in
Oracular yet, IIUIC; adding bug task.

master

$ git log --oneline -1 ed768ab
ed768ab50713 Fix Users/Groups tab list when a domain context is set

stable/2024.1

$ git log --oneline origin/stable/2024.1 | grep -m1 'Fix Users/Groups 
tab list when a domain context is set'
3fce54017985 Merge "Fix Users/Groups tab list when a domain context is 
set" into stable/2024.1

$ git describe --contains 3fce54017985
fatal: cannot describe '3fce54017985ce6bc87c751880b913f456679626'

$ git describe 3fce54017985
24.0.0-5-g3fce54017985

stable/2023.2

$ git log --oneline origin/stable/2023.2 | grep -m1 'Fix Users/Groups 
tab list when a domain context is set'
593ef9b56191 Fix Users/Groups tab list when a domain context is set

$ git describe --contains 593ef9b56191
fatal: cannot describe '593ef9b56191676d0a85b55bd152c0c757fad2de'

$ git describe 593ef9b56191
23.3.0-11-g593ef9b56191

ubuntu

$ rmadison -a source horizon
...
 horizon | 4:23.3.0-0ubuntu1.1   | mantic-updates  
| source
 horizon | 4:24.0.0-0ubuntu1 | noble   
| source
 horizon | 4:24.0.0-0ubuntu1 | oracular
| source


** Also affects: horizon (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/2054799

Title:
  [SRU] Issue with Project administration at Cloud Admin level

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page

[Mauricio Faria de Oliveira]

Adding bug tasks for Noble/Oracular as Fix Released, for clarity, per
comment #2 and checks below.

$ git log --oneline -1 95089025fda7c8cce6f7195e2a63f7f09efc9e0a
95089025fda7 Extend configurable skippability of neutron calls to project 
instance detail

$ git describe --contains 95089025fda7
24.0.0~11^2

$ rmadison -a source horizon
...
 horizon | 4:24.0.0-0ubuntu1 | noble   | source
 horizon | 4:24.0.0-0ubuntu1 | oracular| source

OK.
Double check:

$ pull-lp-source horizon noble
Found horizon 4:24.0.0-0ubuntu1 in noble
...

$ grep -A2 'def _update_addresses' 
horizon-24.0.0/openstack_dashboard/dashboards/project/instances/views.py
def _update_addresses(self, instance):
if not settings.OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES:
return


** Also affects: horizon (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: horizon (Ubuntu Oracular)
   Importance: Undecided
   Status: New

** Changed in: horizon (Ubuntu Oracular)
   Status: New => Fix Released

** Changed in: horizon (Ubuntu Noble)
   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/2055409

Title:
  [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply
  to instance detail page

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1728031] Re: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True

[Mauricio Faria de Oliveira]

Patch [1] (proposed for Ubuntu SRUs & Cloud Archive) isn't in
Oracular/Noble yet, IIUIC; adding bug tasks.

$ git log --oneline -- openstack_dashboard/api/keystone.py | grep -m1 
'Fix error on changing user password by admin'
da8e95929857 Fix error on changing user password by admin

$ git describe --contains da8e95929857
fatal: cannot describe 'da8e959298575127434e6e15aae5d1f0638a6e22'

$ git describe da8e95929857
24.0.0-1-gda8e95929857

$ rmadison -a source horizon | grep -e noble -e oracular
 horizon | 4:24.0.0-0ubuntu1 | noble   
| source
 horizon | 4:24.0.0-0ubuntu1 | oracular
| source

[1] https://review.opendev.org/c/openstack/horizon/+/913250

** Also affects: horizon (Ubuntu Oracular)
   Importance: Undecided
   Status: New

** Also affects: horizon (Ubuntu Noble)
   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/1728031

Title:
  [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is
  True

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901742] Re: systemd-modules-load.service fails to start because it can't understand module arguments in /etc/modules, which it shouldn't even be reading

[Mauricio Faria de Oliveira]

Marking Bionic as Won't Fix as it's End of Standard Support (EOSS), and in 
Expanded Security Maintenance (ESM).
If you have an Ubuntu Pro subscription with Support, and would like a fix, 
please open a support ticket.


** Tags removed: sts-sponsor-volunteer

** Changed in: kmod (Ubuntu Bionic)
   Status: New => 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/1901742

Title:
  systemd-modules-load.service fails to start because it can't
  understand module arguments in /etc/modules, which it shouldn't even
  be reading

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875669] Re: autopkgtest failures

[Mauricio Faria de Oliveira]

** Tags removed: sts-sponsor-volunteer

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

Title:
  autopkgtest failures

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064580] Re: Please update the package to 20240320.00

[Mauricio Faria de Oliveira]

Oh, and Oracular indeed just migrated while I posted the comment (#21
#22); nice timing.

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

Title:
  Please update the package to 20240320.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064580] Update Released

[Mauricio Faria de Oliveira]

The verification of the Stable Release Update for google-osconfig-agent
has completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Please update the package to 20240320.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064580] Re: Please update the package to 20240320.00

[Mauricio Faria de Oliveira]

Summary for SRU release.

Autopkgtests: OK
- Devel/O: proposed migration was blocked in a test queued since early May; 
re-triggered it and it passed; this should migrate soon.
- Stable/NMJF: re-triggered/cleared autopkgtests pending; all series/archs 
passed.

Builds/FTBFS: OK
- Focal/riscv64: failed to build (no logs); fixed with a rebuild.

Pending SRU: OK
- No autopkgtest regressions or FTBFS reported in any series.

Update Excuses: OK
- Devel/O: waiting on refresh/migration after Autopkgtests addressed above
- Stable/NMJF: 'Issues preventing migration:' none

SRU Exception:
- (QA Process) testing/validation from CPC and GCE: OK (comment #18)
- (Vendored dependencies) version changes: OK (comment #19 based on #15, #16, 
#17; in SRU template)

Therefore, will proceed with the release to -updates for 
Noble/Mantic/Jammy/Focal,
as Oracular is expected to migrate soon (and is not a blocker since there are no
GCE images for Oracular as it's not a stable release yet, and when it becomes 
so,
the package is expected to have migrated by months).

Details:
===

Versions in -proposed:
---
$ rmadison -a source google-osconfig-agent | grep proposed | tac
 google-osconfig-agent | 20240320.00-0ubuntu1 | 
oracular-proposed| source
 google-osconfig-agent | 20240320.00-0ubuntu1~24.04.0 | noble-proposed  
 | source
 google-osconfig-agent | 20240320.00-0ubuntu1~23.10.0 | mantic-proposed 
 | source
 google-osconfig-agent | 20240320.00-0ubuntu1~22.04.0 | jammy-proposed  
 | source
 google-osconfig-agent | 20240320.00-0ubuntu1~20.04.0 | 
focal-proposed/universe  | source

Autopkgtests:
---
https://autopkgtest.ubuntu.com/packages/g/google-osconfig-agent/

oracular (OK)
- amd64:PASS // 20240320.00-0ubuntu1
google-osconfig-agent/20240320.00-0ubuntu1  2024-05-14 22:13:57 UTC 
0h 14m 44s  -   pass
- arm64:PASS // 20240320.00-0ubuntu1
google-osconfig-agent/20240320.00-0ubuntu1  2024-05-06 12:58:51 UTC 
0h 06m 54s  -   pass
- armhf:PASS // 20240320.00-0ubuntu1
google-osconfig-agent/20240320.00-0ubuntu1  2024-05-14 16:12:45 UTC 
0h 09m 31s  ginggs  pass
- ppc64el:  PASS // 20240320.00-0ubuntu1
google-osconfig-agent/20240320.00-0ubuntu1  2024-05-06 13:01:11 UTC 
0h 08m 05s  -   pass
- s390x:PASS // 20240320.00-0ubuntu1
google-osconfig-agent/20240320.00-0ubuntu1  2024-05-07 08:47:25 UTC 
0h 14m 00s  utkarsh pass

noble (OK)
- amd64:PASS // 20240320.00-0ubuntu1~24.04.0
google-osconfig-agent/20240320.00-0ubuntu1~24.04.0  2024-05-14 19:52:16 UTC 
0h 29m 56s  mfo pass
- arm64:PASS // 20240320.00-0ubuntu1~24.04.0
google-osconfig-agent/20240320.00-0ubuntu1~24.04.0  2024-05-14 20:16:24 UTC 
0h 16m 56s  mfo pass
- armhf:PASS // 20240320.00-0ubuntu1~24.04.0
google-osconfig-agent/20240320.00-0ubuntu1~24.04.0  2024-05-07 07:15:38 UTC 
0h 07m 11s  utkarsh pass
- ppc64el:  PASS // 20240320.00-0ubuntu1~24.04.0
google-osconfig-agent/20240320.00-0ubuntu1~24.04.0  2024-05-14 20:08:43 UTC 
0h 06m 18s  mfo pass
- s390x:PASS // 20240320.00-0ubuntu1~24.04.0
google-osconfig-agent/20240320.00-0ubuntu1~24.04.0  2024-05-14 20:14:29 UTC 
0h 13m 01s  mfo pass

mantic (OK)
- amd64:PASS // 20240320.00-0ubuntu1~23.10.0
google-osconfig-agent/20240320.00-0ubuntu1~23.10.0  2024-05-07 01:06:44 UTC 
0h 03m 15s  -   pass
- arm64:PASS // 20240320.00-0ubuntu1~23.10.0
google-osconfig-agent/20240320.00-0ubuntu1~23.10.0  2024-05-07 01:24:23 UTC 
0h 23m 36s  -   pass
- armhf:PASS // 20240320.00-0ubuntu1~23.10.0
google-osconfig-agent/20240320.00-0ubuntu1~23.10.0  2024-05-07 01:06:04 UTC 
0h 04m 54s  -   pass
- ppc64el:  PASS // 20240320.00-0ubuntu1~23.10.0
google-osconfig-agent/20240320.00-0ubuntu1~23.10.0  2024-05-07 01:07:25 UTC 
0h 07m 12s  -   pass
- s390x:PASS // 20240320.00-0ubuntu1~23.10.0
google-osconfig-agent/20240320.00-0ubuntu1~23.10.0  2024-05-07 08:40:46 UTC 
0h 08m 11s  utkarsh pass

jammy (OK)
- amd64:PASS // 20240320.00-0ubuntu1~22.04.0
google-osconfig-agent/20240320.00-0ubuntu1~22.04.0  2024-05-07 15:56:10 UTC 
0h 20m 50s  -   pass
- arm64:PASS // 20240320.00-0ubuntu1~22.04.0
google-osconfig-agent/20240320.00-0ubuntu1~22.04.0  2024-05-07 16:54:15 UTC 
0h 25m 57s  -   pass
- armhf:PASS // 20240320.00-0ubuntu1~22.04.0
google-osconfig-agent/20240320.00-0ubuntu1~22.04.0  2024-05-07 16:09:52 UTC 
0h 21m 21s  -   pass
- ppc64el:  PASS // 20240320.00-0ubuntu1~22.04.0
google-osconfig-agent/20240320.00-0ubuntu1~22.04.0  2024-05-07 15:38:43 UTC 
0h 10m 15s  -   pass
- s390x:  

[Bug 1988366] Re: python-rtslib-fb needs to handle new attribute cpus_allowed_list

[Mauricio Faria de Oliveira]

Hi Robie, Sergio,

The concern about removing 'version_attributes' and 'discovery_auth_attributes'
can be addressed with this simple change/backport. 

What do you think?

Don't remove the 2 attributes / move elements into 'target_name_excloudes'.
Instead, add a new attribute / its element into 'target_name_excloudes'.

i.e., this (backport):

 version_attributes = set(["lio_version", "version"])
 discovery_auth_attributes = set(["discovery_auth"])

+cpus_allowed_list_attributes = set(["cpus_allowed_list"])

-target_names_excludes = version_attributes | discovery_auth_attributes
+target_names_excludes = version_attributes | discovery_auth_attributes 
| cpus_allowed_list_attributes

instead of this (upstream):

-version_attributes = set(["lio_version", "version"])
-discovery_auth_attributes = set(["discovery_auth"])
-target_names_excludes = version_attributes | discovery_auth_attributes

+excludes_list = [
+# version_attributes
+"lio_version", "version",
+# discovery_auth_attributes
+"discovery_auth",
+# cpus_allowed_list_attributes
+"cpus_allowed_list",
+]
+target_names_excludes = set(excludes_list)

Python confirms the results are equivalent:

$ python3 -q

Backport:

>>> version_attributes = set(["lio_version", "version"])
>>> discovery_auth_attributes = set(["discovery_auth"])
>>> cpus_allowed_list_attributes = set(["cpus_allowed_list"])
>>> target_names_excludes = version_attributes | 
discovery_auth_attributes | cpus_allowed_list_attributes

>>> target_names_excludes
{'lio_version', 'cpus_allowed_list', 'discovery_auth', 'version'}
>>> backport = target_names_excludes

Upstream:

>>> excludes_list = [
... # version_attributes
... "lio_version", "version",
... # discovery_auth_attributes
... "discovery_auth",
... # cpus_allowed_list_attributes
... "cpus_allowed_list",
... ]
>>> target_names_excludes = set(excludes_list)

>>> target_names_excludes
{'lio_version', 'cpus_allowed_list', 'discovery_auth', 'version'}
>>> upstream = target_names_excludes

The 2 sets are identical, and not the same object:

>>> backport == upstream
True

>>> backport is upstream
False

[1] https://github.com/open-iscsi/rtslib-
fb/commit/8d2543c4da62e962661011fea5b19252b9660822

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

Title:
  python-rtslib-fb needs to handle new attribute cpus_allowed_list

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-rtslib-fb/+bug/1988366/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2015017] Re: [SRU] scaling is wrong in SVG output

[Mauricio Faria de Oliveira]

To be clear, I don't think these should block the acceptance of this SRU
(I have seen different criteria to accept SRUs regarding DEP-3 headers),
but hopefully might be of some value for future SRUs, if you agree w/ it.

I'll refrain from accepting it for now as oracular-proposed seems to have
some regressions in autopkgtests [3], so let's see how that goes first.

Thanks again!

[3] https://ubuntu-archive-team.ubuntu.com/proposed-
migration/oracular/update_excuses.html#graphviz

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

Title:
  [SRU] scaling is wrong in SVG output

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2015017] Re: [SRU] scaling is wrong in SVG output

[Mauricio Faria de Oliveira]

Hi Dave (~waveform),

Thanks for all the work to review/sponsor this fix! (And several others!)
It's really appreciated.

In a comparatively small but relevant note, I'd like to humbly point out though
that some DEP-3 headers seem incorrect (IMHO) in the uploads AFAICT based in [1]
(section `Standard fields`):

+Author: David Huggins-Daines 
+Bug: 
https://gitlab.com/graphviz/graphviz/-/commit/a5606d101af1cc949908a6f0bc19caaa4eb31159
+Description: Corrects scale factor in SVG output

These headers are totally understandable with the context in this bug,
but it might not always be available when looking at it in the future.

If I understand it correctly:

`Author` isn't David (who proposed the patch; so, credit is certainly due, 
likely in the changelog, e.g., '[ Name ]' before the entry), but the upstream 
patch author
> Author or From (optional): This field can be used to record the name and 
> email of the patch author ...

`Bug` should be an upstream bug tracker, not the commit/patch:
> Bug- or Bug (optional): It contains one URL pointing to the related 
> bug ... 
> The Bug field is reserved for the bug URL in the upstream bug tracker. 
> Those fields can be used multiple times ... 
> The vendor name is explicitely encoded in the field name"

`Description` is OK, but looks more like `Subject`, as it's single line.
(BTW, this reads way better than the upstream commit title! :)

I think the correct form should be, starting from `git format-patch` or the 
`.patch`-suffixed URL [2],
which already gives us:
`From:`, which replaces `Author:` ("Author or From (optional)")
`Subject:`, which replaces `Description:` with a different/unstructured format 
("Description or Subject (required)")

And we would add 2 optional fields, but which are highly useful (and
more standard, considering most SRUs I've seen so far).

Bug-Ubuntu: http://bugs.launchpad.net/bugs/2015017
Origin: [,] 
https://gitlab.com/graphviz/graphviz/-/commit/a5606d101af1cc949908a6f0bc19caaa4eb31159

[1] https://dep-team.pages.debian.net/deps/dep3/
[2] 
https://gitlab.com/graphviz/graphviz/-/commit/a5606d101af1cc949908a6f0bc19caaa4eb31159.patch
[3] 
https://ubuntu-archive-team.ubuntu.com/proposed-migration/oracular/update_excuses.html#graphviz

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

Title:
  [SRU] scaling is wrong in SVG output

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921914] Re: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1

[Mauricio Faria de Oliveira]

Rejected from the unapproved queues for Noble, Mantic, Jammy, and Focal
per comment #14. Thanks!

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

Title:
  [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed
  quickml package post-installation script subprocess returned error
  exit status 1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064914] Re: Windows guest hangs after reboot from the guest OS

[Mauricio Faria de Oliveira]

Hi Sergio,

Thanks for the upload!

The bug and fix sound good and relatively simple to verify.

The SRU bug template is still missing Test Plan / Regression Potential,
so I'll mark it as Incomplete for the time being (I see it may be coming
soon, per "TBD").

While looking at the Björn's mention of the test case in RH BZ, that uses the 
`rdtsc.flat` kernel, which I couldn't find elsewhere. Do you know about it?
It's apparently a `rdtsc`/print loop we can replicate, if needed.

If I may, I'd suggest to test this in 3 ways:

1) unit test, with such rdtsc/print loop (and confirm the tsc value decreases 
after system_reset)
2) functional test, booting Windows (e.g., downloaded from MSFT Evaluation 
Center) and changing TSC manually to a problematic value (> 2^54) before reset, 
with the QEMU monitor or GDB, if possible?
3) regression test, booting Ubuntu kernel/initrd pairs (installer's should be 
enough) from supported releases, and checking they boot/reach a prompt.

I realize that looks like too much for a simple fix, but this is QEMU on amd64.
I'd be quite willing to help with that if needed. :)

Thanks again!

** Changed in: qemu (Ubuntu Jammy)
   Status: Triaged => Incomplete

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

Title:
  Windows guest hangs after reboot from the guest OS

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064580] Re: Please update the package to 20240320.00

[Mauricio Faria de Oliveira]

Chlo, thanks for the updates to the SRU template.

'Where problems could occur' is indeed generic as can be expected for
such a big update, but the information there is certainly helpful.

The one point/patch that applies to Ubuntu more directly in the big update 
(comment #5)
is a gpg/apt change [1], which could be mentioned, but the text/verification 
does tell
there is plenty of testing, and since gpg/apt is exercised so often, that looks 
covered!

Thanks again to you and Utkarsh for all the work done on this in such a
quick timeframe.

[1]
https://github.com/GoogleCloudPlatform/osconfig/commit/e41a055704c2b08e41d722e0b27d3ae8a40fbecc

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

Title:
  Please update the package to 20240320.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064580] Re: Please update the package to 20240320.00

[Mauricio Faria de Oliveira]

Hi Utkarsh,

Thanks for the pointer to the dependency changes as requested by the SRU
exception, and update to the bug template.

I had seen that in the diff (and filter it out, per the size, of
course), but I think what the request in the SRU exception is, is
something easier to parse re: the version diff per dependency.

Since I'm not sure that is exactly what it means, and may be my own
interpretation, I'll handle it:

$ curl -sL 
'https://git.launchpad.net/~ubuntu-core-dev/+git/google-osconfig-agent/patch/?id=abbf5d88edb27008d0899f313db347f3eccece4b'
 | filterdiff -i 'a/go.mod' | grep '^[+-].*/' | sort -k2,3 -V
+   cloud.google.com/go v0.110.0 // indirect
-   cloud.google.com/go v0.110.0 // indirect
+   cloud.google.com/go/compute v1.19.1 // indirect
-   cloud.google.com/go/iam v0.12.0 // indirect
+   cloud.google.com/go/iam v0.13.0 // indirect
+   cloud.google.com/go/logging v1.7.0 // indirect
+   cloud.google.com/go/longrunning v0.4.1 // indirect
-   cloud.google.com/go/longrunning v0.4.1 // indirect
+   github.com/golang/glog v1.1.0 // indirect
+   github.com/golang/groupcache v0.0.0-20200121045136-8c9f03a8e57e // 
indirect
+   github.com/golang/protobuf v1.5.3 // indirect
+   github.com/googleapis/enterprise-certificate-proxy v0.2.3 // indirect
+   github.com/googleapis/gax-go/v2 v2.7.1 // indirect
+   github.com/google/uuid v1.3.0 // indirect
+   github.com/julienschmidt/httprouter v1.3.0 // indirect
+   github.com/konsorten/go-windows-terminal-sequences v1.0.3 // indirect
+   github.com/pkg/errors v0.9.1 // indirect
+   github.com/sirupsen/logrus v1.6.0 // indirect
-   golang.org/x/crypto v0.6.0
+   golang.org/x/crypto v0.17.0
+   golang.org/x/net v0.17.0 // indirect
-   golang.org/x/oauth2 v0.5.0
+   golang.org/x/oauth2 v0.7.0
+   golang.org/x/sync v0.1.0 // indirect
-   golang.org/x/sys v0.5.0
+   golang.org/x/sys v0.15.0
+   golang.org/x/text v0.14.0 // indirect
+   golang.org/x/xerrors v0.0.0-20220907171357-04be3eba64a2 // indirect
-   google.golang.org/api v0.110.0
+   google.golang.org/api v0.114.0
+   google.golang.org/appengine v1.6.7 // indirect
-   google.golang.org/genproto v0.0.0-20230223222841-637eb2293923
+   google.golang.org/genproto v0.0.0-20230410155749-daa745c078e1
-   google.golang.org/grpc v1.53.0
+   google.golang.org/grpc v1.56.3
-   google.golang.org/protobuf v1.28.1
+   google.golang.org/protobuf v1.30.0
+   go.opencensus.io v0.24.0 // indirect
--- a/go.mod
+++ b/go.mod

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

Title:
  Please update the package to 20240320.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064580] Please test proposed package

[Mauricio Faria de Oliveira]

Hello Philip, or anyone else affected,

Accepted google-osconfig-agent into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/google-osconfig-
agent/20240320.00-0ubuntu1~22.04.0 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: google-osconfig-agent (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  Please update the package to 20240320.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064580] Please test proposed package

[Mauricio Faria de Oliveira]

Hello Philip, or anyone else affected,

Accepted google-osconfig-agent into focal-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/google-osconfig-
agent/20240320.00-0ubuntu1~20.04.0 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Please update the package to 20240320.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064580] Re: Please update the package to 20240320.00

[Mauricio Faria de Oliveira]

The uploads for Jammy and Focal follow Oracular's too,
with additional changes to use a newer go version, as
already done in Focal (J: any > 1.21; F: 1.18 > 1.21).

Please address the SRU-related requests in comment #7.

Thanks!

** Changed in: google-osconfig-agent (Ubuntu Jammy)
   Status: New => Fix Committed

** Tags added: verification-needed-jammy

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

Title:
  Please update the package to 20240320.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064580] Re: Please update the package to 20240320.00

[Mauricio Faria de Oliveira]

The uploads for Noble and Mantic follow Oracular's as expected (#5),
the only differences being timestamps and a securiy patch in Mantic.

The code changes look good AFAICT, and the vendored deps changes
are such in size that require validation by testing.

Please address the request in comment #6 / SRU exception page [1],
and if at all possible, add a 'Where problems could occur' section
per SRU bug template [2] (even if it's generic, per the big scope).

Regarding the mention about some archs FTBFS with the new version,
the reasoning for it being acceptable looks OK, but we might want
to check if previous version binaries should be removed, I guess.

I'll continue tomorrow, as possible, when the uploads for Jammy
and Focal (and earlier, as Bionic and Xenial are listed) arrive.

Thanks!

[1] https://wiki.ubuntu.com/google-osconfig-agent-Updates
[2] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

** Changed in: google-osconfig-agent (Ubuntu Noble)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  Please update the package to 20240320.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064580] Please test proposed package

[Mauricio Faria de Oliveira]

Hello Philip, or anyone else affected,

Accepted google-osconfig-agent into mantic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/google-osconfig-
agent/20240320.00-0ubuntu1~23.10.0 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Please update the package to 20240320.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064580] Please test proposed package

[Mauricio Faria de Oliveira]

Hello Philip, or anyone else affected,

Accepted google-osconfig-agent into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/google-osconfig-
agent/20240320.00-0ubuntu1~24.04.0 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: google-osconfig-agent (Ubuntu Mantic)
   Status: New => Fix Committed

** Tags added: verification-needed-mantic

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

Title:
  Please update the package to 20240320.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064580] Re: Please update the package to 20240320.00

[Mauricio Faria de Oliveira]

It looks like the uploads are coming in 
(noble 25 mins ago, mantic 16 mins ago).

After your code/package-wise tasks are done,
could you please take a look at listing the
vendorized deps changes, as per SRU exception?

I realize that might be a lot, but it's in the
exception, so it must be asked for; please let
us know if there is any issues with that, and
we'll discuss!

Thanks!

@ https://wiki.ubuntu.com/google-osconfig-agent-Updates

'''
Vendored dependencies
If any pinned and vendored dependencies in this package change as part of the 
SRU then the following must be present in the SRU bug.

* Details of vendored package version changes are present in the SRU bug

* It is preferred that links to changelogs for the vendored packages are
also present in the SRU bug

Changes in vendored dependencies may result in requests for additional
testing.

'''

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

Title:
  Please update the package to 20240320.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064580] Re: Please update the package to 20240320.00

[Mauricio Faria de Oliveira]

Updating the Oracular bug task to Fix Committed, as the
reference to this bug is already in oracular-proposed [1].

The Oracular Oriole (active development)

20240320.00-0ubuntu1proposed (main) 9 hours ago

Changelog
google-osconfig-agent (20240320.00-0ubuntu1) oracular; urgency=medium

  [ Chloé 'kajiya' Smith ]
  * New upstream version for upstream tag 20240320.00. (LP: #2064580)
  ...

[1] https://launchpad.net/ubuntu/+source/google-osconfig-agent

** Changed in: google-osconfig-agent (Ubuntu Oracular)
   Status: New => 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/2064580

Title:
  Please update the package to 20240320.00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064580] Re: Please update the package to 20240320.00

[Mauricio Faria de Oliveira]

This bug received a prioritization request for SRU review.

Unfortunately, apparently the uploads for stable releases
haven't happened today so far (but I will check tomorrow).

Meanwhile, I have familiarized myself with the upload for
Oracular, which is expected to be quite similar to stable
releases (all releases will get the same version update);
and with the upstream changes (which closely match that).

AFAICT there is actually _very little_ changes to *code*
that have impacts to Ubuntu -- the bulk of changes (90%!)
are updates to the go version & vendorized dependencies.

Among the code changes, there is Windows and yum/zypper
(other package managers), all these don't affect Ubuntu.

(So, it's curious whether the actual needed changes may
be in the dep updates; otherwise, the code changes that
would be needed could be accomplished with simple patch
SRUs, as far as I can tell / if not missing something.)

Finally, considering that 90%+ of effective changes are
go deps, and that build-time tests seem to be few / not
cover it all, it is required to have plenty of testing
before releasing it for stable releases.


Notes:
-

The upload in oracular-proposed; note it's quite big:

$ curl -sL
'https://launchpad.net/ubuntu/+archive/primary/+files/google-osconfig-
agent_20230504.00-0ubuntu3_20240320.00-0ubuntu1.diff.gz' | zcat >
oracular.debdiff

$ cat oracular.debdiff | diffstat -s 
 572 files changed, 29195 insertions(+), 11535 deletions(-)

But the vendorized deps changes are literally 90% of it:
(91% of files changes, 92% of insertions, 90% of deletions)

$ cat oracular.debdiff | filterdiff -i '*/debian/extra/vendor/*' | 
diffstat -s
 519 files changed, 26866 insertions(+), 10356 deletions(-)

@ debian/rules:
  9 override_dh_auto_configure:
 10 cp -r debian/extra/vendor ./
 11 dh_auto_configure
...
 24 override_dh_clean:
 25 dh_clean vendor/

Plus e2e_tests which are not built/tested/shipped, and examples:
(4.2% of files changed, 6.3% of insertions, 2.9% of deletions)

@ debian/rules:
3 export DH_GOLANG_EXCLUDES := e2e_tests

$ cat oracular.debdiff | filterdiff -i '*/e2e_tests/*' | diffstat -s
 14 files changed, 1179 insertions(+), 277 deletions(-)

$ cat oracular.debdiff | filterdiff -i '*/examples/*' | diffstat -s
 10 files changed, 674 insertions(+), 10 deletions(-)

That is, approximately 95%/98%/93% of the modifications, in total.

Looking at what is left:
(5% of files changes, 1.6% of insertions, 7.7% of deletions)

$ cat oracular.debdiff | filterdiff -x '*/debian/extra/vendor/*' -x 
'*/e2e_tests/*' -x '*/examples/*'  | diffstat -s
 29 files changed, 476 insertions(+), 892 deletions(-)

Taking out a few other files that are not code changes either
(e.g., build-time tests, upstream docs, and changelog/series),
the list is quite small:

$ cat oracular.debdiff | filterdiff -x '*/debian/extra/vendor/*' -x 
'*/e2e_tests/*' -x '*/examples/*' \
  -x '*/*_test.go' -x '*/OWNERS' -x '*/README.md' -x 
'*/debian/changelog' -x '*/debian/patches/series' | diffstat
 agentconfig/agentconfig.go 
 |2
 agentendpoint/agentendpoint.go 
 |2
 attributes/attributes.go   
 |2
 clog/clog.go   
 |   18 +-
 config/exec_resource.go
 |4
 config/repository_resource.go  
 |   59 +
 
debian/patches/0001-Disable-TestGetAptGPGKey-for-LP-build-environment.patch |   
21 +++
 go.mod 
 |   43 +-
 go.sum 
 |  806 ---...
 main.go
 |2
 main_linux.go  
 |2
 main_windows.go
 |4
 ospatch/updates_windows.go 
 |2
 packages/wua_windows.go
 |   49 +--
 packages/yum.go
 |6
 packages/zypper.go 
 |   39 --
 policies/apt.go
 |   40 --
 policies/recipes/steps.go  
 |4
 util/mocks/match.go 

[Bug 1988942] Re: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)

[Mauricio Faria de Oliveira]

Hi Jorge,

Thanks for testing and the update.

Re: mantic-proposed, that is weird; any mirrors in place? It looks OK in the 
archive:
(All cinder binary packages were available in the verification of bug 1987663.)

$ curl -s 
http://archive.ubuntu.com/ubuntu/dists/mantic-proposed/main/binary-amd64/Packages.xz
 | xzcat | grep-dctrl -S cinder -s Package,Source,Version
Package: cinder-api
Source: cinder
Version: 2:23.0.0-0ubuntu1.2

Package: cinder-backup
Source: cinder
Version: 2:23.0.0-0ubuntu1.2

Package: cinder-common
Source: cinder
Version: 2:23.0.0-0ubuntu1.2

Package: cinder-scheduler
Source: cinder
Version: 2:23.0.0-0ubuntu1.2

Package: cinder-volume
Source: cinder
Version: 2:23.0.0-0ubuntu1.2

Package: python3-cinder
Source: cinder
Version: 2:23.0.0-0ubuntu1.2


And regarding the failure, even with manually downloaded packages, can you 
confirm it worked with the test packages for Mantic, used to produce the 
debdiffs? -- That can help identifying/bisecting issues.

Thanks!

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

Title:
  Failed to set image property. Invalid input for field/attribute
  simplestreams_metadata. Value: ... is too long (HTTP 400)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1988942/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Mauricio Faria de Oliveira]

Hi Timo,

Thanks for looking into this.

> Wouldn't it be less risky to just backport 8.0.4 instead of 24/36
commits to mantic/jammy?

So so; and there's more involved.

There are near-future steps being taken in that direction already (SRU
exception to be discussed in the upcoming Engineering Sprint), but that
is likely for a time-frame longer than these SRUs (which are much wanted
sooner), considering the test requirements and preparation work that is
needed.

The regression risk in this case is mostly with the Jammy GA/5.15
kernel, since its HWE kernel (6.5) and Mantic GA/6.5 kernel are already
unusable with their current crash version.

To that extent, AFAICT from the individual patch reviews, they are all
built with backwards compatibility, so as long as crash with the Jammy
5.15 GA kernel is well tested (and the detailed test plans should ensure
this), that should be OK.

Therefore, under the assumption/understanding that the regression risk
is indeed low (and there are benefits of making crash usable at all with
the 6.5-based kernel HWE/GA kernels), and additionally considering the
engineering time already put into this (if results are aligned with SRU
policy), it would seem reasonable to move forward with the SRUs instead
of MREs.

Thanks again.

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1988942] Re: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)

[Mauricio Faria de Oliveira]

Hi Jorge,

Thanks for verifying jammy-proposed.

Could you please verify mantic-proposed as well?
The fix release to jammy-updates depends on release for mantic-updates (ie, 
verification of mantic-proposed).

Thanks again!

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

Title:
  Failed to set image property. Invalid input for field/attribute
  simplestreams_metadata. Value: ... is too long (HTTP 400)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1988942/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1987663] Re: cinder-volume: "Failed to re-export volume, setting to ERROR" with "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected" on service startup

[Mauricio Faria de Oliveira]

Verification done on {mantic,jammy,focal}-proposed.

The detailed verification steps as per comment #3
are attached. This is the summary with key steps.

With the packages from -proposed, when (re)starting 
{cinder-volume,tgt}.service, 
the cinder-volume service is started _after_ the tgt service, and
the volumes remain with 'in-use' status (no longer 'error' status).

Reproducer (45-second startup delay in tgt.service)
---

FILE=/etc/systemd/system/tgt.service.d/start-delay.conf
mkdir -p $(dirname $FILE)
cat < $FILE
[Service]
ExecStartPre=$(which sleep) 45
EOF
systemctl daemon-reload

# systemctl show tgt.service | grep ^ExecStartPre=
ExecStartPre={ path=/usr/bin/sleep ; argv[]=/usr/bin/sleep 45 ; 
ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; 
status=0/0 }

# date; systemctl restart cinder-volume.service tgt.service;
date

Before / packages from -updates:
---

... Notice that cinder-volume.service is Started _BEFORE_ tgt.service
... And the 'tgtadm' error _IS_ seen in the logs.
... And volumes are listed with 'error' Status.

mantic:

root@cinder-mantic:~# dpkg -l | grep cinder-volume
ii  cinder-volume   2:23.0.0-0ubuntu1.1 
all  Cinder storage service - Volume server

root@cinder-mantic:~# date; systemctl restart cinder-volume.service 
tgt.service; date
Tue Apr 30 15:54:43 UTC 2024
Tue Apr 30 15:55:29 UTC 2024

root@cinder-mantic:~# journalctl -b -u cinder-volume.service -u 
tgt.service | grep Start | tail -3
Apr 30 15:54:43 cinder-mantic systemd[1]: Started cinder-volume.service 
- OpenStack Cinder Volume.
Apr 30 15:54:44 cinder-mantic systemd[1]: Starting tgt.service - 
(i)SCSI target daemon...
Apr 30 15:55:29 cinder-mantic systemd[1]: Started tgt.service - (i)SCSI 
target daemon.

root@cinder-mantic:~# grep 'ERROR cinder.volume.manager' 
/var/log/cinder/cinder-volume.log | grep tgtadm
2024-04-30 15:54:54.603 13692 ERROR cinder.volume.manager (out, 
err) = cinder.privsep.targets.tgt.tgtadm_show()
2024-04-30 15:54:54.603 13692 ERROR cinder.volume.manager Command: 
tgtadm --lld iscsi --op show --mode target
2024-04-30 15:54:54.603 13692 ERROR cinder.volume.manager Stderr: 
'tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not 
connected\n'

root@cinder-mantic:~# cinder list

+--++-+--++-+--+-+
| ID   | Status | Name| Size | 
Consumes Quota | Volume Type | Bootable | Attached to |

+--++-+--++-+--+-+
| 45b39ae0-2552-4703-a664-ae8de77a23a1 | error  | test-volume | 1| 
True   | __DEFAULT__ | false| |

+--++-+--++-+--+-+


jammy:

root@cinder-jammy:~# dpkg -l | grep cinder-volume
ii  cinder-volume   2:20.3.1-0ubuntu1.1 
all  Cinder storage service - Volume server

root@cinder-jammy:~# date; systemctl restart cinder-volume.service 
tgt.service; date
Tue Apr 30 15:54:45 UTC 2024
Tue Apr 30 15:55:30 UTC 2024

root@cinder-jammy:~# journalctl -b -u cinder-volume.service -u 
tgt.service | grep Start | tail -3
Apr 30 15:54:45 cinder-jammy systemd[1]: Started OpenStack Cinder 
Volume.
Apr 30 15:54:45 cinder-jammy systemd[1]: Starting (i)SCSI target 
daemon...
Apr 30 15:55:30 cinder-jammy systemd[1]: Started (i)SCSI target daemon.

root@cinder-jammy:~# grep 'ERROR cinder.volume.manager' 
/var/log/cinder/cinder-volume.log | grep tgtadm
2024-04-30 15:54:55.918 14576 ERROR cinder.volume.manager (out, 
err) = cinder.privsep.targets.tgt.tgtadm_show()
2024-04-30 15:54:55.918 14576 ERROR cinder.volume.manager Command: 
tgtadm --lld iscsi --op show --mode target
2024-04-30 15:54:55.918 14576 ERROR cinder.volume.manager Stderr: 
'tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not 
connected\n'

root@cinder-jammy:~# cinder list

+--++-+--++-+--+-+
| ID   | Status | Name| Size | 
Consumes Quota | Volume Type | Bootable | Attached to |

+--++-+--++-+--+-+
| 88024eca-203c-4f8f-9ff0-4de704041a2f | error  | test-volume | 1| 
True   | 

[Bug 2063221] Re: Drop libglib2.0-0 transitional package

[Mauricio Faria de Oliveira]

The updates look good, thanks!

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

Title:
  Drop libglib2.0-0 transitional package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2052985] Re: [SRU] Upgrade Rust to 1.76.0

[Mauricio Faria de Oliveira]

** Changed in: rustc (Ubuntu)
   Status: Incomplete => New

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

Title:
  [SRU] Upgrade Rust to 1.76.0

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063221] Re: Drop libglib2.0-0 transitional package

[Mauricio Faria de Oliveira]

Hi Jeremy,

This looks mostly good, AFAICT.

Could you please complete the SRU bug template by adding the section
'Where problems could occur' / 'Regression potential'? [1]

And although the 'Test Case' is feasible to understand, based on the 'Impact' 
section, it would be nice to have a 'functional' test, if at all 
possible/reasonably doable.
For example, I  tried to reproduce the thunderbird deb2snap issue, but it 
didn't. I realize there might be a more complex package setup/install list to 
trigger it, but maybe there's something simpler that you are aware of.
(Or if it's too complex / not worth it, just clarifying that and mentioning 
what shouldn't change / how to check for no regressions, would be OK too; I 
tried to convey that in comment #1).

Thanks!

[1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

** Changed in: glib2.0 (Ubuntu Noble)
   Status: In Progress => Incomplete

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

Title:
  Drop libglib2.0-0 transitional package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063221] Re: Drop libglib2.0-0 transitional package

[Mauricio Faria de Oliveira]

I tested this with a local package build and local repo in a mantic container,
doing an `apt --dry-run dist-upgrade` without/with that repo (w/ noble apt 
sources list),
and manually download/run noble's release upgrader without/with that repo.

The behavior is the same (ie, no regressions) as expected;
libglib2.0-0 is removed in favor of libglib2.0-0t64 in all cases.

Test 1)

Just Noble:

$ apt-cache show libglib2.0-bin | grep Version:
Version: 2.80.0-6ubuntu1
Version: 2.78.0-2

$ sudo apt --dry-run dist-upgrade 2>&1 | awk '{ print NR ": " $0 }' | 
fgrep libglib2.0
17:   libevent-core-2.1-7 libext2fs2 libgdbm-compat4 libgdbm6 
libglib2.0-0
30:   libgdbm6t64 libglib2.0-0t64 libgnutls30t64 libgpgme11t64
79:   libglib2.0-bin libglib2.0-data libgmp10 libgomp1 libgpg-error-l10n
154: Remv libelf1 [0.189-4] [libglib2.0-bin:amd64 libbpf1:amd64 
iproute2:amd64 ]
156: Inst libglib2.0-bin [2.78.0-2] (2.80.0-6ubuntu1 Ubuntu:24.04/noble 
[amd64]) []
378: Remv libglib2.0-0 [2.78.0-2] [libappstream4:amd64 
open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64 
libnetplan0:amd64 ]
379: Inst libglib2.0-0t64 (2.80.0-6ubuntu1 Ubuntu:24.04/noble [amd64]) 
[open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64 ]
611: Inst libglib2.0-data [2.78.0-2] (2.80.0-6ubuntu1 
Ubuntu:24.04/noble [all])
927: Conf libglib2.0-bin (2.80.0-6ubuntu1 Ubuntu:24.04/noble [amd64])
1070: Conf libglib2.0-0t64 (2.80.0-6ubuntu1 Ubuntu:24.04/noble [amd64])
1201: Conf libglib2.0-data (2.80.0-6ubuntu1 Ubuntu:24.04/noble [all])

Noble and local build/repo:

$ apt-cache show libglib2.0-bin | grep Version:
Version: 2.80.0-6ubuntu3
Version: 2.80.0-6ubuntu1
Version: 2.78.0-2

$ sudo apt --dry-run dist-upgrade 2>&1 | awk '{ print NR ": " $0 }' | 
fgrep libglib2.0
17:   libevent-core-2.1-7 libext2fs2 libgdbm-compat4 libgdbm6 
libglib2.0-0
30:   libgdbm6t64 libglib2.0-0t64 libgnutls30t64 libgpgme11t64
79:   libglib2.0-bin libglib2.0-data libgmp10 libgomp1 libgpg-error-l10n
154: Remv libelf1 [0.189-4] [libglib2.0-bin:amd64 libbpf1:amd64 
iproute2:amd64 ]
156: Inst libglib2.0-bin [2.78.0-2] (2.80.0-6ubuntu3 localhost [amd64]) 
[]
378: Remv libglib2.0-0 [2.78.0-2] [libappstream4:amd64 
open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64 
libnetplan0:amd64 ]
379: Inst libglib2.0-0t64 (2.80.0-6ubuntu3 localhost [amd64]) 
[open-vm-tools:amd64 libc-dev-bin:amd64 libc-bin:amd64 libc6-dev:amd64 ]
611: Inst libglib2.0-data [2.78.0-2] (2.80.0-6ubuntu3 localhost [all])
927: Conf libglib2.0-bin (2.80.0-6ubuntu3 localhost [amd64])
1070: Conf libglib2.0-0t64 (2.80.0-6ubuntu3 localhost [amd64])
1201: Conf libglib2.0-data (2.80.0-6ubuntu3 localhost [all])


Test 2)

Just Noble:

$ dpkg -l | fgrep libglib2.0
rc  libglib2.0-0:amd64  2.78.0-2
amd64GLib library of C routines
ii  libglib2.0-0t64:amd64   2.80.0-6ubuntu1 
amd64GLib library of C routines
ii  libglib2.0-bin  2.80.0-6ubuntu1 
amd64Programs for the GLib library
ii  libglib2.0-data 2.80.0-6ubuntu1 
all  Common files for GLib library

$ dpkg -l | grep thunderbird
ii  thunderbird 2:1snap1-0ubuntu3   
amd64Transitional package - thunderbird -> thunderbird snap

$ snap list thunderbird
Name Version Rev  Tracking   Publisher   Notes
thunderbird  115.10.1-1  470  latest/stable  canonical✓  -

Noble and local build/repo:

$ dpkg -l | fgrep libglib2.0
rc  libglib2.0-0:amd64  2.78.0-2
amd64GLib library of C routines
ii  libglib2.0-0t64:amd64   2.80.0-6ubuntu3 
amd64GLib library of C routines
ii  libglib2.0-bin  2.80.0-6ubuntu3 
amd64Programs for the GLib library
ii  libglib2.0-data 2.80.0-6ubuntu3 
all  Common files for GLib library

$ dpkg -l | grep thunderbird
ii  thunderbird 2:1snap1-0ubuntu3   
amd64Transitional package - thunderbird -> thunderbird snap

$ snap list thunderbird
Name Version Rev  Tracking   Publisher   Notes
thunderbird  115.10.1-1  470  latest/stable  canonical✓  -

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

Title:
  Drop libglib2.0-0 transitional package

To 

[Bug 2061891] Re: Noble upgrade breaks iptables-persistent and netfilter-persistent usage

[Mauricio Faria de Oliveira]

Ok; thanks for clarifying.

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

Title:
  Noble upgrade breaks iptables-persistent and netfilter-persistent
  usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2061891/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063464] Re: systemd-resolved wasn't installed on upgrade from Jammy to Noble

[Mauricio Faria de Oliveira]

Moving from Fix Committed back to In Progress as this isn't in -proposed yet,
and In Progress reflects 'uploaded' better.

(I don't mean to be pedantic, but this avoids confusion; even though the git
repo was mentioned, AFAIK the 'Ubuntu' project in bug tasks means the status
Fix Committed should be interpreted as -proposed/Ubuntu Archive, not others.)

https://wiki.ubuntu.com/Bugs/Bug%20statuses

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Fix Committed => 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/2063464

Title:
  systemd-resolved wasn't installed on upgrade from Jammy to Noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063464/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064090] Re: Automatically installed bit not transitioned to t64 libraries

[Mauricio Faria de Oliveira]

Moving from Fix Committed back to In Progress as this isn't in -proposed yet,
and In Progress reflects 'uploaded' better.

(I don't mean to be pedantic, but this avoids confusion; even though the git
repo was mentioned, AFAIK the 'Ubuntu' project in bug tasks means the status
Fix Committed should be interpreted as -proposed/Ubuntu Archive, not others.)

https://wiki.ubuntu.com/Bugs/Bug%20statuses

** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
   Status: Fix Committed => 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/2064090

Title:
  Automatically installed bit not transitioned to t64 libraries

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2064090/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061891] Re: Noble upgrade breaks iptables-persistent and netfilter-persistent usage

[Mauricio Faria de Oliveira]

Hi Nick and Julian,

Thanks for the fix and SRU template!

Question:

IIUIC, the fix simply removes 'ufw' if '{iptables,netfilter}-persistent'
is installed.

But is it possible that removing ufw is the wrong thing to do in some 
particular case?  
Say, if the user actually used/configured ufw instead of the -persistent 
packages.

That seems possible, as users could have both installed previously, right?
(The bug report says both ufw/-persistent 'had no conflicts in jammy').

Thanks!

PS: I added an 'Other Info' section to the SRU template to clarify the
'fix released' in comment #1.

** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
   Status: In Progress => Incomplete

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

Title:
  Noble upgrade breaks iptables-persistent and netfilter-persistent
  usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2061891/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061891] Re: Noble upgrade breaks iptables-persistent and netfilter-persistent usage

[Mauricio Faria de Oliveira]

** Description changed:

- [Impact / Original Description]
+ [Impact]
+ ufw and -persistent packages both manage the firewall, hence they conflict 
but they accidentally had no conflicts in jammy. If both are installed, 
persistent packages will store and restore firewall configuration, so ufw 
cannot really be used.
  
- Upgrade from Jammy to Noble breaks iptables-persistent and netfilter-
- persistent firewall configuration if ufw is also installed pre-upgrade.
+ Noble adds a conflicts from ufw to the persistent packages, but we end
+ up removing the persistent packages rather than the ufw which is wrong -
+ they are in charge.
+ 
+ [Test plan]
+ persistent and netfilter-persistent should remain installed, and ufw removed 
to preserve user config.
+ 
+ [Where problems could occur]
+ There may be ufw reverse dependencies that could get removed.
+ 
+ [Other Info]
+ The fix (released) in 1:24.04.15 is reverted and improved in 1:24.04.17 
(upload).
+ 
+ [Original bug report]
+ Upgrade from Jammy to Noble breaks iptables-persistent and 
netfilter-persistent firewall configuration if ufw is also installed 
pre-upgrade., removing them.
  
  from /var/log/dist-upgrade/apt.log:
  Broken ufw:amd64 Breaks on iptables-persistent:amd64 < 1.0.16 -> 1.0.20 @ii 
umU >
    Considering iptables-persistent:amd64 -1 as a solution to ufw:amd64 5
    Added iptables-persistent:amd64 to the remove list
    Conflicts//Breaks against version 1.0.16 for iptables-persistent but that 
is not InstVer, ignoring
  Broken ufw:amd64 Breaks on netfilter-persistent:amd64 < 1.0.16 -> 1.0.20 @ii 
umU >
    Considering netfilter-persistent:amd64 0 as a solution to ufw:amd64 5
    Added netfilter-persistent:amd64 to the remove list
    Conflicts//Breaks against version 1.0.16 for netfilter-persistent but that 
is not InstVer, ignoring
    MarkDelete iptables-persistent:amd64 < 1.0.16 -> 1.0.20 @ii umU > FU=0
    Fixing ufw:amd64 via remove of iptables-persistent:amd64
    MarkDelete netfilter-persistent:amd64 < 1.0.16 -> 1.0.20 @ii umU > FU=0
    Fixing ufw:amd64 via remove of netfilter-persistent:amd64
  
  ufw 0.36.2-1 add the breaks
  $ apt show ufw
  Package: ufw
  Version: 0.36.2-6
  Priority: standard
  Section: admin
  Origin: Ubuntu
  Maintainer: Jamie Strandboge 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 869 kB
  Depends: iptables, ucf, python3:any, debconf (>= 0.5) | debconf-2.0
  Suggests: rsyslog
  Breaks: iptables-persistent, netfilter-persistent
  Homepage: https://launchpad.net/ufw
  Task: standard
  Download-Size: 169 kB
  APT-Manual-Installed: no
  APT-Sources: http://phx-ad-3.clouds.archive.ubuntu.com/ubuntu noble/main 
amd64 Packages
  Description: program for managing a Netfilter firewall
   The Uncomplicated FireWall is a front-end for iptables, to make managing a
   Netfilter firewall easier. It provides a command line interface with syntax
   similar to OpenBSD's Packet Filter. It is particularly well-suited as a
   host-based firewall.
  
  Post do-release-upgrade, iptables-persistent and netfilter-persistent
  are removed, which breaks any machines that relied on their
  configuration.
- 
- [Test Plan]
- 
- 1. Start a Jammy LXD container and obtain a shell.
- 
- $ lxc launch ubuntu-daily:jammy jammy
- $ lxc exec jammy bash
- 
- 2. In the container, install netfilter-persistent and iptables-
- persistent.
- 
- $ apt install netfilter-persistent iptables-persistent -y
- 
- 3. Run a release upgrade. To test with noble-proposed, the --proposed
- flag is needed.
- 
- $ do-release-upgrade --proposed
- 
- 4. Answer prompts as needed so that the upgrade runs as expected. After
- the upgrade has finished, verify that the packages have not been
- removed.
- 
- $ apt policy netfilter-persistent iptables-persistent
- 
- 5. Check the upgrade log to verify messages are present explaining that
- these packages are kept.
- 
- $ grep "Keeping.*-persistent" /var/log/dist-upgrade/main.log
- 
- [Where problems could occur]
- 
- This quirk requires manipulating the apt cache. It does so only for the
- ufw, netfilter-persistent, and iptables-persistent packages. If these
- package names were misspelled in the code, that would cause the quirk to
- be wrong. Any problems would most likely be surrounding whether or not
- these packages are installed. This quirk _should_ do nothing when (a)
- not upgrading from jammy, (b) ufw is not installed, or (c) neither
- netfilter-persistent nor iptables-persistent are installed.

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

Title:
  Noble upgrade breaks iptables-persistent and netfilter-persistent
  usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2061891/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1989078] Re: libvirt-qemu apparmor profile doesn't allow locking of AAVMF firmware

[Mauricio Faria de Oliveira]

Updating the verification tags for the new version,
agreeing with Christian's assessment in comment 12,
and verifying that the changes are still included:

$ pull-lp-debs -a arm64 libvirt-daemon-system focal 6.0.0-0ubuntu8.20
$ dpkg-deb -x libvirt-daemon-system_6.0.0-0ubuntu8.20_arm64.deb deb
$ fgrep -i -e '/usr/share/ovmf/**' -e 'owner 
/var/lib/libvirt/qemu/nvram/*_VARS' deb/etc/apparmor.d/abstractions/libvirt-qemu
  /usr/share/ovmf/** rk,
  /usr/share/OVMF/** rk,
  owner /var/lib/libvirt/qemu/nvram/*_VARS.fd rwk,
  owner /var/lib/libvirt/qemu/nvram/*_VARS.ms.fd rwk,
$

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

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

Title:
  libvirt-qemu apparmor profile doesn't allow locking of AAVMF firmware

To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/1989078/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

[Mauricio Faria de Oliveira]

The packages in focal-proposed have also been verified successfully in
real-world/non-synthetic tests by one of our Ubuntu Pro support
customers.

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

Title:
  libvirt domain is not listed/managed after libvirt restart with
  messages "internal error: no monitor path" and "Failed to load config
  for domain"

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

[Mauricio Faria de Oliveira]

Verification done on focal-proposed, following comments 23, 24, 25, 26.

Including in this comment a few key snippets from each test/comment.

---
Environment
---

LXD virtual machine

 lxc launch --vm ubuntu:focal lp2059272-focal
 lxc exec lp2059272-focal -- su - ubuntu

Enable proposed & debug symbols

cat 
for SLEEP in $(seq 0.1 0.1 2.0); do
<...>

All VMs are still managed by libvirt:

$ virsh list
 Id   Name State

 1test-vm-1running
 2test-vm-2running
 3test-vm-3running
 4test-vm-4running
 5test-vm-5running
 6test-vm-6running
 7test-vm-7running
 8test-vm-8running
 9test-vm-9running
 10   test-vm-10   running


---
Steps with test packages on Focal (shutdown-on-init)
---

Scenario 1) Shutdown wins race against XML update (ie, shutdown happens
first)

<...>

Now, let the qemuProcessReconnect thread continue, it will not update the XML 
file,
because 'quit' is set (ie, shutdown in progress)

(gdb) t 20
(gdb) p ((virNetDaemonPtr)anyobj)->quit
$2 = true

$ ls -l /run/libvirt/qemu/test-vm.xml
-rw--- 1 root root 10189 Apr 24 12:02 /run/libvirt/qemu/test-vm.xml

(gdb) c &

$ ls -l /run/libvirt/qemu/test-vm.xml
-rw--- 1 root root 10189 Apr 24 12:02 /run/libvirt/qemu/test-vm.xml

<...>

$ sudo grep 'Leaving the update of .* domain status XML' 
/var/log/libvirt/libvirtd-debug.log
2024-04-24 12:08:40.054+: 3770: info : qemuProcessReconnect:8157 : 
Leaving the update of 'test-vm' domain status XML for the next initialization 
(shutdown detected on this initialization).

<...>

$ sudo grep -e '
  
  

Scenario 2) Shutdown loses race against XML update (ie, update happens
first)

<...>

Instead, let the qemuProcessReconnect thread take the lock, and update
the XML file, but not unlock yet

<...>

$ ls -l /run/libvirt/qemu/test-vm.xml
-rw--- 1 root root 10189 Apr 24 12:02 /run/libvirt/qemu/test-vm.xml

(gdb) b virObjectUnlock thread 20 if anyobj == $ptr
(gdb) c

$ ls -l /run/libvirt/qemu/test-vm.xml
-rw--- 1 root root 10189 Apr 24 12:14 /run/libvirt/qemu/test-vm.xml

<...>

$ sudo grep -e '
  
  

Scenario 3) Shutdown happens along QEMU monitor calls (ie, calls don't
finish)

<...>

The XML was not updated, as expected:

$ ls -l /run/libvirt/qemu/test-vm.xml
-rw--- 1 root root 10189 Apr 24 12:14 /run/libvirt/qemu/test-vm.xml

$ sudo grep -e '
  
  
<...>

Now, the next time libvirtd starts, it correctly parses that XML:

 $ sudo systemctl start libvirtd.service

 $ journalctl -b -u libvirtd.service | grep -A1 error
 $
 
And libvirt is aware of the domain, and can manage it:

$ virsh list
 Id   Name  State
-
 1test-vm   running

$ virsh destroy test-vm
Domain test-vm destroyed

$ virsh undefine test-vm
Domain test-vm has been undefined

---
Steps with test packages on Focal (shutdown-on-runtime)
---

<...>
Check the formatter/options again; it is *STILL* referenced, not 0x0 anymore:

(gdb) t 20
(gdb) p xmlopt.privateData.format
$3 = (virDomainXMLPrivateDataFormatFunc) 0x7fd08c3437c0 

(gdb) p/x xmlopt.parent
$4 = {u = {dummy_align1 = 0x1cafe0026, dummy_align2 = 0x1cafe0026, s = 
{magic = 0xcafe0026, refs = 0x1}}, klass = 0x7fd080043170}

Let the save function continue, and libvirt finishes shutting down:
<...>
Check the VM status XML *after*:

$ ls -l /run/libvirt/qemu/test-vm.xml
-rw--- 1 root root 10251 Apr 24 12:28 /run/libvirt/qemu/test-vm.xml

$ sudo grep -e '
   

[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU

[Mauricio Faria de Oliveira]

Hi Giuseppe,

That's good news; thanks for testing!

Yes, that's correct. I'll review the patch for SRU considerations (e.g.,
potential side-effects/regressions for existing users, not always
directly clear from the code changes) and proceed if all is OK.

** Also affects: nova (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qemu (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: nova (Ubuntu)
   Status: New => Triaged

** Changed in: nova (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nova (Ubuntu)
 Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)

** Changed in: qemu (Ubuntu)
 Assignee: Sergio Durigan Junior (sergiodj) => (unassigned)

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

Title:
  EPYC-Rome model without XSAVES may break live migration since the
  removal of the flag on the physical CPU

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU

[Mauricio Faria de Oliveira]

Hi Giuseppe,

Please test nova version 2:21.2.4-0ubuntu2.7~ppa3 in the PPA.
(It's finished building and should be published in some time.)

The config change should be something along the lines of
`cpu_model_extra_flags = -xsaves` 


I couldn't test the package/functionality yet, but all of the
build-time unit tests have passed (just like official packages).

Please let us know how it goes.

Thanks,
Mauricio

** Changed in: qemu (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  EPYC-Rome model without XSAVES may break live migration since the
  removal of the flag on the physical CPU

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU

[Mauricio Faria de Oliveira]

Hmm, sorry, please hold; the unit tests caught an error.
I'll check that on Monday.

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

Title:
  EPYC-Rome model without XSAVES may break live migration since the
  removal of the flag on the physical CPU

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Mauricio Faria de Oliveira]

Mantic and Jammy built successfully in all supported architectures.
(riscv64 fails, but it also fails on mantic/jammy-release; it's OK.)

Uploaded! 
Thanks

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU

[Mauricio Faria de Oliveira]

Hi Giuseppe,

You're right, libvirt checks the specified model against its known
models.

However, the EPYC-Rome (not-v4) doesn't specify 'xsaves', just EPYC-Milan,
so it _seems_ the feature came from the default with cpu_model host-model,
which perhaps found EPYC Milan model closer to the host flags for reasons,
and used that CPU model file instead, which resulted in 'xsaves' required.

Since there is an increase in CPU feature flags changes recently (eg, the
'xsaves' you mentioned and also PKRU/xsave changes/regressions in kernel
5.15.0-85 per bug 2032164 comment 5), and these apparently may continue
to grow over time, as errata, security vulnerabilities, and other stuff
come up, maybe it's better not to rely on updates that require CPU model
updates in packages (specially 2 of them; qemu/libvirt).

So, in Yoga and later, Nova extends the 'libvirt.cpu_model_extra_flags' [1]
parsing with '+' and '-', so you can disable specific flags with '-', [2]
e.g., '-xsaves'.

This can be used with the unpatched QEMU, as it can use existing CPU
models.

I backported the patch to Focal/Ussuri's nova (it's present in Jammy/Yoga),
and built it in PPA [3].

Could you please test it, and see how it goes? More details in [1] and
[2].

Thanks!

[1] https://docs.openstack.org/nova/yoga/admin/cpu-models.html#cpu-
feature-flags

[2]
https://opendev.org/openstack/nova/commit/bcd6b42047ea9422a58a4273d831e23f2ea27092

[3] https://launchpad.net/~mfo/+archive/ubuntu/lp2048517

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

Title:
  EPYC-Rome model without XSAVES may break live migration since the
  removal of the flag on the physical CPU

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Mauricio Faria de Oliveira]

** Description changed:

  [Impact]
- Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
+ Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility in Mantic (release kernel 6.5) and Jammy (HWE kernel 6.5) unable
+ to parse the dump file. For example (there are more, in other areas):
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==
  
  [Fix]
- It is advisable to adopt commits that address the structural changes issue.
- ==
- 
- In 8.0.1:
- - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
- - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
- - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB
- 
- In 8.0.2:
- - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing
- 
- In 8.0.3:
- - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
- - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
- - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
- - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later
- 
- In 8.0.4
- - 7750e61fdb2a Support module memory layout change on Linux 6.4
- - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
- - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added
- 
- ==
+ It is advisable to adopt commits that address the structural changes:
+ - 10 patches from crash 8.0.1 into Jammy
+ - 02 patches from crash 8.0.2 into Jammy
+ - 12 patches from crash 8.0.3 into Jammy/Mantic
+ - 12 patches from crash 8.0.4 into Jammy/Mantic
  
  [Test Plan]
  
- On Jammy (LTS), which provides HWE (6.5) and GA (5.15) kernels,
+ On Jammy (LTS), which provides HWE (6.5) and release/GA (5.15) kernels,
  perform testing on both HWE (verify fixes) and GA (verify no regressions).
  
  There are detailed/per-commit test plans in the attachments:
  `crash_jammy_test_plan.txt.txt` and `crash_lunar_test_plan.txt`.
  
- And the general sysrq-trigger/makedumpfile/crash test:
+ A. Test the live mode (live-system form; without a dumpfile), and
+ B. Test the dump mode (dumpfile form: sysrq-trigger/makedumpfile/crash):
  
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump
  
  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
  
  WARNING: VA_BITS: calculated: 46  

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Mauricio Faria de Oliveira]

Jammy: patches 0001-0012 look good too!

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Mauricio Faria de Oliveira]

Partial review of the Jammy debdiff.
(Still in progress.)

Started with Jammy's patches 0012-0036, which are Mantic's patches 0001-0024 
(already reviewed).
Most patches are identical, and some have context-line changes, as expected 
(8.0.2/8.0.0 delta).
Just had a few changes.

$ for ((i=1; i<=24; i++)); do 
echo "PATCH $i"
echo
diff -U0 \
  mantic/crash-8.0.2/debian/patches/lp2038249-$(printf '%04d' $i)-*.patch \
  jammy/crash-8.0.0/debian/patches/lp2038249-$(printf '%04d' 
$((i+12)))-*.patch
echo
  done 2>&1 | less

patch 13
actually a backport, context line changes

patch 4
likewise

patch 8
augment backport notes

patch 11
actually a backport, context line changes, more
indentation issue, fixed

patch 36 (same note as patch 24/mantic)

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Mauricio Faria de Oliveira]

Today, I tackled the Mantic debdiff (made only a few changes; below).

It's now currently building in a PPA for all supported architectures,
(ppa:mfo/lp2038249) and if all goes well I will upload it to Mantic.

Thanks!
Mauricio

---

All 24 commits are included in Noble (12 in 8.0.4 and 12 in 8.0.3).
changelog OK
DEP3 tags OK

I reviewed each commit, with the exception of the big code additions
(patches 8,16: for maple tree and module memory layout): all look OK.

I fixed up patch 24, which is originally 2 trivial and short changes,
but had like ~3800 lines of indentation/formatting changes included
(certainly this wasn't intented, and mistakes happen; so I fixed it).

$ git show 55a43bcefa20161c7e56ed0e309e90e941f47efc | wc -l
57

$ wc -l 
debian/patches/lp2038249-0024-Fix-compilation-error-and-warning-with-gcc-4.8.5.patch
3865 
debian/patches/lp2038249-0024-Fix-compilation-error-and-warning-with-gcc-4.8.5.patch

We can all learn from this -- I will check .patch files with diffstat!

I also just augmented backport notes (thanks for those) to indicate
which functions/hunks had context lines modified/adjusted/refreshed,
since the patch is big (patch 15), and clarify variables (not) used.

-+[chengen - modify x86_64.c context]
++[chengen - modify context in x86_64.c: x86_64_ORC_init() and 
x86_64_get_framesize()]

-+[chengen - initialize init_tss to zero in xen_hyper.c]
++[chengen - initialize only init_tss to zero in xen_hyper.c (there is 
no stack_base yet)]

Very importantly, the detailed test plan will be key to validate the
changes are working correctly, considering their number and size.
Thanks again for it!

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Mauricio Faria de Oliveira]

** Description changed:

  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==
  
  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==
  
  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB
  
  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing
  
  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later
  
  In 8.0.4
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added
  
  ==
  
  [Test Plan]
  
+ On Jammy (LTS), which provides HWE (6.5) and GA (5.15) kernels,
+ perform testing on both HWE (verify fixes) and GA (verify no regressions).
  
  There are detailed/per-commit test plans in the attachments:
  `crash_jammy_test_plan.txt.txt` and `crash_lunar_test_plan.txt`.
  
  And the general sysrq-trigger/makedumpfile/crash test:
  
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump
  
  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
  
  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu".
  Type "show configuration" for configuration details.
  Find the GDB manual and other documentation resources online at:
  .
  
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  
  crash: seek error: kernel virtual 

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Mauricio Faria de Oliveira]

Marking Lunar as Won't Fix (EOL).

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Mauricio Faria de Oliveira]

crash 8.0.4 is available in noble (bug 2047861); checking the stable
releases' debdiffs.

** Changed in: crash (Ubuntu Noble)
   Status: Fix Committed => Fix Released

** Description changed:

  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==
  
  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==
  
  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB
  
  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing
  
  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later
  
- In 8.0.3++ (8.0.4 development)
+ In 8.0.4
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added
  
  ==
  
  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump
  
  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
  
  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu".
  Type "show configuration" for configuration details.
  Find the GDB manual and other documentation resources online at:
  .
  
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  
  crash: seek error: kernel virtual address: d59a92d48ae8  type: "possible"
  WARNING: cannot read cpu_possible_map
  crash: seek error: kernel virtual address: 

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Mauricio Faria de Oliveira]

Updated the SRU template as requested in comment #11 with the detailed
test plans provided in comments #16-#20.

** Changed in: crash (Ubuntu Lunar)
   Status: In Progress => Won't Fix

** Changed in: crash (Ubuntu Lunar)
   Importance: Medium => Undecided

** Changed in: crash (Ubuntu Lunar)
 Assignee: Chengen Du (chengendu) => (unassigned)

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1987663] Re: cinder-volume: "Failed to re-export volume, setting to ERROR" with "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected" on service startup

[Mauricio Faria de Oliveira]

Cloud Archive:

Caracal is addressed with Noble
Bobcat is addressed with Mantic
* Antelope is _not_ addressed with Lunar (no longer supported), needs patching 
in UCA [Triaged]
Zed is no longer supported (2024/04)
Yoga is addressed with Jammy
Wallaby is no longer supported (2024/04)
Victoria is no longer supported (2022/04)
Ussuri is _not_ adddressed with Focal (Bionic is in ESM/Pro), needs patching in 
Pro [Triaged]

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

Title:
  cinder-volume: "Failed to re-export volume, setting to ERROR" with
  "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint
  is not connected" on service startup

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1988942] Re: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)

[Mauricio Faria de Oliveira]

Cloud Archive:

Caracal is addressed with Noble
Bobcat is addressed with Mantic
* Antelope is _not_ addressed with Lunar (no longer supported), needs patching 
in UCA [Triaged]
Zed is no longer supported (2024/04)
Yoga is addressed with Jammy

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

Title:
  Failed to set image property. Invalid input for field/attribute
  simplestreams_metadata. Value: ... is too long (HTTP 400)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1988942/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1994521] Re: HPE3PAR: Failing to clone a volume having children

[Mauricio Faria de Oliveira]

Cloud Archive:

Caracal is addressed with Noble
Bobcat is addressed with Mantic
* Antelope is _not_ addressed with Lunar (no longer supported), needs patching 
in UCA [Triaged]
Zed is no longer supported (2024/04)
Yoga is addressed with Jammy

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

Title:
  HPE3PAR: Failing to clone a volume having children

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1994521/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1987663] Re: cinder-volume: "Failed to re-export volume, setting to ERROR" with "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected" on service startup

[Mauricio Faria de Oliveira]

Uploaded to Mantic, Jammy, Focal.

This upload has been coordinated with the Openstack Engineering team 
(~james-page) for bugs 1987663, 1988942, and 1994521.
Test PPA and build-time unit test summary in 
https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1987663/comments/16

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

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

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

** Changed in: cloud-archive/yoga
   Status: New => In Progress

** Changed in: cloud-archive/bobcat
   Status: New => In Progress

** Changed in: cloud-archive/antelope
   Status: New => Incomplete

** Changed in: cloud-archive/antelope
   Status: Incomplete => Triaged

** Changed in: cloud-archive/ussuri
   Status: Incomplete => Triaged

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

Title:
  cinder-volume: "Failed to re-export volume, setting to ERROR" with
  "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint
  is not connected" on service startup

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1994521] Re: HPE3PAR: Failing to clone a volume having children

[Mauricio Faria de Oliveira]

** Changed in: cinder (Ubuntu Jammy)
   Status: Incomplete => In Progress

** Changed in: cloud-archive/bobcat
   Status: New => Fix Released

** Changed in: cloud-archive/antelope
   Status: New => Triaged

** Changed in: cloud-archive/yoga
   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/1994521

Title:
  HPE3PAR: Failing to clone a volume having children

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1994521/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1988942] Re: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)

[Mauricio Faria de Oliveira]

** Changed in: cloud-archive/antelope
   Status: In Progress => Triaged

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

Title:
  Failed to set image property. Invalid input for field/attribute
  simplestreams_metadata. Value: ... is too long (HTTP 400)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1988942/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1988942] Re: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)

[Mauricio Faria de Oliveira]

Uploaded to Mantic, Jammy.
 
This upload has been coordinated with the Openstack Engineering team 
(~james-page) for bugs 1987663, 1988942, and 1994521.
Test PPA and build-time unit test summary in 
https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1987663/comments/16

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

Title:
  Failed to set image property. Invalid input for field/attribute
  simplestreams_metadata. Value: ... is too long (HTTP 400)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1988942/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1994521] Re: HPE3PAR: Failing to clone a volume having children

[Mauricio Faria de Oliveira]

Uploaded to Jammy.

This upload has been coordinated with the Openstack Engineering team 
(~james-page) for bugs 1987663, 1988942, and 1994521.
Test PPA and build-time unit test summary in 
https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1987663/comments/16

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

Title:
  HPE3PAR: Failing to clone a volume having children

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1994521/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1994521] Re: HPE3PAR: Failing to clone a volume having children

[Mauricio Faria de Oliveira]

Hi Seyeong,

Thanks for the patches!

In the future, could you please add DEP-3 headers [1] to them?
(usually just 'Bug-Ubuntu:'/'Origin:' are needed on git patches)

Also, it's a good practice to name the patch files with the bug
prefix (this is style, not requirement, but it helps when there
is multiple bugs per upload, and with maintenance over time).

I have handled these in this upload, as the changes are minor.
Thanks again!

[1] https://dep-team.pages.debian.net/deps/dep3/

$ head -n2 debian/patches/lp1994521-*

==> 
debian/patches/lp1994521-0001-HPE-3PAR-Fix-umanaged-volumes-snapshots-missing.patch
 <==
Bug-Ubuntu: http://bugs.launchpad.net/bugs/1994521
Origin: https://review.opendev.org/c/openstack/cinder/+/907257

==> 
debian/patches/lp1994521-0002-3PAR-Error-out-if-vol-cannot-be-converted-to-base.patch
 <==
Bug-Ubuntu: http://bugs.launchpad.net/bugs/1994521
Origin: https://review.opendev.org/c/openstack/cinder/+/907258


** Description changed:

  [Impact]
  
  The customer faced issue when they are using nova with 3par storage.
  they can't delete volume if there is children and it is attached to vm.
  
  it makes sense they can't delete it as the children has attachment but
  nova should expose proper error when trying deletion.
  
  [Test Case]
- Haven't tested this as there is no test 3par storage.
+ 
+ The customer has the required hardware for testing this.
+ 
  Volume->Snapshot->Volume2
  Volume2 is attached to some VM.
  and can't delete Volume without proper error msg.
  
  [Where problems could occur]
  This is related to hpe3par storage.
  snapshot handling could be issue with this patch.
  deleting volume could be issue with this patch.
  
  [Others]
  
  Original Desc
  
  When we try to delete a snapshot, we flatten it's dependent volumes by 
copying them to a new volume and deleting the original one.
  We fail to copy the volume when it has children and it is not handled in the 
code.
  
  : hpe3parclient.exceptions.HTTPConflict: Conflict (HTTP 409) 32 - volume
  has a child

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

Title:
  HPE3PAR: Failing to clone a volume having children

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1994521/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1987663] Re: cinder-volume: "Failed to re-export volume, setting to ERROR" with "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected" on service startup

[Mauricio Faria de Oliveira]

The packages built successfully in Test PPA ppa:mfo/cinder-
lp1987663-lp1988942-lp1994521

All build-time unit tests passed in the Test PPA (as in the Ubuntu
Archive).

Mantic:
---

mantic-updates:


BUILDLOG='https://launchpad.net/ubuntu/+source/cinder/2:23.0.0-0ubuntu1.1/+build/27741243/+files/buildlog_ubuntu-mantic-amd64.cinder_2%3A23.0.0-0ubuntu1.1_BUILDING.txt.gz'
curl -sL "$BUILDLOG" -o - | gzip -dc | grep -e '^Ran .* tests' -e '^OK 
(skipped='

Ran 17293 tests in 343.725s
OK (skipped=44)

mantic test ppa:


BUILDLOG='https://launchpadlibrarian.net/725471761/buildlog_ubuntu-mantic-amd64.cinder_2%3A23.0.0-0ubuntu1.2_BUILDING.txt.gz'
curl -sL "$BUILDLOG" -o - | gzip -dc | grep -e '^Ran .* tests' -e '^OK 
(skipped='

Ran 17293 tests in 333.393s
OK (skipped=44)

Jammy:
---

jammy-updates:


BUILDLOG='https://launchpad.net/ubuntu/+source/cinder/2:20.3.1-0ubuntu1.1/+build/27741270/+files/buildlog_ubuntu-jammy-amd64.cinder_2%3A20.3.1-0ubuntu1.1_BUILDING.txt.gz'
curl -sL "$BUILDLOG" -o - | gzip -dc | grep -e '^Ran .* tests' -e '^OK 
(skipped='

Ran 16048 tests in 367.044s
OK (skipped=48)

jammy test ppa:


BUILDLOG='https://launchpad.net/~mfo/+archive/ubuntu/cinder-lp1987663-lp1988942-lp1994521/+build/28125465/+files/buildlog_ubuntu-jammy-amd64.cinder_2%3A20.3.1-0ubuntu1.2_BUILDING.txt.gz'
curl -sL "$BUILDLOG" -o - | gzip -dc | grep -e '^Ran .* tests' -e '^OK 
(skipped='

Ran 16054 tests in 343.184s
OK (skipped=48)

Focal:
---

focal-updates:


BUILDLOG='https://launchpadlibrarian.net/666807464/buildlog_ubuntu-focal-amd64.cinder_2%3A16.4.2-0ubuntu2.4_BUILDING.txt.gz'
curl -sL "$BUILDLOG" -o - | gzip -dc | sed -n -e '/^Ran:/,/^Sum of/p'

Ran: 12772 tests in 205.1574 sec.
 - Passed: 12760
 - Skipped: 12
 - Expected Fail: 0
 - Unexpected Success: 0
 - Failed: 0
Sum of execute time for each test: 802.0120 sec.

focal test ppa:


BUILDLOG='https://launchpad.net/~mfo/+archive/ubuntu/cinder-lp1987663-lp1988942-lp1994521/+build/28125762/+files/buildlog_ubuntu-focal-amd64.cinder_2%3A16.4.2-0ubuntu2.5_BUILDING.txt.gz'
curl -sL "$BUILDLOG" -o - | gzip -dc | sed -n -e '/^Ran:/,/^Sum of/p'

Ran: 12772 tests in 228.6830 sec.
 - Passed: 12760
 - Skipped: 12
 - Expected Fail: 0
 - Unexpected Success: 0
 - Failed: 0
Sum of execute time for each test: 866.5233 sec.

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

Title:
  cinder-volume: "Failed to re-export volume, setting to ERROR" with
  "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint
  is not connected" on service startup

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1988942] Re: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)

[Mauricio Faria de Oliveira]

** Changed in: cloud-archive/zed
   Status: In Progress => Won't Fix

** Changed in: cloud-archive/zed
 Assignee: Jorge Merlino (jorge-merlino) => (unassigned)

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

Title:
  Failed to set image property. Invalid input for field/attribute
  simplestreams_metadata. Value: ... is too long (HTTP 400)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1988942/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1987663] Re: cinder-volume: "Failed to re-export volume, setting to ERROR" with "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected" on service startup

[Mauricio Faria de Oliveira]

** Changed in: cloud-archive/wallaby
   Status: New => Won't Fix

** Changed in: cloud-archive/ussuri
   Status: New => Incomplete

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

Title:
  cinder-volume: "Failed to re-export volume, setting to ERROR" with
  "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint
  is not connected" on service startup

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

[Mauricio Faria de Oliveira]

SRU team: this is on hold to double check the library symbols (thanks,
Robie!), please do not accept yet.

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

Title:
  libvirt domain is not listed/managed after libvirt restart with
  messages "internal error: no monitor path" and "Failed to load config
  for domain"

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1987663] Re: cinder-volume: "Failed to re-export volume, setting to ERROR" with "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected" on service startup

[Mauricio Faria de Oliveira]

Re: comment #13, I had re-tested Mantic, Jammy, and Focal with/without
the patch (they all work/fail as expected), but forgot to update the
bug.

** Changed in: cinder (Ubuntu Lunar)
   Importance: Medium => Undecided

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

Title:
  cinder-volume: "Failed to re-export volume, setting to ERROR" with
  "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint
  is not connected" on service startup

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1994521] Re: HPE3PAR: Failing to clone a volume having children

[Mauricio Faria de Oliveira]

Hey Seyeong, Dariusz,

Thanks for the clarifications!

Yes, this needs coordination with the Openstack Engineering team
not only for the other changes they plan to combine in an upload,
but also regarding the upstream acceptance situation for this in
the different branches.

Apparently, they still haven't confirmed that, so I have reached
out to James (as I'm involved in one of the three bugs) to offer
help and ask the question whether they are OK with these changes.

Thanks!

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

Title:
  HPE3PAR: Failing to clone a volume having children

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1994521/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

[Mauricio Faria de Oliveira]

Hi Sergio,

Thanks for taking the time to read and review the patch and test cases!

> this new code path could be reached even after the initialization,
couldn't it?

No, this code path should only be reached during initialization, AFAICT.

That is because qemuProcessReconnect() can only be reached from function
calls in the initialization path when the daemon initializes the drivers.

For reference, this is the only call path reaching qemuProcessReconnect().
(I've started with it, and gone back into callers.)

@ src/remote/remote_daemon.c
- main()
- daemonStateInit()
- daemonRunStateInit()
@ src/libvirt.c
- virStateInitialize()
- virStateDriverTab[i]->stateInitialize()
@ src/qemu/qemu_driver.c
- virStateDriver qemuStateDriver.stateInitialize = qemuStateInitialize
- qemuStateInitialize()
@ src/qemu/qemu_process.c
- qemuProcessReconnectAll()
- qemuProcessReconnectHelper()
- qemuProcessReconnect()

> Worst case scenario (i.e., if we fail to consider a code path), we will
> have a "memory leak" during shutdown, which is not the end of the world.

Right, that's comforting. :)

And just to clarify on the code path consideration (so as to provide more
reassurance for the patch, regarding a code path possibly not considered):

There should be only one code path leading to qemuProcessReconnect() (above),
and fortunately the points to inc/dec references are straightforward there:

The thread is created (1) either successfully or fails (2), and has a single
return point (3).

So, if the reference count is incremented right before thread creation (1), 
there is only 2 code sites to decrement it: on thread creation failure (2)
(since the function doesn't run, its return point "dec" doesn't run either),
and thread creation success: the function runs, so "dec" in return point (3).

> Otherwise, the patch LGTM and I'm satisfied with the testing you did.
> Feel free to go ahead and upload it.

Ok, cool. I think the clarifications above should address the two points
you brought up, so I'll continue and rebase and upload it.

Thanks again!

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

Title:
  libvirt domain is not listed/managed after libvirt restart with
  messages "internal error: no monitor path" and "Failed to load config
  for domain"

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976312] Please test proposed package

[Mauricio Faria de Oliveira]

Hello thom, or anyone else affected,

Accepted pathological into jammy-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/pathological/1.1.3-16ubuntu0.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [SRU] Pathological wont accept any input

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976312] Re: [SRU] Pathological wont accept any input

[Mauricio Faria de Oliveira]

Hi Sudip, Dave (uploader),

Thanks for the patch for Ubuntu!

These changes do not modify the DEP3 headers of the existing
python3.patch file.

For SRUs, it's good practice to add 'Bug-Ubuntu:' / 'Origin:' tags, and in the
case the .patch file already exists, a 'Last-Update:' tag too would be helpful.

The fact that Debian applied the change this way doesn't mean derivatives have
to apply it the same way; so, in the future, I'd suggest that the Ubuntu patch
should be added/updated the DEP3 tags for the incremental changes.

It's not a big deal for this package/frequency of maintenance; this one
is OK.

Thanks again!

** Changed in: pathological (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  [SRU] Pathological wont accept any input

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976312] Re: [SRU] Pathological wont accept any input

[Mauricio Faria de Oliveira]

** Description changed:

  [ Impact ]
  
  pathological is completely unusable as none of the keyboard or mouse
  input will work. And the game can not be played if the user can not
  control the game.
  
  [ Test Plan ]
  
  1. Install pathologial
  2. Use up-down keys to check if different options can be selected
  3. start the game
  4. Use mouse left and right buttons to control
  5. Play the game
  
  If the package is not fixed, then it will fail in Step 2.
  
  [ Where problems could occur ]
  
  There is not much change in the code, its only fixing the Python3 syntax
- and using '==' instead of 'is'. The change has been in Mantic and Debian
- and there has been no reported regression due to this change. And, so I
- am not expecting any regression for Jammy also. The game is already not
- playable, there can not be a worse regression than this.
+ and using '==' instead of 'is'. The change has been in Lunar/Mantic and
+ Debian and there has been no reported regression due to this change.
+ And, so I am not expecting any regression for Jammy also. The game is
+ already not playable, there can not be a worse regression than this.
  
  [ Other Info ]
  
  The same fix from Debian is in Mantic.
  
  Focal has the same package version but the game can be played.
  
  [ Original Bug Description ]
  
  cat /etc/lsb-release:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=22.04
  DISTRIB_CODENAME=jammy
  DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS"
  
  apt policy pathological:
  pathological:
    Geïnstalleerd: 1.1.3-16
    Kandidaat: 1.1.3-16
    Versietabel:
   *** 1.1.3-16 500
  500 http://nl.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  500 http://nl.archive.ubuntu.com/ubuntu jammy/universe i386 Packages
  100 /var/lib/dpkg/status
  
  Pathological 1.1.3-16 accepts no input from keyboard or mouse anymore
  under ubuntu 22.04 LTS.
  
  The same pathological version (1.1.3-16) works without problem under ubuntu 
20.04 LTS
  (so it is probably library related)
  
  Steps to reproduce:
  Start pathological (by commandline or menuitem or starter)
  When titlescreen/openingsmenu appears, try to select any menuitem (can't be 
done)
  
  It may be important to know that pygame and probably some other libraries 
changed:
  20.04
   pygame 1.9.6
  
  22.04
   pygame 2.1.2 (SDL 2.0.20, Python 3.10.4)

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

Title:
  [SRU] Pathological wont accept any input

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1936449] Please test proposed package

[Mauricio Faria de Oliveira]

Hello DarkTrick, or anyone else affected,

Accepted numptyphysics into focal-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/numptyphysics/0.2+svn157-0.4ubuntu0.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [SRU] numptyphysics segfault on startup on XUb 21.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1936449] Re: [SRU] numptyphysics segfault on startup on XUb 21.04

[Mauricio Faria de Oliveira]

Notes:

- Version with the patch [0] (0.2+svn157-0.5) was introduced in Ubuntu on 
Impish [1]
(older than Jammy in the SRU template, so updated the SRU template to increase
version range it has been applied in Ubuntu).

- The DEP-3 field 'Origin:' has an invalid optional prefix 'Debian';
it should be 'vendor' per DEP-3 guidelines [2] in this case, 
but let's not require another upload just because of this.

Please just note that in future uploads :) Thanks for using DEP-3 tags!

Thanks!

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986692
[1] https://launchpad.net/ubuntu/+source/numptyphysics/+publishinghistory
[2] https://dep-team.pages.debian.net/deps/dep3/

The field can be optionaly prefixed with a single keyword followed by a
comma and a space to categorize the origin. The allowed keywords are
"upstream" (in the case of a patch cherry-picked from the upstream VCS),
"backport" (in the case of an upstream patch that had to be modified to
apply on the current version), "vendor" for a patch created by Debian or
another distribution vendor, or "other" for all other kind of patches.

** Changed in: numptyphysics (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  [SRU] numptyphysics segfault on startup on XUb 21.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1936449] Re: [SRU] numptyphysics segfault on startup on XUb 21.04

[Mauricio Faria de Oliveira]

** Description changed:

  [ Impact ]
  
  numptyphysics is completely unusable as it will segfault immediately on
  start.
  
  [ Test Plan ]
  
  1. Install numptyphysics
  2. Start numptyphysics
  3. Play the game to check it works
  
  If the package is not fixed then it will fail to start.
-  
  
  [ Where problems could occur ]
  
  This is changing the code and is now returning valid values from non-
  void functions, so the runtime behaviour of the application will change.
  So, there might be a little chance that the some of the return values
  are not as expected. But, currently the application does not even start,
  and any regression due to this change can not be more than that.
  
  [ Other Info ]
  
- This change is from Debian and is part of Ubuntu from Jammy onwards.
+ This change is from Debian and is part of Ubuntu from Impish onwards.
  There has been no reported regression.
- 
  
  [ Original Bug Description ]
  
  Reproduce
  =
  - `sudo apt install numptyphysics`
  - `numptyphysics`
  - Actual: segfault
  
  Nothing more to explain here...
  
  numptyphysics:
    Installed: 0.2+svn157-0.4build1
    Candidate: 0.2+svn157-0.4build1
    Version table:
   *** 0.2+svn157-0.4build1 500
  500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages
  100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: numptyphysics 0.2+svn157-0.4build1
  ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22
  Uname: Linux 5.11.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri Jul 16 11:23:30 2021
  SourcePackage: numptyphysics
  UpgradeStatus: Upgraded to hirsute on 2021-06-05 (40 days ago)

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

Title:
  [SRU] numptyphysics segfault on startup on XUb 21.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1994521] Re: HPE3PAR: Failing to clone a volume having children

[Mauricio Faria de Oliveira]

Seyeong, Dariusz (subscribing you as you're the uploader),

Could you please confirm whether the Openstack Engineering team
is OK with the proposed changes, and that they are not upstream?

From comment #12 it seems unclear whether the situation could
move forward, and the SRU template was updated in case it was;
but there is no other comment indicating how things turned out,
before the upload happened.

Thanks!

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

Title:
  HPE3PAR: Failing to clone a volume having children

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1994521/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970521] Please test proposed package

[Mauricio Faria de Oliveira]

Hello Graham, or anyone else affected,

Accepted boinc into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/boinc/7.18.1+dfsg-4ubuntu0.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [SRU] boinc-client crashes when started with core dump on Xubuntu
  22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970521] Re: [SRU] boinc-client crashes when started with core dump on Xubuntu 22.04

[Mauricio Faria de Oliveira]

Looked at potential performance regressions of removing AVX instructions.
(Updated the SRU template sections accordingly.)

The boinc packages do not provide high-performance code, it's the boinc
_applications_ written to be run by the client and linked against the 
library for API access that have the high-performance code, IIUIC.

The API documentation/headers do not seem to provide any high-performance
functions (e.g., the crypto part are wrapper for openssl), the only code
it seems to implement is MD5.

https://github.com/BOINC/boinc/wiki/ProjectMain#developing-boinc-
applications

Considering this change has been introduced in Debian ~2 years ago
(Feb-Jun 2022) and in Ubuntu Kinetic (22.10) and is still in place,
there indeed does not seem to be a performance regression (or other
issues related to it).

```
boinc (7.20.0+dfsg-1) unstable; urgency=medium

  [ Steffen Moeller ]
  * Reverse AVX instructions for better compatibility with older servers
```

https://launchpad.net/ubuntu/kinetic/+source/boinc

** Changed in: boinc (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  [SRU] boinc-client crashes when started with core dump on Xubuntu
  22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970521] Re: [SRU] boinc-client crashes when started with core dump on Xubuntu 22.04

[Mauricio Faria de Oliveira]

** Description changed:

  [ Impact ]
  
  boinc-client is completely unusable on older CPU which does not have avx like 
a Celeron CPU.
  It will crash immediately if run on old CPU, but will run without any problem 
on newer CPUs.
  
  [ Test Plan ]
  
  It should be done on both types of CPUs, one which has AVX, and one which 
does not have AVX.
  If using qemu then "-cpu Conroe-v1" will emulate Celeron CPU without AVX.
  
  Confirm with the command "lscpu" and check the flags if "avx" is listed
  or not.
  
  Commands to execute for testing on both CPUs:
  
  1. Install boinc
  2. Execute "boinc" from a terminal
  
  If the package is not fixed then it will fail to start.
  
  [ Where problems could occur ]
  
  There is no change in the code and is only modifying debian/rules so
  that the built binary does not have any machine instruction for AVX. It
  will result in a different executable machine code but chances of
  regression due to this is very low.
  
+ There does not seem to be performance-critical code in the boinc client
+ or boinc library (which is the API provided for the boinc _applications_,
+ which are performance-critical path; the API is not a high-performance lib).
+ 
+ Thus, removing AVX from the package, even for the API, would not seem to
+ cause a performance regression for working/avx-capable processor models.
+ 
  [ Other Info ]
  
- This change is from Debian and is part of Ubuntu from Manctic onwards. There 
has been no reported regression due to this change.
+ This change is from Debian and is part of Ubuntu from Kinetic onwards. There 
has been no reported regression due to this change.
  The Debian change is at: 
https://salsa.debian.org/pkg-boinc-team/boinc/-/commit/a0611c2bc86864428337b07b382e4d5cf823b95d
  
  [ Original Bug Description ]
  
  lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04
  
  apt-cache policy boinc-client
  boinc-client:
    Installed: 7.18.1+dfsg-4
    Candidate: 7.18.1+dfsg-4
    Version table:
   *** 7.18.1+dfsg-4 500
  500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status
  
  I expected boinc-client to start; it crashed immediately with a core
  dump.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: boinc-client 7.18.1+dfsg-4
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 27 15:04:19 2022
  InstallationDate: Installed on 2019-12-24 (854 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: boinc
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (3 days ago)

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

Title:
  [SRU] boinc-client crashes when started with core dump on Xubuntu
  22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970521] Re: [SRU] boinc-client crashes when started with core dump on Xubuntu 22.04

[Mauricio Faria de Oliveira]

Marked bug 1988863 as a duplicate.

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

Title:
  [SRU] boinc-client crashes when started with core dump on Xubuntu
  22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1988863] Re: boinc package uses avx instructions unconditionally

[Mauricio Faria de Oliveira]

*** This bug is a duplicate of bug 1970521 ***
https://bugs.launchpad.net/bugs/1970521

** This bug has been marked a duplicate of bug 1970521
   [SRU] boinc-client crashes when started with core dump on Xubuntu 22.04

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

Title:
  boinc package uses avx instructions unconditionally

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892558] Please test proposed package

[Mauricio Faria de Oliveira]

Hello Nathaniel, or anyone else affected,

Accepted macutils into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/macutils/2.0b3-16ubuntu0.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [SRU] binhex always segfaults

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892558] Re: [SRU] binhex always segfaults

[Mauricio Faria de Oliveira]

$ lsb_release -cs; dpkg -s macutils | grep ^Version:; dpkg -L macutils | grep 
/bin/ | while read BIN; do echo $BIN; $BIN -H >/dev/null 2>&1; echo RC = $?; 
done
focal
Version: 2.0b3-16build1
/usr/bin/binhex
RC = 139
/usr/bin/frommac
RC = 139
/usr/bin/hexbin
RC = 0
/usr/bin/macsave
RC = 0
/usr/bin/macstream
RC = 0
/usr/bin/macunpack
RC = 0
/usr/bin/tomac
RC = 139
ubuntu@focal:~$

$ lsb_release -cs; dpkg -s macutils | grep ^Version:; dpkg -L macutils | grep 
/bin/ | while read BIN; do echo $BIN; $BIN -H >/dev/null 2>&1; echo RC = $?; 
done
jammy
Version: 2.0b3-17
/usr/bin/binhex
RC = 0
/usr/bin/frommac
RC = 0
/usr/bin/hexbin
RC = 0
/usr/bin/macsave
RC = 0
/usr/bin/macstream
RC = 0
/usr/bin/macunpack
RC = 0
/usr/bin/tomac
RC = 0

$ lsb_release -cs; dpkg -s macutils | grep ^Version:; dpkg -L macutils | grep 
/bin/ | while read BIN; do echo $BIN; $BIN -H >/dev/null 2>&1; echo RC = $?; 
done
No LSB modules are available.
mantic
Version: 2.0b3-17
/usr/bin/binhex
RC = 0
/usr/bin/frommac
RC = 0
/usr/bin/hexbin
RC = 0
/usr/bin/macsave
RC = 0
/usr/bin/macstream
RC = 0
/usr/bin/macunpack
RC = 0
/usr/bin/tomac
RC = 0

$ lsb_release -cs; dpkg -s macutils | grep ^Version:; dpkg -L macutils | grep 
/bin/ | while read BIN; do echo $BIN; $BIN -H >/dev/null 2>&1; echo RC = $?; 
done
No LSB modules are available.
noble
Version: 2.0b3-17
/usr/bin/binhex
RC = 0
/usr/bin/frommac
RC = 0
/usr/bin/hexbin
RC = 0
/usr/bin/macsave
RC = 0
/usr/bin/macstream
RC = 0
/usr/bin/macunpack
RC = 0
/usr/bin/tomac
RC = 0

** Changed in: macutils (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  [SRU] binhex always segfaults

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892558] Re: [SRU] binhex always segfaults

[Mauricio Faria de Oliveira]

Hi Sudip,

Thanks for debugging, backporting, and submitting a patch!
Nice touch on the DEP-3 headers.

Just a style/cosmetic _suggestion_ that is helpful: in the
future, please list the .patch file in d/changelog; e.g.,
'* d/p/fix-segfault.patch: Fix segfault with binhex, frommac and tomac. (LP: 
#1892558)'

And just for documentation purposes:
> There is no change in code, only the relevant header file has been included.
> And, so there are minimum chances of a regression.

The inclusion of a header file even 'without code changes'
may actually cause code changes _indirectly_. For example,
a header file defines a macro that is checked in the source
file (to change code paths) with a preprocessor #if/#ifdef.

This is _not_ the case here, as the included headers only
define the function prototypes, and nothing else/no macro;
so it looks good!

I also confirmed that the newer releases have the change
and are not affected.

Accepting macutils to focal-proposed.
Thanks again!

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

Title:
  [SRU] binhex always segfaults

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

[Mauricio Faria de Oliveira]

Steps with test packages on Focal (shutdown-on-runtime)
---

Stop libvirtd systemd units

 sudo systemctl stop 'libvirtd*'

Start libvirt in GDB

  sudo gdb \
-iex 'set confirm off' \
-iex 'set pagination off' \
-ex 'set non-stop on' \
-ex 'handle SIGTERM nostop noprint pass' \
-ex 'add-symbol-file /usr/sbin/libvirtd' \
-ex 'add-symbol-file /usr/lib/x86_64-linux-gnu/libvirt.so.0' \
-ex 'add-symbol-file /usr/lib/x86_64-linux-gnu/libvirt-qemu.so.0' \
-ex 'add-symbol-file 
/usr/lib/x86_64-linux-gnu/libvirt/connection-driver/libvirt_driver_qemu.so' \
/usr/sbin/libvirtd

Add breakpoints for qemu driver cleanup and device deleted event

 b qemuStateCleanup
 b processDeviceDeletedEvent
 run

Start test VM with an USB mouse device

  cat <<-EOF >test-vm.xml
  
test-vm

  hvm

32
1

  

  
EOF

 virsh define test-vm.xml
 virsh start test-vm

 $ virsh list
 Id Name State
 -
 1 test-vm running

Delete the USB mouse device

 DEVICE_ID=$(virsh qemu-monitor-command test-vm --hmp 'info qtree' | 
grep 'dev: usb-mouse' | cut -d'"' -f2)
 virsh qemu-monitor-command test-vm --hmp "device_del $DEVICE_ID"

Back to GDB

 Thread 20 "libvirtd" hit Breakpoint 2, 0x7ffba902204e in
processDeviceDeletedEvent (devAlias=, vm=0x7ffbac00de90,
driver=0x7ffbac021380) at ../../../src/qemu/qemu_driver.c:4888

Add breakpoint to domain status XML save, and continue the thread above

 b virDomainObjSave
 t 20
 c

Thread 20 "libvirtd" hit Breakpoint 3, virDomainObjSave
(obj=0x7ffbac00de90, xmlopt=0x7ffbac044130, statusDir=0x7ffbac01f530
"/run/libvirt/qemu") at ../../../src/conf/domain_conf.c:29157

Check the backtrace of the domain status XML save function, coming from
device deleted event

 (gdb) bt
#0  virDomainObjSave (obj=0x7ffbac00de90, xmlopt=0x7ffbac044130, 
statusDir=0x7ffbac01f530 "/run/libvirt/qemu") at 
../../../src/conf/domain_conf.c:29157
#1  0x7ffba9022127 in processDeviceDeletedEvent 
(devAlias=0x556074b5e3f0 "input0", vm=0x7ffbac00de90, driver=0x7ffbac021380) at 
../../../src/qemu/qemu_driver.c:4312
#2  qemuProcessEventHandler (data=0x556074b63a10, 
opaque=0x7ffbac021380) at ../../../src/qemu/qemu_driver.c:4888
#3  0x7ffbbee8f1af in virThreadPoolWorker 
(opaque=opaque@entry=0x556074c047a0) at ../../../src/util/virthreadpool.c:163
#4  0x7ffbbee8e51c in virThreadHelper (data=) at 
../../../src/util/virthread.c:196
#5  0x7ffbbeb4f609 in start_thread (arg=) at 
pthread_create.c:477
#6  0x7ffbbea74353 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Leave the thread at this point

Let's trigger the shutdown path

 $ sudo kill $(pidof libvirtd)

Thread 1 "libvirtd" hit Breakpoint 1, qemuStateCleanup () at
../../../src/qemu/qemu_driver.c:1127

Check the function pointer is non-NULL _before_ cleanup

(gdb) p xmlopt.privateData.format
$1 = (virDomainXMLPrivateDataFormatFunc) 0x7ffba8f7c7c0 


(gdb) p/x xmlopt.parent
$2 = {u = {dummy_align1 = 0x1cafe0027, dummy_align2 = 0x1cafe0027, s = 
{magic = 0xcafe0027, refs = 0x1}}, klass = 0x7ffbac044100}

Let cleanup run:

t 1
c &

Check the formatter/options again; it is *STILL* referenced, not 0x0
anymore:

(gdb) p xmlopt.privateData.format
$3 = (virDomainXMLPrivateDataFormatFunc) 0x7ffba8f7c7c0 


(gdb) p/x xmlopt.parent
$4 = {u = {dummy_align1 = 0x1cafe0027, dummy_align2 = 0x1cafe0027, s = 
{magic = 0xcafe0027, refs = 0x1}}, klass = 0x7ffbac044100}

Check the shutdown/cleanup thread is waiting for it,
in the path to free the worker thread pool:

(gdb) i th 1
  Id   Target Id   Frame
  1Thread 0x7ffbbb035b40 (LWP 5887) "libvirtd" (running)
(gdb) t 1
(gdb) interrupt
(gdb) bt
#0  futex_wait_cancelable (private=, expected=0, 
futex_word=0x7ffbac05fd60) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, 
mutex=0x7ffbac05fce0, cond=0x7ffbac05fd38) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x7ffbac05fd38, mutex=0x7ffbac05fce0) at 
pthread_cond_wait.c:647
#3  0x7ffbbee8e79b in virCondWait (c=, m=) at ../../../src/util/virthread.c:144
#4  0x7ffbbee8f438 in virThreadPoolFree (pool=) at 
../../../src/util/virthreadpool.c:286
#5  0x7ffba8fed5d1 in qemuStateCleanup () at 
../../../src/qemu/qemu_driver.c:1131
#6  0x7ffbbf02c47f in virStateCleanup () at 
../../../src/libvirt.c:669
#7  0x556072acebc8 in main (argc=, argv=) at