from:"Christian Ehrhardt "

** Changed in: highway (Ubuntu)
 Assignee: (unassigned) => Lukas Märdian (slyon)

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

Title:
  [MIR] highway

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


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

[Bug 2073269] [NEW] [MIR] libconvert-base32-perl and libcrypt-urandom-perl

Public bug reported:

https://ubuntu-archive-team.ubuntu.com/component-mismatches-proposed.svg
shows freeradius depending on libconvert-base32-perl and libcrypt-urandom-perl 
now


Evaluate the new freeradius please if we want to file MIRs for them OR if we 
want to modify the dependencies.

** Affects: freeradius (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: libconvert-base32-perl (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: libcrypt-urandom-perl (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: oracular

** Also affects: libcrypt-urandom-perl (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Changed in: libcrypt-urandom-perl (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  [MIR] libconvert-base32-perl and libcrypt-urandom-perl

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


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

[Bug 2069324] Re: vsftpd hangs with SIGCHLD when pam_exec.so is used

** Description changed:

[ Impact ]

- * when running sub-processes on login through pam_exec a process
+ * User impact: under certain conditions using pam_exec the vsftp server
+just hangs
+
+ * Reason: when running sub-processes on login through pam_exec a process
is spawned. That can confuse vsftp if that child ends triggering SIGCHLD
but
already been picked up by e.g. pam_exec.so itself.

- * The fix uses waitpid over wait to be able to pass options. With that
+ * Fix: The fix uses waitpid over wait to be able to pass options. With that
it sets WNOHANG in vsf_sysutil_wait except if it is explicitly called
-to wait as done in common_do_login for the pre-login child.
+ to wait as done in common_do_login for the pre-login child.
Therefore these other calls now allow it to "return immediately if
-no child has exited" as defined for WNOHANG in [1]
+ no child has exited" as defined for WNOHANG in [1]

[1]: https://manpages.ubuntu.com/manpages/noble/en/man2/wait.2.html

[ Test Plan ]

# install
$ apt install lftp vsftpd
# change config
$ sed -i.old '1 i\account optional pam_exec.so debug quiet /root/foo.sh\'
/etc/pam.d/vsftpd
# script to run
$ cat > /root/foo.sh << EOF
#!/bin/bash
/bin/true
touch /tmp/brooks-was-here
/bin/true
EOF
$ chmod +x /root/foo.sh
# enable ssl
$ sed -i -s -e 's/ssl_enable=NO/ssl_enable=YES/' /etc/vsftpd.conf
$ systemctl restart vsftpd.service
# Place a file there
$ echo foobar > /home/ubuntu/egal
# set test PW to ubuntu user
echo 'ubuntu:ubuntu' | chpasswd

# Using it with ftps (and ignore cert verification as it is the snakeoil
cert)

To verify the test config, if you run this in a second console you should see
it calling the script as yo uact on the server.
$ tail -f /var/log/auth.log
...
2024-07-16T07:30:37.966553+00:00 o vsftpd: pam_exec(vsftpd:account): Calling
/root/foo.sh ...

Good case (Noble / Oracular):

root@n:~# lftp 127.0.0.1
lftp 127.0.0.1:~> set ftp:ssl-force true
lftp 127.0.0.1:~> set ssl:verify-certificate false
lftp 127.0.0.1:~> login ubuntu ubuntu
lftp ubuntu@127.0.0.1:~> dir
-rw-r--r-- 1 0 0 7 Jul 16 07:30 egal
lftp ubuntu@127.0.0.1:~> get egal
7 bytes transferred
lftp ubuntu@127.0.0.1:~>
exit
root@n:~# cat egal
foobar

Bad case (Focal and Jammy)
root@j:~# lftp 127.0.0.1
lftp 127.0.0.1:~> set ftp:ssl-force true
lftp 127.0.0.1:~> set ssl:verify-certificate false
lftp 127.0.0.1:~> login ubuntu ubuntu
lftp ubuntu@127.0.0.1:~> dir
`ls' at 0 [Sending commands...]

[ Where problems could occur ]

* This changes signal handling for SIGCHLD.
The code now returns cleanly if there was nobody to wait for, which formerly
would have caused a the main process to die "Child died, so we'll do the
same"
That is intentionally changed for the condition of the child already being
consumed.
If there is a use case of the child leaving which was meant to terminate
(unlikely, this is an unclean die call) it might no more happen now.

[ Other Info ]

* The code is the same (only no change rebuilds) still, this does not occur in
Noble and Oracular. At least not with the current test setup. That is
slightly
disturbing.
Also in the reproduction we've seen that it only occurred with FTPS, but
that
is not conceptually tied to the problem, it might only be yet another detail
that changes the timing and size of the signal race window.
Of course we can assume that it is just a race and the window is
different there, but then should we not fix it? Or we can assume something
else e.g. pam_exec has changed behavior to mask the issue and hence no
vsftpd
change is needed there. I think it is wasted to research this for ages, but
it leaves some uncertainty.

---

When you try to run a script with pam_exec.so on login vsftpd freezes
with SIGCHLD.

This was fixed in 2015 by redhat and never adopted to Debian/Ubunutu.

See also:
- https://bugzilla.redhat.com/show_bug.cgi?id=1198259
-
https://git.centos.org/rpms/vsftpd/blob/54ac5fac29fcc1bb68f2e96e63ecfda655286ff8/f/SOURCES/0026-Prevent-hanging-in-SIGCHLD-handler.patch

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

Title:
vsftpd hangs with SIGCHLD when pam_exec.so is used

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

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

[Bug 2069324] Re: vsftpd hangs with SIGCHLD when pam_exec.so is used

** Description changed:

  [ Impact ]
  
-  * when running sub-processes on login through pam_exec a process
-is spawned. That can confuse vsftp if that child ends triggering SIGCHLD 
but 
-already been picke dup by e.g. pam_exec.so itself.
+  * when running sub-processes on login through pam_exec a process
+    is spawned. That can confuse vsftp if that child ends triggering SIGCHLD 
but
+    already been picked up by e.g. pam_exec.so itself.
  
-  * The fix uses waitpid over wait to be able to pass options. With that
-it sets WNOHANG when calling vsf_sysutil_wait is called from 
common_do_login 
-(as there pam_exec would run if configured). That allows it to
-"return immediately if no child has exited" [1]
+  * The fix uses waitpid over wait to be able to pass options. With that
+    it sets WNOHANG in vsf_sysutil_wait except if it is explicitly called
+to wait as done in common_do_login for the pre-login child.
+    Therefore these other calls now allow it to "return immediately if
+no child has exited" as defined for WNOHANG in [1]
  
  [1]: https://manpages.ubuntu.com/manpages/noble/en/man2/wait.2.html
  
  [ Test Plan ]
  
  # install
  $ apt install lftp vsftpd
  # change config
  $ sed -i.old '1 i\account optional pam_exec.so debug quiet /root/foo.sh\' 
/etc/pam.d/vsftpd
  # script to run
  $ cat > /root/foo.sh << EOF
  #!/bin/bash
  /bin/true
  touch /tmp/brooks-was-here
  /bin/true
  EOF
  $ chmod +x /root/foo.sh
  # enable ssl
  $ sed -i -s -e 's/ssl_enable=NO/ssl_enable=YES/' /etc/vsftpd.conf
  $ systemctl restart vsftpd.service
  # Place a file there
  $ echo foobar > /home/ubuntu/egal
  # set test PW to ubuntu user
  echo 'ubuntu:ubuntu' | chpasswd
  
  # Using it with ftps (and ignore cert verification as it is the snakeoil
  cert)
  
  To verify the test config, if you run this in a second console you should see 
it calling the script as yo uact on the server.
  $ tail -f /var/log/auth.log
  ...
  2024-07-16T07:30:37.966553+00:00 o vsftpd: pam_exec(vsftpd:account): Calling 
/root/foo.sh ...
  
  Good case (Noble / Oracular):
  
  root@n:~# lftp 127.0.0.1
  lftp 127.0.0.1:~> set ftp:ssl-force true
  lftp 127.0.0.1:~> set ssl:verify-certificate false
  lftp 127.0.0.1:~> login ubuntu ubuntu
  lftp ubuntu@127.0.0.1:~> dir
  -rw-r--r-- 1 0 0 7 Jul 16 07:30 egal
  lftp ubuntu@127.0.0.1:~> get egal
  7 bytes transferred
  lftp ubuntu@127.0.0.1:~>
  exit
  root@n:~# cat egal
  foobar
  
  Bad case (Focal and Jammy)
  root@j:~# lftp 127.0.0.1
  lftp 127.0.0.1:~> set ftp:ssl-force true
  lftp 127.0.0.1:~> set ssl:verify-certificate false
  lftp 127.0.0.1:~> login ubuntu ubuntu
  lftp ubuntu@127.0.0.1:~> dir
  `ls' at 0 [Sending commands...]
  
  [ Where problems could occur ]
  
  * This changes signal handling for SIGCHLD.
-   The code now returns cleanly if there was nobody to wait for, which formerly
-   would have caused a the main process to die "Child died, so we'll do the 
same"
-   That is intentionally changed for the condition of the child already being 
-   consumed.
-   If there is a use case of the child leaving which was meant to terminate
-   (unlikely, this is an unclean die call) it might no more happen now.
+   The code now returns cleanly if there was nobody to wait for, which formerly
+   would have caused a the main process to die "Child died, so we'll do the 
same"
+   That is intentionally changed for the condition of the child already being
+   consumed.
+   If there is a use case of the child leaving which was meant to terminate
+   (unlikely, this is an unclean die call) it might no more happen now.
  
  [ Other Info ]
  
- * The code is the same (only no change rebuilds) still, this does not occur 
in 
-   Noble and Oracular. At least not with the current test setup. That is 
slightly
-   disturbing.
-   Also in the reproduction we've seen that it only occurred with FTPS, but 
that 
-   is not conceptually tied to the problem, it might only be yet another detail
-   that changes the timing and size of the signal race window.
-   Of course we can assume that it is just a race and the window is 
-   different there, but then should we not fix it? Or we can assume something 
-   else e.g. pam_exec has changed behavior to mask the issue and hence no 
vsftpd 
-   change is needed there. I think it is wasted to  research this for ages, 
but 
-   it leaves some uncertainty.
- 
+ * The code is the same (only no change rebuilds) still, this does not occur in
+   Noble and Oracular. At least not with the current test setup. That is 
slightly
+   disturbing.
+   Also in the reproduction we've seen that it only occurred with FTPS, but 
that
+   is not conceptually tied to the problem, it might only be yet another detail
+   that changes the timing and size of the signal race window.
+   Of course we can assume that it is just a race and the window is
+   different there, but then should we not fix it? Or we can assume something
+   else e.g. pam_exec has

[Bug 2069324] Re: vsftpd hangs with SIGCHLD when pam_exec.so is used

** Description changed:

+ [ Impact ]
+ 
+  * when running sub-processes on login through pam_exec a process
+is spawned. That can confuse vsftp if that child ends triggering SIGCHLD 
but 
+already been picke dup by e.g. pam_exec.so itself.
+ 
+  * The fix uses waitpid over wait to be able to pass options. With that
+it sets WNOHANG when calling vsf_sysutil_wait is called from 
common_do_login 
+(as there pam_exec would run if configured). That allows it to
+"return immediately if no child has exited" [1]
+ 
+ [1]: https://manpages.ubuntu.com/manpages/noble/en/man2/wait.2.html
+ 
+ [ Test Plan ]
+ 
+ # install
+ $ apt install lftp vsftpd
+ # change config
+ $ sed -i.old '1 i\account optional pam_exec.so debug quiet /root/foo.sh\' 
/etc/pam.d/vsftpd
+ # script to run
+ $ cat > /root/foo.sh << EOF
+ #!/bin/bash
+ /bin/true
+ touch /tmp/brooks-was-here
+ /bin/true
+ EOF
+ $ chmod +x /root/foo.sh
+ # enable ssl
+ $ sed -i -s -e 's/ssl_enable=NO/ssl_enable=YES/' /etc/vsftpd.conf
+ $ systemctl restart vsftpd.service
+ # Place a file there
+ $ echo foobar > /home/ubuntu/egal
+ # set test PW to ubuntu user
+ echo 'ubuntu:ubuntu' | chpasswd
+ 
+ # Using it with ftps (and ignore cert verification as it is the snakeoil
+ cert)
+ 
+ To verify the test config, if you run this in a second console you should see 
it calling the script as yo uact on the server.
+ $ tail -f /var/log/auth.log
+ ...
+ 2024-07-16T07:30:37.966553+00:00 o vsftpd: pam_exec(vsftpd:account): Calling 
/root/foo.sh ...
+ 
+ Good case (Noble / Oracular):
+ 
+ root@n:~# lftp 127.0.0.1
+ lftp 127.0.0.1:~> set ftp:ssl-force true
+ lftp 127.0.0.1:~> set ssl:verify-certificate false
+ lftp 127.0.0.1:~> login ubuntu ubuntu
+ lftp ubuntu@127.0.0.1:~> dir
+ -rw-r--r-- 1 0 0 7 Jul 16 07:30 egal
+ lftp ubuntu@127.0.0.1:~> get egal
+ 7 bytes transferred
+ lftp ubuntu@127.0.0.1:~>
+ exit
+ root@n:~# cat egal
+ foobar
+ 
+ Bad case (Focal and Jammy)
+ root@j:~# lftp 127.0.0.1
+ lftp 127.0.0.1:~> set ftp:ssl-force true
+ lftp 127.0.0.1:~> set ssl:verify-certificate false
+ lftp 127.0.0.1:~> login ubuntu ubuntu
+ lftp ubuntu@127.0.0.1:~> dir
+ `ls' at 0 [Sending commands...]
+ 
+ [ Where problems could occur ]
+ 
+ * This changes signal handling for SIGCHLD.
+   The code now returns cleanly if there was nobody to wait for, which formerly
+   would have caused a the main process to die "Child died, so we'll do the 
same"
+   That is intentionally changed for the condition of the child already being 
+   consumed.
+   If there is a use case of the child leaving which was meant to terminate
+   (unlikely, this is an unclean die call) it might no more happen now.
+ 
+ [ Other Info ]
+ 
+ * The code is the same (only no change rebuilds) still, this does not occur 
in 
+   Noble and Oracular. At least not with the current test setup. That is 
slightly
+   disturbing.
+   Also in the reproduction we've seen that it only occurred with FTPS, but 
that 
+   is not conceptually tied to the problem, it might only be yet another detail
+   that changes the timing and size of the signal race window.
+   Of course we can assume that it is just a race and the window is 
+   different there, but then should we not fix it? Or we can assume something 
+   else e.g. pam_exec has changed behavior to mask the issue and hence no 
vsftpd 
+   change is needed there. I think it is wasted to  research this for ages, 
but 
+   it leaves some uncertainty.
+ 
+ 
+ ---
+ 
  When you try to run a script with pam_exec.so on login vsftpd freezes
  with SIGCHLD.
  
  This was fixed in 2015 by redhat and never adopted to Debian/Ubunutu.
  
  See also:
  - https://bugzilla.redhat.com/show_bug.cgi?id=1198259
  - 
https://git.centos.org/rpms/vsftpd/blob/54ac5fac29fcc1bb68f2e96e63ecfda655286ff8/f/SOURCES/0026-Prevent-hanging-in-SIGCHLD-handler.patch

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

Title:
  vsftpd hangs with SIGCHLD when pam_exec.so is used

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


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

[Bug 2073214] Re: hugepages causes permissions error

Hi Tim,
you are right that neither of the workaround steps were necessary on 22.04 and 
they should neither be on 24.04.


### Topic 1 - changes that should not be needed

Ubuntu 24.04 by default has

1. hugetlbfs mounted (was that no more the case for you after upgrade?)
$ mount | grep huge
hugetlbfs on /dev/hugepages type hugetlbfs 
(rw,nosuid,nodev,relatime,pagesize=2M)

2. uncommenting hugetlbfs_mount in /etc/libvirt/qemu.conf changes nothing
default is
#hugetlbfs_mount = "/dev/hugepages"
Changing that to
hugetlbfs_mount = "/dev/hugepages"
will not change anything.

I assume #1 and #2 have only been things on your try to debug what is wrong - 
which is fine.
But let us know if it is otherwise.

### Topic 2 - was there an apparmor denial?

Now back to your actual issue, you mentioned that you set apparmor to complain 
mode.
Was there an indication that apparmor is the issue, a related denial in the 
syslog when you start your guest? If so could you please pass that denial?

### Topic 3 - repro seems to not trigger this

I picked a guest which before had:
  1024  
 
  1024

And changed it to use huge pages by adding:
 
 
 
 
  
 

 
  

To confirm it tries to use the right thing I started it without allocating huge 
pages and got:
=> qemu-system-x86_64: unable to map backing store for guest RAM: Cannot 
allocate memory

Then I allocated some huge pages in the system and started it again.
$ echo 512 | sudo tee -a /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
$ virsh start --console test

Worked right away.

I double checked in /proc/meminfo and saw HugePages_Free changing when the 
guest was running.
So I think, something is configured in an unexpected way.

Could you share
- your full guest-config in regard to memory
- hugeadm --list-all-mounts
- journalctl -f while starting the guest
- grep -i huge /proc/meminfo

** Changed in: libvirt (Ubuntu)
   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/2073214

Title:
  hugepages causes permissions error

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


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

[Bug 2069324] Re: vsftpd hangs with SIGCHLD when pam_exec.so is used

I was double checking this on other releases and got the hang on focal.
I could indeed only trigger this with FTPS on focal, but AFAICS the same config 
as on Oracular.
That motivated me, so I tried fresh F,J,N,O systems which in theory should all 
be the same but obviously behave different.

And I found it is not affecting Noble and higher.
That is weird in itself, as there the only difference is that they got two no 
change rebuilds (for a CVE and for libssl3t64)

I was updating the steps to recreate as I used them for this.
For >=Noble this either really is no issue due to yet unknown reasons, or on 
>Noble we need adapted test steps that would trigger it there.

# install
$ apt install lftp vsftpd
# change config
$ sed -i.old '1 i\account optionalpam_exec.so debug quiet 
/root/foo.sh\' /etc/pam.d/vsftpd
# script to run
$ cat > /root/foo.sh << EOF
#!/bin/bash
/bin/true
touch /tmp/brooks-was-here
/bin/true
EOF
$ chmod +x /root/foo.sh
# enable ssl
$ sed -i -s -e 's/ssl_enable=NO/ssl_enable=YES/' /etc/vsftpd.conf
$ systemctl restart vsftpd.service
# Place a file there
$ echo foobar > /home/ubuntu/egal
# set test PW to ubuntu user
echo 'ubuntu:ubuntu' | chpasswd

# Using it with ftps (and ignore cert verification as it is the snakeoil
cert)

To verify the test config, if you run this in a second console you should see 
it calling the script as yo uact on the server.
$ tail -f /var/log/auth.log
...
2024-07-16T07:30:37.966553+00:00 o vsftpd: pam_exec(vsftpd:account): Calling 
/root/foo.sh ...


Good case (Noble / Oracular):

root@n:~# lftp 127.0.0.1
lftp 127.0.0.1:~> set ftp:ssl-force true
lftp 127.0.0.1:~> set ssl:verify-certificate false
lftp 127.0.0.1:~> login ubuntu ubuntu
lftp ubuntu@127.0.0.1:~> dir
-rw-r--r--1 00   7 Jul 16 07:30 egal
lftp ubuntu@127.0.0.1:~> get egal
7 bytes transferred
lftp ubuntu@127.0.0.1:~> 
exit
root@n:~# cat egal 
foobar

Bad case (Focal and Jammy)
root@j:~# lftp 127.0.0.1
lftp 127.0.0.1:~> set ftp:ssl-force true
lftp 127.0.0.1:~> set ssl:verify-certificate false
lftp 127.0.0.1:~> login ubuntu ubuntu
lftp ubuntu@127.0.0.1:~> dir
`ls' at 0 [Sending commands...]

^^ here it hangs

** Also affects: vsftpd (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: vsftpd (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Also affects: vsftpd (Ubuntu Oracular)
   Importance: Undecided
   Status: Incomplete

** Changed in: vsftpd (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: vsftpd (Ubuntu Jammy)
   Status: New => Confirmed

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

Title:
  vsftpd hangs with SIGCHLD when pam_exec.so is used

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


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

[Bug 2060649] Re: python-wcmatch not compatible to python3.12

Thank you for cross checking again Daniel and Adric.
Given all your support in verifying I think we are all good now.

This will stay the mandatory aging period in -proposed and then should
be good to be released fixing this for everyone.

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

Title:
  python-wcmatch not compatible to python3.12

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


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

[Bug 2069324] Re: vsftpd hangs with SIGCHLD when pam_exec.so is used

Thanks Markus

#1 trying with this now:

account optionalpam_exec.so debug quiet /root/foo.sh


And
$ cat /root/foo.sh
#!/bin/bash
/bin/true
touch /tmp/brooks-was-here
/bin/true


By default vsftp is configured for the snakeoil certificate to get started 
easily, but with ssl disabled. So enable it and restart.

$ sed -i -s -e 's/ssl_enable=NO/ssl_enable=YES/' /etc/vsftpd.conf
$ sudo systemctl restart vsftpd.service


# Using it with ftps (and ignore cert verification as it is the snakeoil cert)

root@o:~# lftp 127.0.0.1
lftp 127.0.0.1:~> set ftp:ssl-force true
lftp 127.0.0.1:~> set ssl:verify-certificate false
lftp 127.0.0.1:~> login ubuntu ubuntu
lftp ubuntu@127.0.0.1:~> dir
-rw-r--r--1 00   7 Jul 12 06:59 egal
lftp ubuntu@127.0.0.1:~> get egal
7 bytes transferred
lftp ubuntu@127.0.0.1:~> 
exit
root@o:~# cat egal 
foobar
root@o:~# ll /tmp/brooks-was-here
-rw--- 1 root root 0 Jul 15 12:04 /tmp/brooks-was-here
root@o:~# date
Mon Jul 15 12:04:32 UTC 2024

I checked ftps was enabled e.g. a dir without it was not working:
  530 Non-anonymous sessions must use encryption.

Sadly that means it still works fine.
We still need more from you about what is needed to trigger this hang :-/

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

Title:
  vsftpd hangs with SIGCHLD when pam_exec.so is used

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


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

[Bug 2060649] Re: python-wcmatch not compatible to python3.12

Upgrade

root@n:~/python-wcmatch# apt install python3-wcmatch -t noble-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libaio1 libsoup2.4-1 libsoup2.4-common libvpx8 python3-boto
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
  python3-wcmatch
1 upgraded, 0 newly installed, 0 to remove and 57 not upgraded.
Need to get 32.8 kB of archives.
After this operation, 1024 B disk space will be freed.
Get:1 http://archive.ubuntu.com/ubuntu noble-proposed/universe amd64 
python3-wcmatch all 8.4-2ubuntu0.1 [32.8 kB]
Fetched 32.8 kB in 0s (87.1 kB/s)  
(Reading database ... 134318 files and directories currently installed.)
Preparing to unpack .../python3-wcmatch_8.4-2ubuntu0.1_all.deb ...
Unpacking python3-wcmatch (8.4-2ubuntu0.1) over (8.4-2) ...
Setting up python3-wcmatch (8.4-2ubuntu0.1) ...
Scanning processes...   

   
Scanning candidates...  

   

Restarting services...
 systemctl restart wsdd-server.service

Service restarts being deferred:
 /etc/needrestart/restart.d/dbus.service
 systemctl restart networkd-dispatcher.service
 systemctl restart systemd-logind.service
 systemctl restart unattended-upgrades.service

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this
host.





root@n:~/python-wcmatch# ansible-lint test.yaml
WARNING  Listing 2 violation(s) that are fatal
fqcn[action-core]: Use FQCN for builtin module actions (apt).
test.yaml:4 Use `ansible.builtin.apt` or `ansible.legacy.apt` instead.

yaml[truthy]: Truthy value should be one of [false, true]
test.yaml:8

Read documentation for instructions on how to ignore specific rule
violations.

 Rule Violation Summary  
 count tag   profilerule associated tags 
 1 yaml[truthy]  basic  formatting, yaml 
 1 fqcn[action-core] production formatting   

Failed: 2 failure(s), 0 warning(s) on 1 files. Last profile that met the
validation criteria was 'min'.






root@n:~/python-wcmatch# ansible-lint test2.yaml

Passed: 0 failure(s), 0 warning(s) on 1 files. Last profile that met the
validation criteria was 'production'.





root@n:~/test# apt source python-wcmatch
Reading package lists... Done
NOTICE: 'python-wcmatch' packaging is maintained in the 'Git' version control 
system at:
https://salsa.debian.org/python-team/packages/python-wcmatch.git
Please use:
git clone https://salsa.debian.org/python-team/packages/python-wcmatch.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 123 kB of source archives.
Get:1 http://archive.ubuntu.com/ubuntu noble-proposed/universe python-wcmatch 
8.4-2ubuntu0.1 (dsc) [2273 B]
Get:2 http://archive.ubuntu.com/ubuntu noble-proposed/universe python-wcmatch 
8.4-2ubuntu0.1 (tar) [117 kB]
Get:3 http://archive.ubuntu.com/ubuntu noble-proposed/universe python-wcmatch 
8.4-2ubuntu0.1 (diff) [4296 B]
Fetched 123 kB in 1s (167 kB/s) 
dpkg-source: info: extracting python-wcmatch in python-wcmatch-8.4
dpkg-source: info: unpacking python-wcmatch_8.4.orig.tar.gz
dpkg-source: info: unpacking python-wcmatch_8.4-2ubuntu0.1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying lp-2060649-support-Python-3.12.patch
W: Download is performed unsandboxed as root as file 
'python-wcmatch_8.4-2ubuntu0.1.dsc' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)
root@n:~/test# cd python-wcmatch-8.4/
root@n:~/test/python-wcmatch-8.4# head debian/changelog 
python-wcmatch (8.4-2ubuntu0.1) noble; urgency=medium

  * d/p/lp-2060649-support-Python-3.12.patch: compatibility with python 3.12
(LP: #2060649)

 -- Christian Ehrhardt   Thu, 11 Jul
2024 11:51:29 +0200

python-wcmatch (8.4-2) unstable; urgency=medium

  [ Debian Janitor ]
root@n:~/test/python-wcmatch-8.4# pytest
=
 test session starts 
=
platform linux -- Python 3.12.3, pytest-7.4.4, pluggy-1.4.0
rootdir: /root/test/python-wcmatch-8.4
configfile: tox.ini
collected 1315 items

  

tests/test_fnmatch.py

[Bug 2060649] Re: python-wcmatch not compatible to python3.12

** Changed in: python-wcmatch (Ubuntu Mantic)
   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/2060649

Title:
  python-wcmatch not compatible to python3.12

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


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

[Bug 2060649] Re: python-wcmatch not compatible to python3.12

Done: Description updated and fix uploaded

** Description changed:

  [ Impact ]
  
   * The code in wcmatch uses inner details of libraries hidden in python 3.12
   * That breaks several use cases like ansible-lint and many self tests
  
  [racb] ansible-lint doesn't work at all. Calling it with no arguments,
  calling it with --help, and calling it with --version all fail with the
  same stack trace.
  
  [ Test Plan ]
  
  1. For the original report, run ansible-lint
+- without arguments you expect it to fail to load any file (that is ok, a 
total breakage failing to load wcmatch is not)
+ 
+- with --help you want to see the help to be shown
+ 
+- One can run ansible yaml file, with ansible-lint , here are
+ two one can use for that
+ 
+ a) With mistakes (1x fqcn[action-core] 1x yaml[truthy])
+ Result is
+ ...
+ fqcn[action-core]: Use FQCN for builtin module actions (apt).
+ yaml[truthy]: Truthy value should be one of [false, true]
+ ...
+ 
+ $ cat test.yaml
+ - name: Install apache2
+   hosts: servers
+   tasks:
+ - name: Ensure apache2 is installed
+   apt:
+ name: apache2
+ state: present
+   become: yes
+ 
+ b) A file that makes lint happy, result is
+ Passed: 0 failure(s), 0 warning(s) on 1 files. Last profile that met the 
validation criteria was 'production'.
+ 
+ $ cat test2.yaml
+ - name: Install apache2
+   hosts: servers
+   tasks:
+ - name: Ensure apache2 is installed
+   ansible.builtin.apt:
+ name: apache2
+ state: present
+   become: true
+ 
  
  2. For a wider coverage I recommend running the full self-tests
  
  $ apt install dpkg-dev
  # add deb-src to entries in /etc/apt/sources.list.d/ubuntu.sources
  $ apt update
  $ apt source python-wcmatch
  $ cd python-wcmatch-8.*
  $ pytestdetailed instructions how to reproduce the bug
  
  [ Where problems could occur ]
  
   * wcmatch has multiple subelements, only pathlib use cases got changed
   * There are untested changes to the windows code paths, but even WSL will run
     the linux paths, so that should be a no-op
  
  [ Other Info ]
  
   * while in universe, this is just an easy fix and an oversight in
     the python transition hence I think we should fix it
  
  ---
  original report
  
  Running ansible-lint in Ubuntu 24.04 on my role ends up with a stack
  trace:
  
  Traceback (most recent call last):
    File "/usr/bin/ansible-lint", line 5, in 
  from ansiblelint.__main__ import _run_cli_entrypoint
    File "/usr/lib/python3/dist-packages/ansiblelint/__main__.py", line 39, in 

  from ansiblelint import cli
    File "/usr/lib/python3/dist-packages/ansiblelint/cli.py", line 20, in 

  from ansiblelint.file_utils import (
    File "/usr/lib/python3/dist-packages/ansiblelint/file_utils.py", line 15, 
in 
  import wcmatch.pathlib
    File "/usr/lib/python3/dist-packages/wcmatch/pathlib.py", line 218, in 

  class PurePosixPath(PurePath):
    File "/usr/lib/python3/dist-packages/wcmatch/pathlib.py", line 221, in 
PurePosixPath
  _flavour = pathlib._posix_flavour  # type: ignore[attr-defined]
     ^^
  AttributeError: module 'pathlib' has no attribute '_posix_flavour'
  
  This is due to python3-wcmatch=8.4-2 being incompatible with python3.12.
  Upstream fixed this in the next version
  https://github.com/facelessuser/wcmatch/releases/tag/8.5
  
  I think the following portion of changes can be added to library package for 
Noble release:
  
https://github.com/facelessuser/wcmatch/pull/203/files#diff-081b2096c270ab6b17a6c70f95ea07d24dd0d343522e135dbdeb609e59867186L83
  
  Versions of installed packages:
  
  ansible-lint:
    Installed: 6.17.2-1
    Candidate: 6.17.2-1
    Version table:
   *** 6.17.2-1 500
  500 http://ru.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
  500 http://ru.archive.ubuntu.com/ubuntu noble/universe i386 Packages
  100 /var/lib/dpkg/status
  
  python3-wcmatch:
    Installed: 8.4-2
    Candidate: 8.4-2
    Version table:
   *** 8.4-2 500
  500 http://ru.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
  500 http://ru.archive.ubuntu.com/ubuntu noble/universe i386 Packages
  100 /var/lib/dpkg/status

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

Title:
  python-wcmatch not compatible to python3.12

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


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

[Bug 2060649] Re: python-wcmatch not compatible to python3.12

Thank you Adric and Daniel.
I'll upload this to Noble unapproved where it should hopefully be quickly 
accepted given the great pre-checks. I'll use your hints to extend on the test 
steps in the description ...

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

Title:
  python-wcmatch not compatible to python3.12

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


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

[Bug 2069324] Re: vsftpd hangs with SIGCHLD when pam_exec.so is used

2024-07-12 Thread Christian Ehrhardt 

Hi,
first of all thanks for all the prep work.
The patch LGTM and I agree we should add it.
I was happy to see the suggestions on how to reproduce, but while writing it 
out in more detail could not reproduce the hang. The following are the steps I 
drafted to an SRU templates "how to test and verify" steps. But the hang does 
not occur. Could you have a look where my steps diverge from what you had in 
mind?


# Install ftp server
$ sudo apt install vsftpd

# set a user with password, I use ubuntu:ubuntu in the examples here
$ passwd ubuntu

# add testfile to the users home dir
$ echo foobar > /home/ubuntu/egal

# Check with FTP if the normal setup works
root@o:~# ftp 127.0.0.1
Connected to 127.0.0.1.
220 (vsFTPd 3.0.5)
Name (127.0.0.1:root): ubuntu
331 Please specify the password.
Password: 
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> dir
229 Entering Extended Passive Mode (|||47570|)
150 Here comes the directory listing.
-rw-r--r--1 00   7 Jul 12 06:59 egal
226 Directory send OK.
ftp> get egal
local: egal remote: egal
229 Entering Extended Passive Mode (|||21047|)
150 Opening BINARY mode data connection for egal (7 bytes).
100% 
|**|
 7   45.87 KiB/s00:00 ETA
226 Transfer complete.
7 bytes received in 00:00 (8.49 KiB/s)
ftp> ^D
221 Goodbye.
root@o:~# cat egal
foobar
root@o:~# rm egal


# Now set up the failure condition
#1 add a few exec commands on pam
$ echo "account optionalpam_exec.so debug quiet /bin/true" | sudo 
tee -a /etc/pam.d/vsftpd

# Restart server to be sure to pick up everything
$ sudo systemctl restart vsftpd.service

# Log in again to see the hang
$ ftp 127.0.0.1

^^ but this does not fall into the hang, I can get the file and quit
normally.

It is not that the setup is totally useless, in /var/log/auth.log I see on the 
login
2024-07-12T07:27:01.030634+00:00 o vsftpd: pam_exec(vsftpd:account): Calling 
/bin/true ...


Do you have an advice what you do different to reproduce the issue?


P.S. along evaluating this I found many more changes we should apply to our ftp 
servers. Not all suitable for SRUs, but going forward I want to still improve 
them. To find the required time for that effort I internally filed SD-1755 to 
not fall through the cracks forever.

** Changed in: vsftpd (Ubuntu)
   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/2069324

Title:
  vsftpd hangs with SIGCHLD when pam_exec.so is used

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


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

[Bug 2060649] Re: python-wcmatch not compatible to python3.12

** Changed in: python-wcmatch (Ubuntu Noble)
   Status: Triaged => 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/2060649

Title:
  python-wcmatch not compatible to python3.12

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


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

[Bug 2060649] Re: python-wcmatch not compatible to python3.12

** Description changed:

+ [ Impact ]
+ 
+  * The code in wcmatch uses inner details of libraries hidden in python 3.12
+  * That breaks several use cases like ansible-lint and many self tests
+ 
+ [ Test Plan ]
+ 
+ 1. For the original report, run ansible-lint
+ 
+ 2. For a wider coverage I recommend running the full self-tests
+ 
+ $ apt install dpkg-dev
+ # add deb-src to entries in /etc/apt/sources.list.d/ubuntu.sources
+ $ apt update
+ $ apt source python-wcmatch
+ $ cd python-wcmatch-8.*
+ $ pytestdetailed instructions how to reproduce the bug
+ 
+ 
+ [ Where problems could occur ]
+ 
+  * wcmatch has multiple subelements, only pathlib use cases got changed
+  * There are untested changes to the windows code paths, but even WSL will 
run 
+the linux paths, so that should be a no-op
+ 
+ [ Other Info ]
+  
+  * while in universe, this is just an easy fix and an oversight in
+the python transition hence I think we should fix it
+ 
+ ---
+ original report
+ 
  Running ansible-lint in Ubuntu 24.04 on my role ends up with a stack
  trace:
  
  Traceback (most recent call last):
-   File "/usr/bin/ansible-lint", line 5, in 
- from ansiblelint.__main__ import _run_cli_entrypoint
-   File "/usr/lib/python3/dist-packages/ansiblelint/__main__.py", line 39, in 

- from ansiblelint import cli
-   File "/usr/lib/python3/dist-packages/ansiblelint/cli.py", line 20, in 

- from ansiblelint.file_utils import (
-   File "/usr/lib/python3/dist-packages/ansiblelint/file_utils.py", line 15, 
in 
- import wcmatch.pathlib
-   File "/usr/lib/python3/dist-packages/wcmatch/pathlib.py", line 218, in 

- class PurePosixPath(PurePath):
-   File "/usr/lib/python3/dist-packages/wcmatch/pathlib.py", line 221, in 
PurePosixPath
- _flavour = pathlib._posix_flavour  # type: ignore[attr-defined]
-^^
+   File "/usr/bin/ansible-lint", line 5, in 
+ from ansiblelint.__main__ import _run_cli_entrypoint
+   File "/usr/lib/python3/dist-packages/ansiblelint/__main__.py", line 39, in 

+ from ansiblelint import cli
+   File "/usr/lib/python3/dist-packages/ansiblelint/cli.py", line 20, in 

+ from ansiblelint.file_utils import (
+   File "/usr/lib/python3/dist-packages/ansiblelint/file_utils.py", line 15, 
in 
+ import wcmatch.pathlib
+   File "/usr/lib/python3/dist-packages/wcmatch/pathlib.py", line 218, in 

+ class PurePosixPath(PurePath):
+   File "/usr/lib/python3/dist-packages/wcmatch/pathlib.py", line 221, in 
PurePosixPath
+ _flavour = pathlib._posix_flavour  # type: ignore[attr-defined]
+    ^^
  AttributeError: module 'pathlib' has no attribute '_posix_flavour'
  
  This is due to python3-wcmatch=8.4-2 being incompatible with python3.12.
  Upstream fixed this in the next version
  https://github.com/facelessuser/wcmatch/releases/tag/8.5
  
  I think the following portion of changes can be added to library package for 
Noble release:
  
https://github.com/facelessuser/wcmatch/pull/203/files#diff-081b2096c270ab6b17a6c70f95ea07d24dd0d343522e135dbdeb609e59867186L83
  
  Versions of installed packages:
  
  ansible-lint:
-   Installed: 6.17.2-1
-   Candidate: 6.17.2-1
-   Version table:
-  *** 6.17.2-1 500
- 500 http://ru.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
- 500 http://ru.archive.ubuntu.com/ubuntu noble/universe i386 Packages
- 100 /var/lib/dpkg/status
+   Installed: 6.17.2-1
+   Candidate: 6.17.2-1
+   Version table:
+  *** 6.17.2-1 500
+ 500 http://ru.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
+ 500 http://ru.archive.ubuntu.com/ubuntu noble/universe i386 Packages
+ 100 /var/lib/dpkg/status
  
  python3-wcmatch:
-   Installed: 8.4-2
-   Candidate: 8.4-2
-   Version table:
-  *** 8.4-2 500
- 500 http://ru.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
- 500 http://ru.archive.ubuntu.com/ubuntu noble/universe i386 Packages
- 100 /var/lib/dpkg/status
+   Installed: 8.4-2
+   Candidate: 8.4-2
+   Version table:
+  *** 8.4-2 500
+ 500 http://ru.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
+ 500 http://ru.archive.ubuntu.com/ubuntu noble/universe i386 Packages
+ 100 /var/lib/dpkg/status

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

Title:
  python-wcmatch not compatible to python3.12

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


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

[Bug 2060649] Re: ansible-lint crashes in 24.04

MR: 
https://code.launchpad.net/~paelzer/ubuntu/+source/python-wcmatch/+git/python-wcmatch/+merge/469193
PPA: 
https://launchpad.net/~paelzer/+archive/ubuntu/lp-2060649-support-python-312

** Summary changed:

- ansible-lint crashes in 24.04
+ python-wcmatch not compatible to python3.12

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

Title:
  python-wcmatch not compatible to python3.12

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


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

[Bug 2060649] Re: ansible-lint crashes in 24.04

As reported this was just the pre python 3.12 version and not rebuilt since
April 2023.
Thereby I agree to Sorin's suggestion of this not being ansible related at all.

Running the packages self-tests would have been enough to spot this in
the first place,.

But this only had autodep8-python3 defined for autopkgtests.
Which oddly only ran ran import wcmatch; print(wcmatch)
And those are too trivial, they worked.
Due to that there was no signal of that fail when python3.12 migrated.
See
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/p/python-wcmatch/20240303_232528_d4ebb@/log.gz

One should mid term try to look at ensuring the real testsuite runs at
autopkgtest time to avoid that from happening again (which it likely
will given that the project explicitly enables new versions). There is
already https://github.com/facelessuser/wcmatch/commit/09675ed9

But at least thereby manual testing this can be outlined well for the
SRU at hand here:

$ apt install dpkg-dev
# add deb-src to entries in /etc/apt/sources.list.d/ubuntu.sources
$ apt update
$ apt source python-wcmatch
$ cd python-wcmatch-8.*
$ pytest

With that we also see that the helpful suggestion of a more minimal change in
comment #6 will only lead to overcome this but fail in 57 other cases (down
from 2 during collection and not even starting in depth).

According to git there was no later change to the python 3.12 compat
changes in 223f9cab "Update to support Python 3.12 alpha (#203)". So a
subset (no git workflow, no tox, no metadata) seems to be the best
tradeoff for an SRU.

Noble with fix:
1165 passed, 150 skipped in 2.55s
Compared to Oracular (full 8.5.x)
1171 passed, 151 skipped, 54 warnings in 2.71s

I've done the backport for some minimal fuzz and a lot of
release/workflow changes that are only noise in regard to the SRU.
Applying that right to the source makes it work through all tests in
noble.

Preparing a MP, the SRU template and PPA with that ...

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

Title:
python-wcmatch not compatible to python3.12

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

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

[Bug 2060649] Re: ansible-lint crashes in 24.04

** Tags added: server-todo

** Also affects: python-wcmatch (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: python-wcmatch (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: python-wcmatch (Ubuntu Noble)
 Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

** Changed in: python-wcmatch (Ubuntu Noble)
   Status: New => Confirmed

** Changed in: python-wcmatch (Ubuntu Noble)
   Status: Confirmed => Triaged

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

Title:
  ansible-lint crashes in 24.04

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


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

[Bug 2060769] Re: pro-client execs `apt list --installed` instead of using python3-apt - leading to utf-8 errors

Out of a discussion with Renan.

On the system that worked, this triggers it again as it will run apt-
cache policy.

root@n:~# pro attach C1FTFZ9LbGLJWbJdbXhT9twkhymSQ
An unexpected error occurred: 'utf-8' codec can't decode byte 0xa0 in position
18: invalid start byte
For more details, see the log: /var/log/ubuntu-advantage.log
If you think this is a bug, please run: ubuntu-bug ubuntu-advantage-tools

root@n:~# pro detach
An unexpected error occurred: 'utf-8' codec can't decode byte 0xa0 in position
18: invalid start byte
For more details, see the log: /var/log/ubuntu-advantage.log
If you think this is a bug, please run: ubuntu-bug ubuntu-advantage-tools

The problem is that the problem that this was is fixed "apt list --installed".
But this turns out to now be other calls, in that case apt-cache policy.

root@n:~# apt-cache policy
Fichiers du paquet�:
100 /var/lib/dpkg/status
...

You see the bad char here.
So it is more that all kind of calls could return unparseable, based on the
language settings, and hit a bug quite similar to this.

So it seems:
- the original bug is actually fixed
- at least one more similar case is open still
- If we can we will try to ignore parsing errors kind of everywhere.
- If not, then this would need to become a new issue as it would need a bigger
fix.

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

Title:
pro-client execs `apt list --installed` instead of using python3-apt -
leading to utf-8 errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2060769/+subscriptions

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

[Bug 2060769] Re: pro-client execs `apt list --installed` instead of using python3-apt - leading to utf-8 errors

Interesting, the team will later have a deeper look.
But I'm confused as you can see in the following:

---

First confirming the original problem

root@n:~# locale
LANG=C.UTF-8
LANGUAGE=
LC_CTYPE="fr_FR"
LC_NUMERIC="fr_FR"
LC_TIME="fr_FR"
LC_COLLATE="fr_FR"
LC_MONETARY="fr_FR"
LC_MESSAGES="fr_FR"
LC_PAPER="fr_FR"
LC_NAME="fr_FR"
LC_ADDRESS="fr_FR"
LC_TELEPHONE="fr_FR"
LC_MEASUREMENT="fr_FR"
LC_IDENTIFICATION="fr_FR"
LC_ALL=fr_FR
root@n:~# pro status
An unexpected error occurred: 'utf-8' codec can't decode byte 0xe9 in position 
65: invalid continuation byte
For more details, see the log: /var/log/ubuntu-advantage.log
If you think this is a bug, please run: ubuntu-bug ubuntu-advantage-tools

---

Then I can sadly confirm that upgrading indeed is broken the same way
you mentioned.

root@n:~# apt install ubuntu-pro-client
Lecture des listes de paquets... Fait
Construction de l'arbre des d�pendances... Fait
Lecture des informations d'�tat... Fait
ubuntu-pro-client est d�j� la version la plus r�cente (32.3.1~24.04).
ubuntu-pro-client pass� en ��install� manuellement��.
Les paquets suivants ont �t� install�s automatiquement et ne sont plus 
n�cessaires�:
  libaio1 libsoup2.4-1 libsoup2.4-common libvpx8 python3-boto
Veuillez utiliser ��apt autoremove�� pour les supprimer.
0 mis � jour, 0 nouvellement install�s, 0 � enlever et 3 non mis � jour.
root@n:~# apt install ubuntu-pro-client -t noble/proposed
Lecture des listes de paquets... Fait
E: La valeur ��noble/proposed�� n'est pas valable pour APT::Default-Release car 
cette version ne fait pas partie des sources disponibles.
root@n:~# apt install ubuntu-pro-client=33~24.04 
Lecture des listes de paquets... Fait
Construction de l'arbre des d�pendances... Fait
Lecture des informations d'�tat... Fait
Les paquets suivants ont �t� install�s automatiquement et ne sont plus 
n�cessaires�:
  libaio1 libsoup2.4-1 libsoup2.4-common libvpx8 python3-boto
Veuillez utiliser ��apt autoremove�� pour les supprimer.
Paquets recommand�s�:
  ubuntu-pro-client-l10n
Les paquets suivants seront ENLEV�S�:
  ubuntu-pro-client-l10n
Les paquets suivants seront mis � jour�:
  ubuntu-pro-client
1 mis � jour, 0 nouvellement install�s, 1 � enlever et 3 non mis � jour.
Il est n�cessaire de prendre 231 ko dans les archives.
Apr�s cette op�ration, 81,9 ko d'espace disque seront lib�r�s.
Souhaitez-vous continuer�? [O/n] Y
R�ception de�:1 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 
ubuntu-pro-client amd64 33~24.04 [231 kB]
231 ko r�ceptionn�s en 0s (1�210 ko/s)
(Lecture de la base de donn�es... 110216 fichiers et r�pertoires d�j� 
install�s.)
Suppression de ubuntu-pro-client-l10n (32.3.1~24.04) ...
(Lecture de la base de donn�es... 110215 fichiers et r�pertoires d�j� 
install�s.)
Pr�paration du d�paquetage de .../ubuntu-pro-client_33~24.04_amd64.deb ...
Traceback (most recent call last):
  File "/usr/bin/py3clean", line 210, in 
main()
  File "/usr/bin/py3clean", line 196, in main
pfiles = set(dpf.from_package(options.package))
 ^^
  File "/usr/share/python3/debpython/files.py", line 54, in from_package
stdout = str(stdout, 'utf-8')
 
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 584: 
invalid continuation byte
dpkg: avertissement: le sous-processus ancien paquet ubuntu-pro-client script 
pre-removal a renvoy� un �tat de sortie d'erreur 1
dpkg: tentative d'ex�cution du script du nouveau paquet � la place...
Traceback (most recent call last):
  File "/usr/bin/py3clean", line 210, in 
main()
  File "/usr/bin/py3clean", line 196, in main
pfiles = set(dpf.from_package(options.package))
 ^^
  File "/usr/share/python3/debpython/files.py", line 54, in from_package
stdout = str(stdout, 'utf-8')
 
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 584: 
invalid continuation byte
dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/ubuntu-pro-client_33~24.04_amd64.deb (--unpack)�:
 le sous-processus nouveau ubuntu-pro-client paquet pre-removal script a 
renvoy� un �tat de sortie d'erreur 1
dmesg: read kernel buffer failed: Operation not permitted
 Traceback (most recent 
call last):
  File "/usr/bin/py3compile", line 323, in 
main()
  File "/usr/bin/py3compile", line 302, in main
compile(files, versions,
  File "/usr/bin/py3compile", line 185, in compile
for fn, versions_to_compile in filter_files(files, e_patterns, versions):
  File "/usr/bin/py3compile", line 128, in filter_files
for fpath in files:
  File "/usr/share/python3/debpython/files.py", line 71, in filter_public
for fn in files:
  File "/usr/share/python3/debpython/files.py", line 54, in from_package
stdout = str(stdout, 'utf-8')
 
UnicodeDecodeError: 'utf-8'

[Bug 1892456] Re: [MIR] malcontent

Hey,
I agree, this should be equally fine to be promoted on Noble as well.
None of the critical elements are different.

Please land the addition of a matching Extra-Exclude in the noble branch
of the seeds before doing so.

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

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

Title:
  [MIR] malcontent

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


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

[Bug 2071717] Re: [MIR] linuxptp

2024-07-04 Thread Christian Ehrhardt 

 authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)
- does not deal with cryptography (en-/decryption, certificates,
  signing, ...)

Problems:
- does run three daemons as root.
- does expose an external endpoint via ports.
- does parse data formats of the PTP messages which could be externally
  influenced.
- this does not make appropriate (for its exposure) use of established risk
  mitigation features (dropping permissions, using temporary environments,
  restricted users/groups, seccomp, systemd isolation features,
  apparmor, ...)

[Common blockers]
OK:
- does not FTBFS currently
- does have a non-trivial test suite that runs as autopkgtest
- This needs special HW for build or test so it can't be
  automatic at build or autopkgtest time. But as outlined
  by the requester in [Quality assurance - testing] there:
  - HW and test: via checkbox tests
  - simulation in autopkgtest via clknetsim
- no new python2 dependency

Problems:
- Does not have a test suite that runs at build time, but makes up for
  it in autopkgtest to some extent.

[Packaging red flags]
OK:
- Ubuntu does carry a delta, but it is reasonable and maintenance under
  control. It needs to be submitted though to not divereg too much making
  maintenance harder than it has to be as nothing we have is super-special.
  Mostly added QA which helps us as well if spotted earlier.
- symbols tracking not applicable for this kind of code.
- debian/watch is present and looks ok
- Upstream update history is good
- Debian/Ubuntu update history is ok
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- debian/rules is rather clean
- It is not on the lto-disabled list

Problems:
- the current release not is packaged, 4.2 needs to be merged

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
  tests)
- no use of user nobody
- no use of setuid / setgid
- no dependency on webkit, qtwebkit or libseed
- not part of the UI for extra checks
- no translation present, but none needed for this case (user visible)?

Problems:
- important open bugs (crashers, etc) in Debian or Ubuntu. In particular
  before we encourage wider adoption we should address
  - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004744
(partially fixed in Ubuntu with one of our deltas, the service
 dependency needs investigation)
  - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070847
Such cases are a constant source of pain, it should be tried to resolved
before it is a critical issue for someone

** Bug watch added: Debian Bug tracker #1004744
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004744

** Bug watch added: Debian Bug tracker #1070847
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070847

** Changed in: linuxptp (Ubuntu)
 Assignee: Christian Ehrhardt  (paelzer) => Ubuntu Security Team 
(ubuntu-security)

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

Title:
  [MIR] linuxptp

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


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

[Bug 2071717] Re: [MIR] linuxptp

2024-07-02 Thread Christian Ehrhardt 

** Changed in: linuxptp (Ubuntu)
 Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

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

Title:
  [MIR] linuxptp

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


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

[Bug 2070882] Re: [MIR] jpeg-xl

2024-07-02 Thread Christian Ehrhardt 

** Changed in: jpeg-xl (Ubuntu)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

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

Title:
  [MIR] jpeg-xl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jpeg-xl/+bug/2070882/+subscriptions


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

[Bug 2071396] Re: [MIR] libdisplay-info

2024-07-02 Thread Christian Ehrhardt 

** Changed in: libdisplay-info (Ubuntu)
 Assignee: (unassigned) => Lukas Märdian (slyon)

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

Title:
  [MIR] libdisplay-info

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdisplay-info/+bug/2071396/+subscriptions


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

[Bug 2064421] Re: Merge libslirp from Debian unstable for oracular

FYI - Uploaded to Oracular

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

Title:
  Merge libslirp from Debian unstable for oracular

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


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

[Bug 1911400] Re: autopkgtests broken in hirsute - error: int32 scalar cannot be indexed with .

Forgot to update this, it is a thing of the past nowadays

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

** Changed in: octave-parallel (Ubuntu)
   Status: New => Invalid

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

Title:
  autopkgtests broken in hirsute - error: int32 scalar cannot be indexed
  with .

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


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

[Bug 2064421] Re: Merge libslirp from Debian unstable for oracular

MP: 
https://code.launchpad.net/~paelzer/ubuntu/+source/libslirp/+git/libslirp/+merge/468319
PPA: 
https://launchpad.net/~paelzer/+archive/ubuntu/lp-2064421-merge-libslirp-4.8.0-1-oracular/+packages

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

Title:
  Merge libslirp from Debian unstable for oracular

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


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

[Bug 2064421] Re: Merge libslirp from Debian unstable for oracular

Merge Pre-Checks

There is some back and forth on the Debian side of 2029431 which is the only 
Delta we effectively have.
We didn't have any negative reports and since then others chimed in and wanted 
the same. I didn't dive much deeper but right now I see more arguments to keep 
the delta than to drop it.


- Debian changes
  - refer to close some bugs (no-op for us)
  - d/watch updates (fine)
  - standards bump (no-op)
  - copyright and metadata (no-op)
  - cross build fix (almost no effect for us)
  - no more disable tests from DEB_BUILD_OPTIONS (revert of the above)
=> none needs to be reverted, none conflicts with our Delta

- Upstream changes
  - https://gitlab.freedesktop.org/slirp/libslirp/-/releases/v4.8.0
  - fuzzing, haiku support, ...
  - Some new features for Network Controller Sideband Interface
  - fix use after free and last fragment access
=> none needs to be reverted, none conflicts with our Delta

ABI didn't change (not yet versioned anyway, still on soname 0), but
also no changes to libslirp0.symbols

LGTM, Merging 4.8.0-1 just rebasing what we have

** Changed in: libslirp (Ubuntu)
   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/2064421

Title:
  Merge libslirp from Debian unstable for oracular

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


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

[Bug 2064576] Re: Jammy to Noble upgrade lost private use area Ubuntu symbol

2024-06-25 Thread Christian Ehrhardt 

Hi, a month passed since the last update.

I wanted to ask if there has been any insight into why it happened and
how it will be fixed - or if and why this might become a Won't Fix?

I'm personally OK either way but would appreciate an update what we should 
expect on this case :-)
Thanks in advance!

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

Title:
  Jammy to Noble upgrade lost private use area Ubuntu symbol

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


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

[Bug 2070025] Re: [MIR] wsdd

2024-06-25 Thread Christian Ehrhardt 

y). That in contrast to the known security issues
  which state "designed for use in a trusted environment inside a firewall"
  which I think we can not guarantee implies that /usr/bin/wsdd should get
  a pretty strict apparmor profile. Its function should be fine with that
  and that could be our way to consider it "a trusted environment".

[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time (added in Oracular
  in 2:0.8-1ubuntu1)
  - test suite fails will fail the build upon error.
- This does not need special HW for build or test
- no new python2 dependency
- Python package, but using dh_python

Problems:
- Does not have a non-trivial test suite that runs as autopkgtest.
  That would not be an invalidation on its own, but also the build time
  regression tests are just two runs against two past mistakes, not a full
  feature check or anything close.

[Packaging red flags]
OK:
- Ubuntu does carry a delta, but it is reasonable and maintenance under
  control (adding testing)
- symbols tracking not applicable for this kind of code.
- Upstream update history is good (in bursts but ok)
- Debian/Ubuntu update history is good (following upstream)
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- debian/rules is rather clean
- It is not on the lto-disabled list

Problems:
- debian/watch is not present andbut also not needed (e.g. native)

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (python, no natice code)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
  tests)
- no use of setuid / setgid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit or libseed
- not part of the UI for extra checks (only nautilus itself later)

Problems: None

** Bug watch added: Debian Bug tracker #1073265
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073265

** Changed in: wsdd (Ubuntu)
 Assignee: Christian Ehrhardt  (paelzer) => Ubuntu Security Team 
(ubuntu-security)

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

Title:
  [MIR] wsdd

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


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

[Bug 2070025] Re: [MIR] wsdd

2024-06-24 Thread Christian Ehrhardt 

Trying to take a look at this to speed it up as requested...

** Changed in: wsdd (Ubuntu)
 Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

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

Title:
  [MIR] wsdd

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


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

[Bug 2065856] Re: SEGFAULTs in v4.3 with GlusterFS

I've dropped Ubuntu-sponsors to get off the lists people check.
Once the answers (or even better updated debdiffs) have been provided please 
add them back to pop up so someone can have a look again.

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

Title:
  SEGFAULTs in v4.3 with GlusterFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2065856/+subscriptions


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

[Bug 2065856] Re: SEGFAULTs in v4.3 with GlusterFS

State -> incomplete only as I wait for your answers - set it back to new
or confirmed once provided.

Thanks in advance!
Christian

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

Title:
  SEGFAULTs in v4.3 with GlusterFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2065856/+subscriptions


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

[Bug 2065856] Re: SEGFAULTs in v4.3 with GlusterFS

Patch review

First of all it is not as complex as it seems, it does the very same multiple 
times.
But I still found some things I need to ask.

Overall, once you had a look at those 4 points, addressed or explained
them the next sponsor coming by (or myself if I do not miss the ping due
to your reply) could sponsor that to Oracular and for the Noble SRU.


#1
I saw the context changed around
  PTHREAD_RWLOCK_destroy(_fd->fdlock);
which formerly was in many *_free_state functions in the version that is in 
noble.

That is part of the removing of all custom free functions used as function 
pointer in the ops struct.
What is left is that instead of through the function pointer like
  op_ctx->fsal_export->exp_ops.free_state(
it now calls directly
  free_state(pfid->state);
And in these calls the right state is selected that needs to be processed.

The new free_state now checks for bad  state.
Then only if a custom state free function is registered calls that or to 
gsh_free as final fallback.
Those are all set to NULL as seen in `grep -Hrn init_state src/* -A1`.
So gsh_free it is which is in src/include/abstract_mem.h 

But that is just:
254 static inline void  
 
255 gsh_free(void *p)   
 
256 {   
 
257 »···free(p);
 
258 }


Maybe I just do not see it yet, but could you explain why the proposed changes 
would not break the locking which seems to be no more done?
I'm sure the SRU team would want to know as well before accepting.



#2
Further there is a comment lost in the struct of *_state_fd
Upstream added:
  /** state MUST be first to use default free_state */
The comment is not functional and therefore not a huge problem.

But I also see no reason why it is not added, it would only apply other
backports harder right?

If there is a reason why that isn't added let explain it.
And if there is none the next revision could have that change to be more 
similar to the upstream patch right?


#3 the aforementioned versioning and changelog
I think this should be
3.1 oracular
nfs-ganesha (4.3-8ubuntu2) oracular; urgency=medium 
  

 
  * Fix null pointer ref in free_state (LP: #2065856)   
 
- d/p/20-fix-null-ptr-ref-in-free-state.diff 
3.2 noble
nfs-ganesha (4.3-8ubuntu1.1) noble; urgency=medium  
 

 
  * Fix null pointer ref in free_state (LP: #2065856)   
 
- d/p/20-fix-null-ptr-ref-in-free-state.diff 


#4 dep-3 headers
As mentioned I'm happy you have them.
But since I came to the point to ask you to refresh your proposal anyway.
On one hand since it is adapted we'd change origin->backport
And on the other I see no reason why we should not use exactly the text from 
the upstream patch.
Was there a reason to reformat it?
I'd suggest starting it with

Description: free_state may not always be able to be called with a valid export
 Instead of trying to use the export attached to a state to call
 the FSAL free_state, use a function pointer which if non-NULL
 is used, otherwise we just gsh_free the state (which works for all
 in-tree FSALs).
Origin: backport, 
https://github.com/nfs-ganesha/nfs-ganesha/commit/336abcba0b9e0dae0aadb4657c311d04862f2028
Bug: https://github.com/nfs-ganesha/nfs-ganesha/issues/904
Bug-Ubuntu: https://launchpad.net/bugs/2065856
Author: Frank S. Filz 
Reviewed-By: Frank S. Filz 
Last-Update: 2024-05-16

---


** Bug watch added: github.com/nfs-ganesha/nfs-ganesha/issues #904
   https://github.com/nfs-ganesha/nfs-ganesha/issues/904

** Changed in: nfs-ganesha (Ubuntu Mantic)
   Status: New => Won't Fix

** Changed in: nfs-ganesha (Ubuntu Noble)
   Status: New => Confirmed

** Changed in: nfs-ganesha (Ubuntu Oracular)
   Status: In Progress => Confirmed

** Changed in: nfs-ganesha (Ubuntu Noble)
   Status: Confirmed => Incomplete

** Changed in: nfs-ganesha (Ubuntu Oracular)
   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/2065856

Title:
  SEGFAULTs in v4.3 with GlusterFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2065856/+subscriptions


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

[Bug 2065856] Re: SEGFAULTs in v4.3 with GlusterFS

Being an upstream merged change makes it ok for Oracular,
but for the backports it is complex as it is messing with memory management and 
as you said does not apply as-is.

Some comments and adaptations I'll have to make:
- thanks for having dep-3 patch headers at all, that is often forgotten
- usually if modified from the original it states backport instead of upstream, 
but I can fix that along the way
- the version in the changelog would not work. Noble and Oracular are both at 
4.3-8ubuntu1. Only Oracular can go to the proposed 4.3-8ubuntu2 noble will need 
to go to 4.3-8ubuntu1.1. If you are curious about this you can read [1] which 
is an explanation on this more complex than it should be topic :-)
- it is no rule but personal preference to list the related patch in a changelog

Other than that this LGTM, it is complex to test and I need to ask you
if you are willing and able to do the same for all releases that need
SRU verification (noble + mantic in this case).

OTOH strictly speaking the rule is to fix all "later" releases.
We could as well assume that nfs-ganesha is probably not the most common mantic 
workload and it goes out of support soon. So instead of messing with yet 
another version we could stick to what you tested already as oracular and noble 
have the same.

I'll try to prep MPs with the same content you had but my fixes I mentioned 
above on top.
You can give me a +1 that this matches what you have and expected and then I 
could upload it.

[1]: https://github.com/canonical/ubuntu-maintainers-
handbook/blob/main/VersionStrings.md

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

Title:
  SEGFAULTs in v4.3 with GlusterFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2065856/+subscriptions


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

[Bug 2065856] Re: SEGFAULTs in v4.3 with GlusterFS

Hi, I come by reviewing patches that have patches to sponsor, trying to help 
this going forward.
Thank you for your work and linking the related upstream discussions.

The patch is merged upstream but only in 5.0 and later.
There have been some reports that around 4.0 it was still ok.
Comparing that to Ubuntu revisions that means we need to consider fixing 
mantic, noble and oracular (as per SRU policy we need to fix all to avoid the 
issue coming back on upgrades).

Earlier releases do not have the issue, and the patch can be dropped
once we merge 5.0 or later.

Updating bug states accordingly.

** Also affects: nfs-ganesha (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: nfs-ganesha (Ubuntu Oracular)
   Importance: Undecided
   Status: In Progress

** Also affects: nfs-ganesha (Ubuntu Mantic)
   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/2065856

Title:
  SEGFAULTs in v4.3 with GlusterFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2065856/+subscriptions


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

[Bug 2054391] Re: Fix CPU thermal sensors enumeration

This all LGTM, sponsoring to jammy-unapproved

$ dput ubuntu ../thermald_2.4.9-1ubuntu0.5_source.changes
Uploading thermald using ftp to ubuntu (host: upload.ubuntu.com; directory: 
/ubuntu)
running gitubuntu: Warn if uploading without git-ubuntu Vcs-* entries.
running updatemaintainer: Stop if ubuntu changes are without ubuntu maintainer.
running gpg: check GnuPG signatures before the upload
running suite-mismatch: check the target distribution for common errors
running ppaforppaonly: Stop uploads to the archive with or to ppa without ~ppa 
suffix.
running nobug: Stop if uploading without any bug reference.
running releasemismatch: Warn about mismatching suffixesg e.g. focal with a 
XX.YY not being 20.04
running placeholderbug: Stop if using common placeholder numbers as bug 
reference.
running supported-distribution: check whether the target distribution is 
currently supported (using distro-info)
{'allowed': ['release', 'proposed', 'backports', 'security'], 'known': 
['release', 'proposed', 'updates', 'backports', 'security']}
running check-debs: makes sure the upload contains a binary package
running required-fields: check whether a field is present and non-empty in the 
changes file
running checksum: verify checksums before uploading
running badauthor: Stop if uploading with root@ or ubuntu@ email adresses.
Uploading thermald_2.4.9-1ubuntu0.5.dsc
Uploading thermald_2.4.9-1ubuntu0.5.debian.tar.xz
Uploading thermald_2.4.9-1ubuntu0.5_source.buildinfo
Uploading thermald_2.4.9-1ubuntu0.5_source.changes

Up to the SRU team to have a second look and then probably to you
@kaihengfeng to test it on a system of the right size for verification.

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

Title:
  Fix  CPU thermal sensors enumeration

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2054391/+subscriptions


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

[Bug 2054391] Re: Fix CPU thermal sensors enumeration

I had two systems, none had more than two thermal zones.
It was enough to outline the test a bit better, but not to show the good / bad 
case output.

But it gave me the chance to test and install the build I had which is
all fine

$ sudo apt install ./thermald_2.4.9-1ubuntu0.5_amd64.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'thermald' instead of './thermald_2.4.9-1ubuntu0.5_amd64.deb'
The following packages will be upgraded:
  thermald
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/221 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 /home/ubuntu/thermald_2.4.9-1ubuntu0.5_amd64.deb thermald amd64 
2.4.9-1ubuntu0.5 [221 kB]
(Reading database ... 106221 files and directories currently installed.)
Preparing to unpack .../thermald_2.4.9-1ubuntu0.5_amd64.deb ...
Unpacking thermald (2.4.9-1ubuntu0.5) over (2.4.9-1ubuntu0.4) ...
Setting up thermald (2.4.9-1ubuntu0.5) ...
Processing triggers for dbus (1.12.20-2ubuntu4.1) ...
Processing triggers for man-db (2.10.2-1) ...
Scanning processes...   

   
Scanning processor microcode... 

   
Scanning linux images...

   

Running kernel seems to be up-to-date.

The processor microcode seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this
host.


** Description changed:

  [Impact]
  Some CPU sensors are not enumerated, this can make thermald deviates from the 
correct behavior of the CPU TDP.
  
  [Fix]
  Traverse all sensors under hwmon sysfs directory to make sure everything is 
enumerated.
  
  [Test]
  Check the output of thermald. Once the fix is in place, thermal zones that 
are previously omitted now shows up:
  [INFO]Zone 1: AMBF, Active:1 Bind:1 Sensor_cnt:1
+ To do so
+ 0. get a large machine which will have more thermal zones
+ 1. stop the potentially auto-running service
+$ systemctl stop thermald
+ 2. run the daemon in foreground with loglevel to see what is going on.
+On many modern systemd (=the large ones) it might not know the CPUid,
+to bypass that for the test you can ask it to ignore the check
+$ sudo thermald --no-daemon --loglevel=info --ignore-cpuid-check
+ 3. check the output
+On init the system will be probed and that will show something like:
+ 
+ ...
+  ZONE DUMP BEGIN
+ [1718954645][INFO]Zone 2: cpu, Active:1 Bind:0 Sensor_cnt:1
+ ...
+ [1718954645][INFO]Zone 3: cpu, Active:1 Bind:0 Sensor_cnt:1
+ ...
+  ZONE DUMP END
+ 
+ In here, on systems with many thermal zones one would before the fix
+ only see a few, and with the fix more zones.
+ 
  
  [Where problems could occur]
  Since the new logic traverse the whole hwmon sysfs, the startup time can take 
slightly longer.

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

Title:
  Fix  CPU thermal sensors enumeration

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2054391/+subscriptions


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

[Bug 2054391] Re: Fix CPU thermal sensors enumeration

Local test build has been happy as well.

You test description is not wrong, but a bit too incomplete for what an SRU 
should have.
"Check the output of thermald" could use some "how exactly" and good/bad case 
examples.

I got a system in testflinger with a modern CPU hoping it would expose
this issue to test and try to improve that to be more acceptable.

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

Title:
  Fix  CPU thermal sensors enumeration

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2054391/+subscriptions


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

[Bug 2054391] Re: Fix CPU thermal sensors enumeration

I checked upstream git if there are any follow up fixes to the changed
code we should apply right away, there are none.

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

Title:
  Fix  CPU thermal sensors enumeration

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2054391/+subscriptions


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

[Bug 2054391] Re: Fix CPU thermal sensors enumeration

The patch headers requested by Lucas are good as well now - thanks!
The changelog mention of the related patch is 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/2054391

Title:
  Fix  CPU thermal sensors enumeration

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2054391/+subscriptions


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

[Bug 2054391] Re: Fix CPU thermal sensors enumeration

I double checked if we also need to fix others e.g. mantic as often -dev 
releases in between are forgotten but they need to be fixed as well to avoid 
upgraders regressing.
But that looks fine

git tag --contains df8ac025d22e51c237c8ebe2aa25bf672ec04edb
v2.5
v2.5.0-pre
v2.5.1
v2.5.2
v2.5.3
v2.5.4
v2.5.5
v2.5.6
v2.5.7

vs

 thermald | 1.9.1-1build1| focal  | source, amd64
 thermald | 1.9.1-1ubuntu0.6 | focal-updates  | source, amd64
 thermald | 1.9.1-1ubuntu0.7 | focal-proposed | source, amd64
 thermald | 2.4.9-1  | jammy  | source, amd64
 thermald | 2.4.9-1ubuntu0.4 | jammy-updates  | source, amd64
 thermald | 2.5.4-2  | mantic | source, amd64
 thermald | 2.5.6-2build2| noble  | source, amd64
 thermald | 2.5.7-3  | oracular   | source, amd64

So anything >= mantic is already fine having 2.5.4 there.

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

Title:
  Fix  CPU thermal sensors enumeration

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2054391/+subscriptions


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

[Bug 2054391] Re: Fix CPU thermal sensors enumeration

Hi,
thanks for your update. I come by looking at the sponsoring queue and will have 
a look...

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

Title:
  Fix  CPU thermal sensors enumeration

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2054391/+subscriptions


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

[Bug 2067480] Re: MRE updates 23.11.1(Noble)/22.11.5(Mantic)/21.11.7(Jammy)

Frode mentioned he will aim at doing the OVS upload in the next pulse.
To track that I've opened bug 2069991 for him, which allows us to track
it.

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

Title:
  MRE updates 23.11.1(Noble)/22.11.5(Mantic)/21.11.7(Jammy)

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


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

[Bug 2069991] [NEW] [SRU] openvswitch 3.3.1 point release

Public bug reported:

[Impact]
This release sports mostly bug-fixes and we would like to make sure all of our
supported customers have access to these improvements. Among other things this
also fixes a test issue with newer DPDK which will unblock providing the 
backport
of that stable release.

The update contains the following package updates:

   * openvswitch 3.3.1

For more details see:

   * https://www.openvswitch.org/releases/NEWS-3.3.1.txt
   * https://github.com/openvswitch/ovs/compare/v3.3.0...v3.3.1

It will include [1] which can thereby be dropped from the delta.

[1]:
https://github.com/openvswitch/ovs/commit/c560f6ca3257dd3b64e01a4a244b02b90216858b

[Test Case]

The following SRU process was followed:

https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates

In order to avoid regression of existing consumers, the OpenStack team will
run their continuous integration test against the packages that are in
-proposed. A successful run of all available tests will be required before the
proposed packages can be let into -updates.

The OpenStack team will be in charge of attaching the output summary of the
executed tests. The OpenStack team members will not mark ‘verification-done’ 
until
this has happened.

[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned tests are attached to this bug.

[other Info]
This is a regular update policy, it follows many others:
- #1021530 [SRU] update to include stable fixes for OVS 1.4
- #1470120 [SRU] openvswitch 2.3.2
- #1641956 [SRU] openvswitch 2.6.1
- #2003059 [SRU] openvswitch 3.0.3 point release
- #2003060 [SRU] openvswitch 2.17.5 point release
- #2025319 [SRU] openvswitch 3.1.2 point release
- #2025323 [SRU] openvswitch 2.17.7 point release
- #2039906 [SRU] openvswitch 3.2.1 point release
- #2039907 [SRU] openvswitch 3.1.3 point release
- #2039908 [SRU] openvswitch 2.17.8 point release

** Affects: cloud-archive
 Importance: Undecided
 Status: New

** Affects: openvswitch (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: openvswitch (Ubuntu Noble)
 Importance: Undecided
 Assignee: Frode Nordahl (fnordahl)
 Status: New

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

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

** Changed in: openvswitch (Ubuntu Noble)
 Assignee: (unassigned) => Frode Nordahl (fnordahl)

** Also affects: cloud-archive
   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/2069991

Title:
  [SRU] openvswitch 3.3.1 point release

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


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

[Bug 2069991] Re: [SRU] openvswitch 3.3.1 point release

FYI - I can't set/triage the UCA task to set the actual release these
goes to

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

Title:
  [SRU] openvswitch 3.3.1 point release

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


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

[Bug 2067480] Re: MRE updates 23.11.1(Noble)/22.11.5(Mantic)/21.11.7(Jammy)

The issue in openvswitch tests with the new release has been fixed (Only Noble 
onwards).
See: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2067889

You might coordinate with Frode if/when that will land in OVS in Noble.
That might be full 3.3.1 (if that is what they planned) or just the test fix 
and keeping it in block-proposed as it has no real value for the end user.

I heard nothing bad of 21.11.7 or 22.11.5 yet, so they should (tm) be
fine.

Overall this should be unblocked for when you are back @mirespace

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

Title:
  MRE updates 23.11.1(Noble)/22.11.5(Mantic)/21.11.7(Jammy)

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


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

[Bug 2063046] Re: build-depends on obsolete python3-nose-timer

I've put a reminder to bug 2068019 and we are happy to wait for this new upload 
to unblock this.
But since we know what it actually waits for it makes no sense to show up in 
the bug housekeeping weekly - dropping the server-todo tag.

** Tags removed: server-todo

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

Title:
  build-depends on obsolete python3-nose-timer

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


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

[Bug 2068019] Re: Upgrade to v2.11.1.4 on Oracular (24.10)

Once this new version is ready Miriam will also include the fix for bug 2063046 
in the upload.
Thanks!

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

Title:
  Upgrade to v2.11.1.4 on Oracular (24.10)

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


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

[Bug 2069330] Re: make-ssl-cert: expiration-day (-x option) is wrongly handled, if set it is 3 days instead of the value given

** Changed in: ssl-cert (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

** Tags added: bitesize

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

Title:
  make-ssl-cert: expiration-day (-x option) is wrongly handled, if set
  it is 3 days instead of the value given

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ssl-cert/+bug/2069330/+subscriptions


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

[Bug 720638] Re: snmpd crashes with segfault (libnetsnmpmibs.so.15.1.2)

** Changed in: net-snmp (Ubuntu)
 Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)

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

Title:
  snmpd crashes with segfault (libnetsnmpmibs.so.15.1.2)

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


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

[Bug 2064843] Re: Brick SEGFAULTs in 11.1

Thank you that satisfies the test case, a few more day of maturing.

** 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/2064843

Title:
  Brick SEGFAULTs in 11.1

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


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

[Bug 2065423] Re: Update AppArmor template to allow confined runc to kill containers

FYI: Uploaded by Lucas but atm stuck in proposed for networking issues
in the test

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

Title:
  Update AppArmor template to allow confined runc to kill containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2065423/+subscriptions


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

[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony

That is awesome, thanks Vincent.
We will pick it up in the subsequent merge of chrony then.

** Tags removed: server-todo

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

Title:
  apparmor blocks using more than one timemaster clock with chrony

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


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

[Bug 1878264] Re: nvme smart error count email after upgrading to 20.04

Sadly the backport seems to be complex per Andreas evaluation.

It is fixed in Noble onwards and the symptom is "only" false positive
notifications.

As-is this seems not to be feasible effort to fix it in Jammy and before.
If someone has a great approach to tackle this more easily we are open to 
reconsider, the same is true for a proposed patch.

To be clear, it is still valid, but we won't put focus on it anymore.

** Tags removed: server-todo

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

Title:
  nvme smart error count email after upgrading to 20.04

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


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

[Bug 2045297] Re: file root.hints needs update

2024-06-12 Thread Christian Ehrhardt 

** Tags removed: server-todo

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

Title:
  file root.hints needs update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-docker-images/+bug/2045297/+subscriptions


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

2024-06-12 Thread Christian Ehrhardt 

Fully complete in Oracular now and DPDK/OVS migrated together
https://launchpad.net/ubuntu/+source/dpdk/23.11.1-1

@Frode - will you prepare an OVS 3.3.1 for Noble so we can do the DPDK
stable update afterwards?

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

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

** No longer affects: dpdk (Ubuntu Noble)

** Changed in: dpdk (Ubuntu)
   Status: New => Invalid

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

** Changed in: openvswitch (Ubuntu Noble)
   Status: New => Confirmed

** Changed in: openvswitch (Ubuntu Noble)
 Assignee: (unassigned) => Frode Nordahl (fnordahl)

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2066269] Re: [MIR] sysprof

2024-06-11 Thread Christian Ehrhardt 

Review for Source Package: sysprof

[Summary]
MIR team ACK

While not the biggest attack surface, it could get crafted external data
which is a common way. Hence IMHO this does need a security review,
I'll assign ubuntu-security.

List of specific binary packages to be promoted to main: sysprof,
libsysprof-6-6, libsysprof-6-modules, libsysprof-capture-4-dev,
libsysprof-6-dev

Specific binary packages built, but NOT to be promoted to main: n/a

Notes:
Required TODOs:
- none
Recommended TODOs:
- #1 The package should get a team bug subscriber before being promoted
  as you know and already wrote, but as usual that can be done once it
  is supposed to be promoted.

[Rationale, Duplication and Ownership]
- There is no other package in main providing the same functionality.
  It is augmenting the console use cases of perf, but there is nothing in main
  that has the same workflow and visualization.
- A team is committed to own long term maintenance of this package.
- The rationale given in the report seems valid and useful for Ubuntu

[Dependencies]
OK:
- no other Dependencies to MIR due to this (libdex and libpanel already filed)
- no -dev/-debug/-doc packages that need exclusion
  - libsysprof-6-dev has dependencies, but they are all in main
  - libsysprof-capture-4-dev only has internal dependencies
- No dependencies in main that are only superficially tested requiring
  more tests now.

Problems: None

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have unexpected Built-Using entries
- not a go package, no extra constraints to consider in that regard
- not a rust package, no extra constraints to consider in that regard

Problems: None

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not expose any external endpoint (port/socket/... or similar)
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)
- does not deal with cryptography (en-/decryption, certificates,
  signing, ...)
- this makes appropriate (for its exposure) use of established risk
  mitigation features

Problems:
- Does parse data formats (files [images, video, audio,
  xml, json, asn.1], network packets, structures, ...) from
  an untrusted source. An explicit use case mentioned is people attaching
  such profiles to bugs.

[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time
  - test suite fails will fail the build upon error.
- does have a test suite that runs as autopkgtest
  while the tests are superficial, they cover reverse dep failures
- In addition you have already defined [1] which covers for what is left
  like how things "look like".
  [1]: https://wiki.ubuntu.com/DesktopTeam/TestPlans/Sysprof
- The manual test might in the future be automated, but all together are a
  great set of tests and satisfies what we look for as a minimum
- This does not need special HW for build or test
- no new python2 dependency

Problems: None

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking is in place.
- debian/watch is present and looks ok
- Upstream update history is ok
- Debian/Ubuntu update history is ok
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings (the few we have are resonable IMHO)
- debian/rules are rather clean
- It is not on the lto-disabled list

Problems: None

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of user nobody
- no use of setuid / setgid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit or libseed
- part of the UI, desktop file is ok
- translation (of the help AFAICS) is present

Problems:
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH.
  This is not so much of a problem as it would usually be, as it is a
  conceptual part of the design. It needs to peload to insert mem tracking
  (just like other memory profilers). It needs to get root permissions
  to ptrace.
  But that is not unexpected and asks the user about granting permissison.
  The only drawback is that therefore the attack severity (if there is one)
  is higher.
  Gladly for the most likely attack surface (manipulated profile data) there
  is no elevated permission needed (that is only for profiling)

** Changed in: sysprof (Ubuntu)
 Assignee: Christian Ehrhardt  (paelzer) => Ubuntu Security Team 
(ubuntu-security)

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

[Bug 2066269] Re: [MIR] sysprof

2024-06-11 Thread Christian Ehrhardt 

Sorry it took so long from the assignment last week, finally started on this 
MIR review.
If I can't complete I'd at least leave you what I found until then so you can 
act on these.

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

Title:
  [MIR] sysprof

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

2024-06-11 Thread Christian Ehrhardt 

New OVS is in Oracular
  https://launchpad.net/ubuntu/+source/openvswitch/3.3.1-1

Some tests already were happy in old runs, ppc64 and arm64 have not run the way 
they need to.
I've triggered them with the new DPDK and the new OVS together.

Unless some other, formerly masked, test issue affects that it should be
good now.

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

2024-06-10 Thread Christian Ehrhardt 

We found a different solution that fixes even more.

Included as:
commit cc99622485062b902362ffa3a08317dc0f926164
Author: David Marchand 
Date:   Thu Jun 6 15:11:11 2024 +0200

system-dpdk: Fix socket conflict when starting testpmd.

Which is in upstream stable update v3.3.1

Frode will as usual prepare v3.3.1 which will then in turn fix the tests.
There is no real issue which would imply needing a versioned dependency.

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

2024-06-05 Thread Christian Ehrhardt 

Submitted for upstream discussion:
https://mail.openvswitch.org/pipermail/ovs-dev/2024-June/414484.html

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

2024-06-05 Thread Christian Ehrhardt 

Thanks to m4 expansion I had to change it in tests/system-dpdk-testsuite for 
retesting.
The real fix would be in ./tests/system-dpdk-macros.at though.

Adding the following to the rules made it work:
  /TELEMETRY: Socket write base info to client failed/d

Now the questions is "is this a warning that is fine to have in the
tests or is this masking a legit error?"

I'll propose that to openswitch setting a set of people on CC that deal with 
those topics.
In that discussion we can hopefully conclude the above question.

P.S.That was a long strange trip - I wish the test would say something
more clear like "I found this  in the log which I didn't expect",
but since it does not (clear enough to me at least) that was a debugging
rabbit hole.

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

2024-06-05 Thread Christian Ehrhardt 

With what I know from comment #14 and comment #5 I tried to get deeper
to finally find what actually goes wrong which still eludes me :-/


Env vars that we need:
OVS_RUNDIR=/var/run/openvswitch/
abs_top_srcdir=../_debian/openvswitch/


1. db creation + starting ovsdb with --detach in background + checking if it 
has started
=> logs in /var/log/openvswitch/ovsdb-server.log

  ../../tests/system-dpdk.at:741: touch .conf.db.~lock~
  ../../tests/system-dpdk.at:741: ovsdb-tool create conf.db 
$abs_top_srcdir/vswitchd/vswitch.ovsschema
  ../../tests/system-dpdk.at:741: ovsdb-server --detach --no-chdir --pidfile 
--log-file --remote=punix:$OVS_RUNDIR/db.sock

2. initialize and start vswitch in background
=> logs in /var/log/openvswitch/ovs-vswitchd.log

../../tests/system-dpdk.at:741: ovs-vsctl --no-wait init 
../../tests/system-dpdk.at:741: ovs-vsctl --no-wait set Open_vSwitch . 
other_config:dpdk-init=true
../../tests/system-dpdk.at:741: ovs-vsctl --no-wait set Open_vSwitch . 
other_config:dpdk-extra="--log-level=pmd.*:error --no-pci"
../../tests/system-dpdk.at:741: ovs-vswitchd  --detach --no-chdir --pidfile 
--log-file -vvconn -vofproto_dpif -vunixctl

3. add bridge and port
../../tests/system-dpdk.at:744: ovs-vsctl add-br br10 -- set bridge br10 
datapath_type=netdev
../../tests/system-dpdk.at:745: ovs-vsctl add-port br10 dpdkvhostuserclient0 -- 
\
  set Interface dpdkvhostuserclient0 type=dpdkvhostuserclient 
options:vhost-server-path=$OVS_RUNDIR/dpdkvhostclient0

4. check for log to be as expected
system-dpdk.at:745: waiting until grep "VHOST_CONFIG: 
($OVS_RUNDIR/dpdkvhostclient0) vhost-user client: socket created" 
ovs-vswitchd.log...
2024-06-05T08:16:32.191Z|00064|dpdk|INFO|VHOST_CONFIG: 
(/cPJ/_debian/tests/system-dpdk-testsuite.dir/020/dpdkvhostclient0) vhost-user 
client: socket created, fd: 52
system-dpdk.at:745: wait succeeded immediately
system-dpdk.at:745: waiting until grep "vHost User device 
'dpdkvhostuserclient0' created in 'client' mode, using client socket" 
ovs-vswitchd.log...
2024-06-05T08:16:32.191Z|00065|netdev_dpdk|INFO|vHost User device 
'dpdkvhostuserclient0' created in 'client' mode, using client socket 
'/cPJ/_debian/tests/system-dpdk-testsuite.dir/020/dpdkvhostclient0'
system-dpdk.at:745: wait succeeded immediately
system-dpdk.at:745: waiting until grep "VHOST_CONFIG: 
($OVS_RUNDIR/dpdkvhostclient0) reconnecting..." ovs-vswitchd.log...
2024-06-05T08:16:32.191Z|00067|dpdk|INFO|VHOST_CONFIG: 
(/cPJ/_debian/tests/system-dpdk-testsuite.dir/020/dpdkvhostclient0) 
reconnecting...
system-dpdk.at:745: wait succeeded immediately

=> so far, all good in both cases

6. start testpmd in other console
dpdk-testpmd --in-memory --socket-mem=512 --single-file-segments --no-pci 
--vdev="net_virtio_user,path=$OVS_RUNDIR/dpdkvhostclient0,server=1"

Only diff so far, the known:
  dpdk|ERR|TELEMETRY: Socket write base info to client failed


5. set valid MTU

../../tests/system-dpdk.at:746: ovs-vsctl set Interface dpdkvhostuserclient0 
mtu_request=9702
../../tests/system-dpdk.at:747: ovs-vsctl show

6. set invalid MTU

../../tests/system-dpdk.at:756: ovs-vsctl get Interface dpdkvhostuserclient0 mtu
../../tests/system-dpdk.at:761: ovs-vsctl set Interface dpdkvhostuserclient0 
mtu_request=9711
../../tests/system-dpdk.at:762: grep "dpdkvhostuserclient0: unsupported MTU 
9711" ovs-vswitchd.log
stdout:
2024-06-05T08:16:36.857Z|00117|netdev_dpdk|WARN|dpdkvhostuserclient0: 
unsupported MTU 9711

=> Still both systems behave the same

7. delete port and stop testpmd
../../tests/system-dpdk.at:765: ovs-vsctl del-port br10 dpdkvhostuserclient0
../../tests/system-dpdk.at:766: kill `cat testpmd.pid`
The latter in my case is stopping it in the other console.

It seems then the macro/function OVS_DPDK_STOP_VSWITCHD is crucial.
It is called like this in ./tests/system-dpdk.at:

OVS_DPDK_STOP_VSWITCHD(["dnl
/VHOST_CONFIG: (.*dpdkvhostclient0) failed to connect: No such file or 
directory/d
/dpdkvhostuserclient0: unsupported MTU 9711/d
/failed to set MTU for network device dpdkvhostuserclient0: Invalid 
argument/d"])

It seems it lists known messages it expectes in the vswitch log.


The effective clal I see in the log is even a bit longer, maybe some other 
known messages are added.

../../tests/system-dpdk.at:767: check_logs "/VHOST_CONFIG: (.*dpdkvhostclient0) 
failed to connect: No such file or directory/d
/dpdkvhostuserclient0: unsupported MTU 9711/d
/failed to set MTU for network device dpdkvhostuserclient0: Invalid 
argument/d"";/does not exist. The Open vSwitch kernel module is probably not 
loaded./d
/does not support MTU configuration,/d
/EAL: No \(available\|free\) .*hugepages reported/d
/Failed to enable flow control/d
/ice_vsi_config_outer_vlan_stripping(): Single VLAN mode (SVM) does not support 
qinq/d
/Rx checksum offload is not supported on/d
/TELEMETRY: No legacy callbacks, legacy socket not created/d"

defined as expected with extra DPDK messages in tests/system-dpdk-
macros.at:

[Bug 2063970] Re: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment.

I checked with my peers and it seems this happens indeed to almost
everyone. The only exceptions are thos that diabled the assistant or not
using gnome in the first place.

@Jorrit
I agree, the folks I checked had various other GPUs - all affected AFAICS.

@Jon
Just like you I usually use just super+arrow and it happens there on all my
screens. Getting stuck a "little bit" about every third time I rearrange
windows. A little means I can get it to hide again by re-sizing the window over
and over. Like left attach, right attach, maximize, ... until the overlay is
gone.
But sometimes, it is so persistent that AFAIK only disabling the assistant gets
it removed.

@Daniel van Vugt
Thanks for the hint - that is how most go for now, but I guess many want the
benefits of the advanced tiling back as well :-)

Since I could add like 5/5 more people as affected after speaking with
them I wonder if it would be reasonable to raise the severity on this to
better represent that. And maybe assign someone to work on this to get
an expectation when it might be tackled and fixed? I'll ping the Desktop
team to consider that ...

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

Title:
Enhanced tiling orange shading that indicates what a window will
resize to will persist even after I'm done with the adjustment.

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

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

[Bug 2066262] Re: [MIR] libdex

** Changed in: libdex (Ubuntu)
 Assignee: (unassigned) => Lukas Märdian (slyon)

** Changed in: libdex (Ubuntu)
 Assignee: Lukas Märdian (slyon) => Ioanna Alifieraki (joalif)

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

Title:
  [MIR] libdex

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


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

[Bug 2066272] Re: [MIR] libpanel

** Changed in: libpanel (Ubuntu)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Changed in: libpanel (Ubuntu)
 Assignee: Ioanna Alifieraki (joalif) => Lukas Märdian (slyon)

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

Title:
  [MIR] libpanel

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


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

[Bug 2066269] Re: [MIR] sysprof

** Changed in: sysprof (Ubuntu)
 Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

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

Title:
  [MIR] sysprof

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

Here the differences I spot on a high level:

4. OVS-DPDK - ping vhost-user ports
 - testpmd.log - not much difference
 - ovsdb-server.log
   ovsdb-server is killed (sig 15) in the bad case 7 seconds after starting
   that kill is after the test log ends, so it could be cleanup
 - ovs-vswitchd.log
   dpdk|ERR|TELEMETRY: Socket write base info to client failed  (likely red 
herring)
   in addition to all-same messages like the good case, the bad case shows
   dpdk|ERR|remove_xdp_program(): bpf_xdp_query_id failed
   dpdk|ERR|eth_dev_close(): Error while removing XDP program.
 - system-dpdk-testsuite.log
   differs at the end, good case seems to enter cleanup while bad case does 
lots of things
   bad case has more content as it reports detailed steps
   can't cleanup testpmd (pid already gone)

16. OVS-DPDK - MTU increase vport port
17. OVS-DPDK - MTU decrease vport port (same)
20. OVS-DPDK - MTU upper bound vport port (same)
21. OVS-DPDK - MTU lower bound vport port (same)
 - testpmd.log
   good case sees ports going down and stopping
 - ovsdb-server.log
  ovsdb-server is killed (sig 15) in the bad case a few seconds after 
starting
  that kill is after the test log ends, so it could be cleanup
 - ovs-vswitchd.log
  dpdk|ERR|TELEMETRY: Socket write base info to client failed  (likely red 
herring)
 - system-dpdk-testsuite.log
   differs at the end, good case seems to enter cleanup while bad case does 
lots of things
   bad case has more content as it reports detailed steps
   can't cleanup testpmd (pid already gone)


So on case 4 it could be the xdp error which is new.
On the other cases only the telemetry is odd, but that seemed (see above) like 
a false positive.
Yet there are chances a component I didn't see yet tests on no ERR messages.
Worth a rebuild with this reverted?

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

** Attachment added: "Test results on 23.11.1"
   
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2067889/+attachment/5785828/+files/bad-case.tgz

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

** Attachment added: "Test results on 23.11"
   
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2067889/+attachment/5785827/+files/good-case.tgz

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

After the setup outlined above I was running the set the autopkgtest identified 
(4-5 16-17 20-21
). With that I was able to trigger good/bad case in a reproducible way.

In my repro-environment, test 5 also fails in the good case - which
might just be my test environment's fault. Hence I'm comparing 4 16-17
20-21 now and will attach the detailed test logs for them for the good
and bad case (which only differs in the DPDK version used 23.11 vs
23.11.1).

But the good case leaves no details of the execution in the log, hence
I'll also collect and attach the full output of _debian/tests/system-
dpdk-testsuite.dir which holds all these details.

Hopefully we find a pattern comparing the testcases one by one in these
...

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

Directly running just the failing test (of the 6 I picked the MTU upper
bound that I analyzed above) works like this:

# WIP

apt install ubuntu-dev-tools conntrack curl devscripts dpdk-dev ethtool equivs 
net-tools ncat python3-pyftpdlib tcpdump wget
apt-get remove --yes --purge netcat-openbsd
ln -sf /usr/bin/ncat /usr/bin/nc
pull-lp-source openvswitch
cd openvswitch-3.3.0/
mk-build-deps --install --tool "apt-get -o Debug::pkgProblemResolver=yes 
--no-install-recommends --yes" --remove debian/control
./debian/rules build
systemctl stop openvswitch-ipsec ovs-vswitchd ovsdb-server
./tests/system-dpdk-testsuite -C _debian/tests -j1 
AUTOTEST_PATH="$(pwd)/tests:$(pwd)/_debian/tests" 20

# Warning
While it seems to mostly work these steps are yet incomplete, it fails even 
with the good version unable to start the vhost-user client successfully. I'll 
update it once I find more, maybe Fnordahl knows more about OVS tests.

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

The log message I have seen might be a red herring as well [1] added
that but unless something insists on "non-ERR" that should not be the
reason as it is not changing behavior.

But then, what else am I looking for, Frode confirmed that he will do
some triage and debug from the OVS POV which might help to find where
things actually break.

[1]: https://github.com/DPDK/dpdk-
stable/commit/cbd1c165bb1ea86efc31c8ac309ee5e7c5f555cb

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

Frode mentioned that OVS 3.3.1 might get some bonus love in regard to DPDK 
23.11.1 [1].
In the past that was only ever needed for new features, which the stable update 
does not have, but there is a chance that this is just a test bug I do not yet 
understand fully - so yeah, giving this a look with OVS 3.3.1 might be worth a 
try.

Worst case there is a chance that DPDK 23.11.1 only works with OVS
>=3.3.1 which we need to express in dependencies than (which is odd as
DPDK does not depend on OVS, but vice versa)

Also adding a tag to show up in excuses, as this is what makes those
stuck in proposed migration.

** Tags added: update-excuse

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

** Attachment added: "ovs-vswitchd-bad-23.11.1-1.log"
   
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2067889/+attachment/5785493/+files/ovs-vswitchd-bad-23.11.1-1.log

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

** Attachment added: "ovs-vswitchd-good-23.11-1.log"
   
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2067889/+attachment/5785494/+files/ovs-vswitchd-good-23.11-1.log

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

** Attachment added: "just the log section of the failures"
   
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2067889/+attachment/5785468/+files/dpdk-ovs-test-fail-log.txt

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

The only very unique entry I got here in those logs of the dpdk enabled
openvswitch in the bad case was:

1|dpdk|ERR|TELEMETRY: Socket write base info to client failed

Not sure where to go with that, is that from the switch or the client even?
I might need to reach out if there are any known issues where, now that I have
some pointers, this rings a bell.

** Also affects: openvswitch (Ubuntu)
   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/2067889

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

23.11.1-1 console output

root@o-dpdk-ovs:~# systemctl stop openvswitch-switch ovs-vswitchd
root@o-dpdk-ovs:~# rm /var/log/openvswitch/ovs-vswitchd.log
root@o-dpdk-ovs:~# systemctl start openvswitch-switch ovs-vswitchd
root@o-dpdk-ovs:~# ovs-vsctl show
9a966e25-a911-45d1-a5ad-1beeb7c142a1
ovs_version: "3.3.0"
root@o-dpdk-ovs:~# ovs-vsctl add-br br10 -- set bridge br10 datapath_type=netdev
root@o-dpdk-ovs:~# 
OVS_RUNDIR="/tmpdir/_debian/tests/system-dpdk-testsuite.dir/020"
root@o-dpdk-ovs:~# rm -rf $OVS_RUNDIR
root@o-dpdk-ovs:~# mkdir -p $OVS_RUNDIR
root@o-dpdk-ovs:~# ovs-vsctl add-port br10 dpdkvhostuserclient0 -- set 
Interface dpdkvhostuserclient0 type=dpdkvhostuserclient 
options:vhost-server-path=$OVS_RUNDIR/dpdkvhostclient0
root@o-dpdk-ovs:~# ovs-vsctl show
9a966e25-a911-45d1-a5ad-1beeb7c142a1
Bridge br10
datapath_type: netdev
Port dpdkvhostuserclient0
Interface dpdkvhostuserclient0
type: dpdkvhostuserclient
options: 
{vhost-server-path="/tmpdir/_debian/tests/system-dpdk-testsuite.dir/020/dpdkvhostclient0"}
Port br10
Interface br10
type: internal
ovs_version: "3.3.0"
root@o-dpdk-ovs:~# ovs-vsctl get Interface dpdkvhostuserclient0 link_state
up
root@o-dpdk-ovs:~# ovs-vsctl set Interface dpdkvhostuserclient0 mtu_request=9702
root@o-dpdk-ovs:~# ovs-vsctl get Interface dpdkvhostuserclient0 mtu
9702
root@o-dpdk-ovs:~# ovs-vsctl set Interface dpdkvhostuserclient0 mtu_request=9711
root@o-dpdk-ovs:~# ovs-vsctl get Interface dpdkvhostuserclient0 mtu
9702
root@o-dpdk-ovs:~# ovs-vsctl del-port br10 dpdkvhostuserclient0
root@o-dpdk-ovs:~# ovs-vsctl del-br br10

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

From here I was capturing full logs of this with DPDK 23.11-1 and
23.11.1-1

23.11-1 console output:

root@o-dpdk-ovs:~#  systemctl stop openvswitch-switch ovs-vswitchd
root@o-dpdk-ovs:~# rm /var/log/openvswitch/ovs-vswitchd.log
root@o-dpdk-ovs:~# systemctl start openvswitch-switch ovs-vswitchd
root@o-dpdk-ovs:~# ovs-vsctl show
9a966e25-a911-45d1-a5ad-1beeb7c142a1
ovs_version: "3.3.0"
root@o-dpdk-ovs:~# ovs-vsctl add-br br10 -- set bridge br10 datapath_type=netdev
root@o-dpdk-ovs:~# 
OVS_RUNDIR="/tmpdir/_debian/tests/system-dpdk-testsuite.dir/020"
root@o-dpdk-ovs:~# rm -rf $OVS_RUNDIR
root@o-dpdk-ovs:~#  mkdir -p $OVS_RUNDIR
root@o-dpdk-ovs:~# ovs-vsctl add-port br10 dpdkvhostuserclient0 -- set 
Interface dpdkvhostuserclient0 type=dpdkvhostuserclient 
options:vhost-server-path=$OVS_RUNDIR/dpdkvhostclient0
root@o-dpdk-ovs:~# ovs-vsctl show
9a966e25-a911-45d1-a5ad-1beeb7c142a1
Bridge br10
datapath_type: netdev
Port dpdkvhostuserclient0
Interface dpdkvhostuserclient0
type: dpdkvhostuserclient
options: 
{vhost-server-path="/tmpdir/_debian/tests/system-dpdk-testsuite.dir/020/dpdkvhostclient0"}
Port br10
Interface br10
type: internal
ovs_version: "3.3.0"
root@o-dpdk-ovs:~# ovs-vsctl get Interface dpdkvhostuserclient0 link_state
up
root@o-dpdk-ovs:~# ovs-vsctl set Interface dpdkvhostuserclient0 mtu_request=9702
root@o-dpdk-ovs:~# ovs-vsctl get Interface dpdkvhostuserclient0 mtu
9702
root@o-dpdk-ovs:~# ovs-vsctl set Interface dpdkvhostuserclient0 mtu_request=9711
root@o-dpdk-ovs:~# ovs-vsctl get Interface dpdkvhostuserclient0 mtu
9702
root@o-dpdk-ovs:~# ovs-vsctl del-port br10 dpdkvhostuserclient0
root@o-dpdk-ovs:~# ovs-vsctl del-br br10
root@o-dpdk-ovs:~# ovs-vsctl show
9a966e25-a911-45d1-a5ad-1beeb7c142a1
ovs_version: "3.3.0"

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

Trying to isolate the commands used in the failing test (works in a not
too small Oracular VM):

0. Prep install and config
 apt install openvswitch-switch-dpdk dpdk-dev
 echo "NR_2M_PAGES=784" >> /etc/dpdk/dpdk.conf
 systemctl restart dpdk
 update-alternatives --set ovs-vswitchd 
/usr/lib/openvswitch-switch-dpdk/ovs-vswitchd-dpdk
 ovs-vsctl --no-wait init
 ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true
 ovs-vsctl --no-wait set Open_vSwitch . 
other_config:dpdk-extra="--log-level=pmd.*:error --no-pci"
1. start OVS with DPDK support (this is the point where you'd restart new test 
iterations)
 systemctl stop openvswitch-switch ovs-vswitchd
 rm /var/log/openvswitch/ovs-vswitchd.log
 systemctl start openvswitch-switch ovs-vswitchd
 ovs-vsctl show
2. create an internal DPDK bridge with a vhostuserclient port with defined MTU
 ovs-vsctl add-br br10 -- set bridge br10 datapath_type=netdev
 OVS_RUNDIR="/tmpdir/_debian/tests/system-dpdk-testsuite.dir/020"
 rm -rf $OVS_RUNDIR
 mkdir -p $OVS_RUNDIR
 ovs-vsctl add-port br10 dpdkvhostuserclient0 -- set Interface 
dpdkvhostuserclient0 type=dpdkvhostuserclient 
options:vhost-server-path=$OVS_RUNDIR/dpdkvhostclient0
 ovs-vsctl show
3. connect a vhostuserclient server
 # Do this in a shell of its own, it will stay up
 dpdk-testpmd --in-memory --socket-mem=512 --single-file-segments --no-pci 
--vdev="net_virtio_user,path=$OVS_RUNDIR/dpdkvhostclient0,server=1 
--vdev=net_tap0,iface=tap0 -- -a --stats-period 2 --nb-cores 2 --rxq 2 --txq 2
4. check if it is truly ready
 ovs-vsctl show
 grep "virtio is now ready for processing" /var/log/openvswitch/ovs-vswitchd.log
 # should have a happy dpdkvhostuserclient0
 ovs-vsctl get Interface dpdkvhostuserclient0 link_state
 # should say "up"
5. set happy MTU
 ovs-vsctl set Interface dpdkvhostuserclient0 mtu_request=9702
 ovs-vsctl get Interface dpdkvhostuserclient0 mtu
 # should deliver 9702
6. set the bigger MTU
 ovs-vsctl set Interface dpdkvhostuserclient0 mtu_request=9711
 # the ovs-vswitchd.log will say (expected)
   dpdkvhostuserclient0: unsupported MTU 9711
   failed to set MTU for network device dpdkvhostuserclient0: Invalid argument
 ovs-vsctl get Interface dpdkvhostuserclient0 mtu
   # will still deliver 9702
7. cleanup the port
 ovs-vsctl del-port br10 dpdkvhostuserclient0
 # Should work without bad RC, log in ovs-vswitchd.log will say:
bridge|INFO|bridge br10: deleted interface dpdkvhostuserclient0 on port 1
dpif_netdev|INFO|PMD thread on numa_id: 0, core id:  1 destroyed.
dpdk(pmd-c01/id:8)|INFO|PMD thread released DPDK lcore 1.
dpdk|INFO|VHOST_CONFIG: 
(/tmpdir/_debian/tests/system-dpdk-testsuite.dir/020/dpdkvhostclient0) free 
connfd 50
netdev_dpdk|INFO|vHost Device 
'/tmpdir/_debian/tests/system-dpdk-testsuite.dir/020/dpdkvhostclient0' not found
 ovs-vsctl del-br br10
 ovs-vsctl show
 # should show an empty switch


^^ Here I expected the issue with the new code (OVS + DPDK being new).
But sadly I have proven that the "not found" on the path was a red herring as 
well.
It comes up in the good path as well.
The good case just does not push the log output to the test-output.
Hence it seemed to be an issue "only in the bad case" but that was a fluke.

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

Again, is that the root cause or a symptom of a former failure?
Not all tests are very clear in that regard, but one I liked.
As it fails BEFORE this cleanup phase.

The "MTU upper bound vport port" test is like this:

> 2024-05-31T10:08:28.364Z|00117|netdev_dpdk|WARN|dpdkvhostuserclient0: 
> unsupported MTU 9711
> 2024-05-31T10:08:28.364Z|00118|netdev|WARN|failed to set MTU for network 
> device dpdkvhostuserclient0: Invalid argument
> 2024-05-31T10:08:28.374Z|00119|bridge|INFO|bridge br10: deleted interface 
> dpdkvhostuserclient0 on port 1
> 2024-05-31T10:08:28.374Z|00120|dpif_netdev|INFO|PMD thread on numa_id: 0, 
> core id:  3 destroyed.
> 2024-05-31T10:08:28.374Z|2|dpdk(pmd-c03/id:10)|INFO|PMD thread released 
> DPDK lcore 1.
> 2024-05-31T10:08:28.375Z|00121|dpdk|INFO|VHOST_CONFIG: 
> (/tmpdir/_debian/tests/system-dpdk-testsuite.dir/020/dpdkvhostclient0) free 
> connfd 52
> 2024-05-31T10:08:28.375Z|00122|netdev_dpdk|INFO|vHost Device 
> '/tmpdir/_debian/tests/system-dpdk-testsuite.dir/020/dpdkvhostclient0' not 
> found
tests/system-dpdk-testsuite: line 1754: 275858 Killed  
dpdk-testpmd $eal_options -- $testpmd_options > testpmd.log 2>&1
20. system-dpdk.at:736: 20. OVS-DPDK - MTU upper bound vport port 
(system-dpdk.at:736): FAILED (system-dpdk.at:767)

But this is a red-herring, as the setting of this is meant to fail.
The test says:
  "Set MTU value above upper bound and check for error"

So it might indeed be the cleanup that fails?

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

After that one knows which sub-log to check, for ease of consumption
I've attached the subsection here that talks about the actually failing tests.

Fail #1
/tmpdir/_debian/tests/system-dpdk-testsuite.dir/004/cleanup: line 1: kill: 
(275003) - No such process
4. system-dpdk.at:102: 4. OVS-DPDK - ping vhost-user ports 
(system-dpdk.at:102): FAILED (system-dpdk.at:148)

Fail #2
> 2024-05-31T10:08:11.896Z|00087|dpdk|INFO|VHOST_CONFIG: 
> (/tmpdir/_debian/tests/system-dpdk-testsuite.dir/005/dpdkvhostclient0) free 
> connfd 52
> 2024-05-31T10:08:11.896Z|00088|netdev_dpdk|INFO|vHost Device 
> '/tmpdir/_debian/tests/system-dpdk-testsuite.dir/005/dpdkvhostclient0' not 
> found
tests/system-dpdk-testsuite: line 1754: 275274 Killed  
dpdk-testpmd $eal_options -- $testpmd_options > testpmd.log 2>&1
5. system-dpdk.at:158: 5. OVS-DPDK - ping vhost-user-client ports 
(system-dpdk.at:158): FAILED (system-dpdk.at:224)

Fail #3
> 2024-05-31T10:08:17.179Z|00120|dpdk|INFO|VHOST_CONFIG: 
> (/tmpdir/_debian/tests/system-dpdk-testsuite.dir/016/dpdkvhostclient0) free 
> connfd 52
> 2024-05-31T10:08:17.179Z|00121|netdev_dpdk|INFO|vHost Device 
> '/tmpdir/_debian/tests/system-dpdk-testsuite.dir/016/dpdkvhostclient0' not 
> found
tests/system-dpdk-testsuite: line 1754: 275495 Killed  
dpdk-testpmd $eal_options -- $testpmd_options > testpmd.log 2>&1
16. system-dpdk.at:577: 16. OVS-DPDK - MTU increase vport port 
(system-dpdk.at:577): FAILED (system-dpdk.at:609)

Fail #4
> 2024-05-31T10:08:22.436Z|00079|dpdk|INFO|VHOST_CONFIG: 
> (/tmpdir/_debian/tests/system-dpdk-testsuite.dir/017/dpdkvhostclient0) free 
> connfd 52
> 2024-05-31T10:08:22.436Z|00080|netdev_dpdk|INFO|vHost Device 
> '/tmpdir/_debian/tests/system-dpdk-testsuite.dir/017/dpdkvhostclient0' not 
> found
tests/system-dpdk-testsuite: line 1767: 275658 Killed  
dpdk-testpmd $eal_options -- $testpmd_options > testpmd.log 2>&1
17. system-dpdk.at:618: 17. OVS-DPDK - MTU decrease vport port 
(system-dpdk.at:618): FAILED (system-dpdk.at:651)

Fail #5
> 2024-05-31T10:08:28.375Z|00121|dpdk|INFO|VHOST_CONFIG: 
> (/tmpdir/_debian/tests/system-dpdk-testsuite.dir/020/dpdkvhostclient0) free 
> connfd 52
> 2024-05-31T10:08:28.375Z|00122|netdev_dpdk|INFO|vHost Device 
> '/tmpdir/_debian/tests/system-dpdk-testsuite.dir/020/dpdkvhostclient0' not 
> found
tests/system-dpdk-testsuite: line 1754: 275858 Killed  
dpdk-testpmd $eal_options -- $testpmd_options > testpmd.log 2>&1
20. system-dpdk.at:736: 20. OVS-DPDK - MTU upper bound vport port 
(system-dpdk.at:736): FAILED (system-dpdk.at:767)

Fail #6
> 2024-05-31T10:08:32.113Z|00079|dpdk|INFO|VHOST_CONFIG: 
> (/tmpdir/_debian/tests/system-dpdk-testsuite.dir/021/dpdkvhostclient0) free 
> connfd 52
> 2024-05-31T10:08:32.113Z|00080|netdev_dpdk|INFO|vHost Device 
> '/tmpdir/_debian/tests/system-dpdk-testsuite.dir/021/dpdkvhostclient0' not 
> found
tests/system-dpdk-testsuite: line 1767: 276061 Killed  
dpdk-testpmd $eal_options -- $testpmd_options > testpmd.log 2>&1
21. system-dpdk.at:778: 21. OVS-DPDK - MTU lower bound vport port 
(system-dpdk.at:778): FAILED (system-dpdk.at:809)

They seem to all stumble over some cleanup.
The question now is if that is a symptom (something before goes wrong, and then
we see the cleanup path go nuts). Or if it is the root cause (it always cleaned
up, but now it no more works).


It seems the sequence here is always to the end of the actual tests.
There it deletes interfaces, but then breaks on the associated file not 
existing.
But is that really the issue that changed?

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

One has to realize, even the good path hits the cleanup function, but entered
with rc=0. It then cleans up and exits with the RC it got.

The bad case OTOH seems to do parts of the cleanup function, but not all of it.
It ends the tests, with more successful tests (151) but then enters cleanup
with a bad RC.

Note:
There is also an autopkgtest/nova issue in the bad log:
5063s /home/ubuntu/autopkgtest/ssh-setup/nova: 234: [: x86_64: unexpected 
operator
5063s /home/ubuntu/autopkgtest/ssh-setup/nova: 237: [: x86_64: unexpected 
operator
But myself and bryce think this is an orthogonal issue.

Diving into the log a bit deeper made me find:

4: OVS-DPDK - ping vhost-user portsFAILED (system-dpdk.at:148)
5: OVS-DPDK - ping vhost-user-client ports FAILED (system-dpdk.at:224)
16: OVS-DPDK - MTU increase vport port  FAILED (system-dpdk.at:609)
17: OVS-DPDK - MTU decrease vport port  FAILED (system-dpdk.at:651)
20: OVS-DPDK - MTU upper bound vport port   FAILED (system-dpdk.at:767)
21: OVS-DPDK - MTU lower bound vport port   FAILED (system-dpdk.at:809)

The partial confusion is from the test running multiple suites:
=> openvswitch-afxdp-testsuite Good 136 skip 39
=> system-dpdk-testsuite Good 142 skip 49 Fail 6
=> system-userspace-testsuite Good 151 skip 36
=> system-offloads-testsuite Good 152 skip 33

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] Re: DPDK 23.11.1 / OVS 3.3.0 cause test failures

Oracular OVS bad test with DPDK 23.11.1-1
https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/amd64/o/openvswitch/20240531_100906_6f957@/log.gz

5047s 151 tests were successful.
5047s 36 tests were skipped.
5047s + update-alternatives --set ovs-vswitchd 
/usr/lib/openvswitch-switch/ovs-vswitchd
5047s update-alternatives: using /usr/lib/openvswitch-switch/ovs-vswitchd to 
provide /usr/sbin/ovs-vswitchd (ovs-vswitchd) in manual mode
5047s /tmp/autopkgtest.62SGkT/build.KmH/src
5047s + dirs +1
5047s + popd
5047s + umount /UZ4
5047s + rmdir /UZ4
5047s + exit 1


Oracular OVS good test with DPDK 23.11-1
https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/amd64/o/openvswitch/20240529_111623_6f8db@/log.gz

4957s 148 tests were successful.
4957s 49 tests were skipped.
4957s + cleanup
4957s + rc=0
4957s + set +e
4957s + '[' 0 -ne 0 ']'
4957s + '[' -L /usr/bin/nc ']'
4957s + rm -f /usr/bin/nc
4957s + '[' dpdk = dpdk ']'
4957s + mv /etc/dpdk/dpdk.conf.bak /etc/dpdk/dpdk.conf
4957s + systemctl restart dpdk
4957s + update-alternatives --set ovs-vswitchd 
/usr/lib/openvswitch-switch/ovs-vswitchd
4957s update-alternatives: using /usr/lib/openvswitch-switch/ovs-vswitchd to 
provide /usr/sbin/ovs-vswitchd (ovs-vswitchd) in manual mode
4957s /tmp/autopkgtest.vQL7uJ/build.4Ev/src
4957s + dirs +1
4957s + popd
4957s + umount /S31
4957s + rmdir /S31
4957s + exit 0

The arches that worked are no counter to that:
 dpdk SKIP exit status 77 and marked as skippable

Theory, legit issue with the new DPDK breaking the OVS testcase

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

Title:
  DPDK 23.11.1 / OVS 3.3.0 cause test failures

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


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

[Bug 2067889] [NEW] DPDK 23.11.1 / OVS 3.3.0 cause test failures