[Bug 1892275] Re: [sync][sru] sos upstream 4.0
[VERIFICATION FOCAL]
[sos report (new main binary) / sosreport (former binary name)]
Work as usual. It has been tested with simple.sh script, which runs
various/several sos scenarios/arguments/...).
[sos clean]
Obfuscation works as expect.
Take a bit of time to complete, but nothing preventing the release of
the package for now, spending most of its time at obfuscating data.
Verification includes:
- Ipv4 address/network obfuscation : OK
3: wlp58s0inet 100.0.0.1/24 brd 100.0.0.255 scope global dynamic
noprefixroute wlp58s0\ obfuscatedword0 7000
8sec preferred_lft 70008sec
#mapping file:
"ip_map": {
...
"10.10.30.123/24": "100.0.0.1/24",
...
}
- Host name, and domain name obfuscation: OK
$ cat path_to_obfuscated_sosreport/hostname
host0
$ cat path_to_obfuscated_sosreport/var/log/*
Aug 28 08:57:14 host0 kernel: [ 472.635702] usb usb3: New USB device strings:
Mfr=3, Product=2, SerialNumber=1
Aug 28 08:57:14 host0 kernel: [ 472.635710] usb usb3: Product: xHCI Host
Controller
# mapping file:
"hostname_map": {
"thinkpad": "host0"
- User-provided keyword obfuscations: OK
3: wlp58s0inet 100.0.0.1/24 brd 100.0.0.255 scope global dynamic
noprefixroute wlp58s0\ obfuscatedword0 7000
8sec preferred_lft 70008sec
#mapping file:
"keyword_map": {
"valid_lft": "obfuscatedword0"
}
[sos collect & sos mask (alias)]
sos collector has been tested using SSH key authorization
No problem reported, and it works as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892275
Title:
[sync][sru] sos upstream 4.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
I would like to see testing and feedbacks from others now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync][sru] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
[VERIFICATION FOCAL] [PART 2] No ERROR nor WARNING found during my testing on container, VM and physical machine (laptop/workstation) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync][sru] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
** Changed in: sosreport (Ubuntu Bionic) Status: New => In Progress ** Changed in: sosreport (Ubuntu Bionic) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: sosreport (Ubuntu Xenial) Status: New => In Progress ** Changed in: sosreport (Ubuntu Xenial) Assignee: (unassigned) => Eric Desrochers (slashd) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync][sru] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1874662] Re: Corrupted installation medium
Reimiging the install media worked for me. Other than that, I regret my lack of knowledge. Good luck, and please stay safe. On Thu, Aug 27, 2020, 3:20 PM Arpit Kumar <1874...@bugs.launchpad.net> wrote: > how to fix this bug? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1891170). > https://bugs.launchpad.net/bugs/1874662 > > Title: > Corrupted installation medium > > Status in Ubuntu: > Fix Released > > Bug description: > > If you have been redirected to this page, it means that your > installation of Ubuntu or a flavour failed. > > If you search in the log file /var/log/syslog, you'll see messages > like above: > > Apr 24 00:01:40 ubuntu kernel: [ 329.409695] SQUASHFS error: zlib > decompression failed, data probably corrupt > Apr 24 00:01:40 ubuntu kernel: [ 329.409704] SQUASHFS error: > squashfs_read_data failed to read block 0x37545 > > This failure is usually caused by bad ISO download, corrupted install > media, or device failure. > > We suggest you verify your ISO download, your installation medium or > use another USB stick. > > You may also find useful information in this tutorial: > https://tutorials.ubuntu.com/tutorial/tutorial-how-to-verify-ubuntu > > If you experienced an issue during installation and think it is not > caused by a corrupted installation media, do not hesitate to report a > bug by running the following command from a terminal: > > $ ubuntu-bug ubiquity > > Thanks for using Ubuntu. > > > [Do not close or re-assign this report] > [It's used to help users using faulty USB sticks] > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+bug/1874662/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874662 Title: Corrupted installation medium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1874662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
** Description changed: [Impact] The sos team is pleased to announce the release of sos-4.0. This is a major version release that represents a significant change to the sos project, new features, and bug fixes. https://github.com/sosreport/sos/releases/tag/4.0 [Test Case] * Install sosreport 4.0-1* package ** Test new main binary 'sos' and it's former binary still present 'sosreport' (e.g. sosreport -a --all-logs & sos report -a --all-logs) ** Test new features: *** sos-collect (Collect sosreport from multiple node simultaneously) *** sos-clean || sos-mask (It's aim is to scrub potentially sensitive information from sosreports in a consistent manner, beyond the obfuscation done by plugins already.) Replacement of the former project called 'soscleaner' which no longer deliver development. [Regression Potential] Main binary formerly known as 'sosreport' has been officially renamed to 'sos' but 'sosreport' still exist and has been carried over for now to help to transition for package maintainer. No impact nor behavioural change for existing user. They are welcome to use the new binary or the former one as they wish. -rwxr-xr-x 1 root root 1057 Aug 25 16:24 /usr/bin/sosreport -rwxr-xr-x 1 root root 596 Aug 25 16:24 /usr/bin/sos New functionalities has been added which could lead to possible bugs ,since they are fairly new addition, if not already caught by the travis/autopkg tests but if a problem arise it will be limited to the components itself and won't affect the main behaviour (which by the way remain the same, which is to collect a tarball using 'sosreport' or/and now 'sos report' subcommand. To resume, main known existing behaviour remain the same but some new features which are limited/independent to each other has been added to offer new features such as : * sos collect is a new sub command in this release, and is an integration of the standalone sos-collector project, with the aim being to collect sosreports from multiple systems simultaneously. Note that this sub-command requires python3-pexpect to be available. If the module is not available, sos collect will abort with an appropriate error message * sos clean, also available as sos mask, is a newly added sub-command in this release and is an implementation of the standalone soscleaner project. Its aim is to scrub potentially sensitive information from sosreports in a consistent manner, beyond the obfuscation done by plugins already. https://wiki.ubuntu.com/SosreportUpdates sos4.0 now enforces archives to be stored in /var/tmp. A debian patch has been made to continue to store in /tmp (current behaviour) to stay align with current behaviour but also because debian's systemd implementation doesn't provide a tmpfiles.d cleaner for /var/tmp. So /tmp remains the default "tmp-dir" location. During the testing, I found a py38 incompatibility related to dictionnary order, that I fixed upstream and cherry-pick for Ubuntu release having py38 found in : d/p/0002-fix-dict-order- py38-incompatibility.patch. Upstream commit: https://github.com/sosreport/sos/pull/2207/commits/86dfd99931ac0199895cf5e41711fc9b1ab6feaf + + The old config (/etc/sos.conf) contents will not be carried over after + update, and that people will have to modify the new file + (/etc/sos/sos.conf) instead. [Other Information] https://github.com/sosreport/sos/releases/tag/4.0 [Original Description] https://github.com/sosreport/sos/releases/tag/4.0 Major changes Sos has been redesigned to provide functionality beyond the well known report data collection usage. It has been updated to provide more functionality via sub-commands. A new sos binary has replaced the former sosreport binary as the main entry point for the utility. sos report is now used to generate sosreport tarballs. A sosreport binary is maintained as a redirection point and will now invoke sos report. sos collect formally brings sos-collector into the main sos project, and is used to collect sosreports from multiple nodes simultaneously. A sos-collector binary is maintained as a redirection point and will invoke sos collect. This means the standalone sos-collector utility will no longer be independently developed. sos clean formally brings soscleaner-like functionality into the main sos project. This sub command will perform further data obfuscation on reports, such as scrubbing IP addresses, domain names, and user-provided keywords. See below for more information. /etc/sos.conf has been moved to /etc/sos/sos.conf, and the layout of the config file has changed: The general section has been renamed to global, and may be used to specify options that are available to all sos commands and sub-commands. Each sub-command will have its own section, e.g. sos report will load options from global and from report. Sos is
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
Considering that "sos report" (AKA soreport) doesn't have any feature/behavioural breaks (just usual plugins update/addition/...), and that 4.X focuses more on addition such as "sos clean" and "sos collect", I start to think it's not worth the maintenance of 2 splitting things out. After a discussion with sil2100 (to get a neutral opinion) he agreed with the above statement. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync][sru] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
As discussed the above proposal might require a meta package call 'sosreport4' in Groovy to ease the upgrade path. Again let's wait for a Ubuntu archive admin to look at this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync][sru] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
That's also going to involve more package work: * Does sosreport and sosreport4 needs to break/conflict ? or can co-exist ? I think it would make more sense to have one or the other. * Make sure sosreport and sosreport4 follow the same upgrade path if one upgrade from focal to groovy. Note that groovy only has sosreport package which default to 4.0 To summarise the idea: Groovy (Currently in place as we speak): - binary package name: sosreport | upstream version: 4.0 Focal (arif-ali proposal): - binary package name: sosreport | upstream version: 3.0 - binary package name: sosreport4 | upstream version: 4.0 Bionic (arif-ali proposal): - binary package name: sosreport | upstream version: 3.0 - binary package name: sosreport4 | upstream version: 4.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync][sru] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
@arif-ali, I like the idea. Let me talk with an Ubuntu archive admin. Most likely sosreport4 would have to go in universe at first and then go over the MIR process if need be. I also like to have sosreport4 in Universe and sosreport in Main, since sosreport4 is still experimental ish. Let's see what an Admin Archive think of that first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync][sru] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
sosreport4 would also have to Conflicts with sosreport and vice versa since they share same file and binaries name/location. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync][sru] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
@arif-ali, I like the idea. @arif-ali, I like the idea. Let me talk with a Ubuntu archive admin. Most likely sosreport4 would have to go in universe at first and then go over the MIR process if we go that route. Let me talk with an Ubuntu archive admin. Most likely sosreport4 would have to go in universe at first and then go over the MIR process if need be. I also like to have sosreport4 in Universe and sosreport in main. Let's see what an Admin Archive think of that first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync][sru] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
I think we could go that route starting focal and downward, but groovy would have sosreport only which would be 4.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync][sru] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
@arif-ali, I like the idea. Let me talk with a Ubuntu archive admin. Most likely sosreport4 would have to go in universe at first and then go over the MIR process if we go that route. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync][sru] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
"4.0-1~ubuntu0.20.04.1" has been uploaded in the focal upload queue, waiting for approval to start building in focal-proposed where more verification will happen across Canonical support team. - Eric ** Also affects: sosreport (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Xenial) Importance: Undecided Status: New ** Description changed: [Impact] - The sos team is pleased to announce the relase of sos-4.0. This is a major version release that represents a significant change to the sos project, new features, and bug fixes. + The sos team is pleased to announce the release of sos-4.0. This is a major version release that represents a significant change to the sos project, new features, and bug fixes. https://github.com/sosreport/sos/releases/tag/4.0 [Test Case] * Install sosreport 4.0-1* package ** Test new main binary 'sos' and it's former binary still present 'sosreport' (e.g. sosreport -a --all-logs & sos report -a --all-logs) ** Test new features: *** sos-collect (Collect sosreport from multiple node simultaneously) *** sos-clean || sos-mask (It's aim is to scrub potentially sensitive information from sosreports in a consistent manner, beyond the obfuscation done by plugins already.) Replacement of the former project called 'soscleaner' which no longer deliver development. [Regression Potential] Main binary formerly known as 'sosreport' has been officially renamed to 'sos' but 'sosreport' still exist and has been carried over for now to help to transition for package maintainer. No impact nor behavioural change for existing user. They are welcome to use the new binary or the former one as they wish. -rwxr-xr-x 1 root root 1057 Aug 25 16:24 /usr/bin/sosreport -rwxr-xr-x 1 root root 596 Aug 25 16:24 /usr/bin/sos New functionalities has been added which could lead to possible bugs ,since they are fairly new addition, if not already caught by the travis/autopkg tests but if a problem arise it will be limited to the components itself and won't affect the main behaviour (which by the way remain the same, which is to collect a tarball using 'sosreport' or/and now 'sos report' subcommand. To resume, main known existing behaviour remain the same but some new features which are limited/independent to each other has been added to offer new features such as : * sos collect is a new sub command in this release, and is an integration of the standalone sos-collector project, with the aim being to collect sosreports from multiple systems simultaneously. Note that this sub-command requires python3-pexpect to be available. If the module is not available, sos collect will abort with an appropriate error message * sos clean, also available as sos mask, is a newly added sub-command in this release and is an implementation of the standalone soscleaner project. Its aim is to scrub potentially sensitive information from sosreports in a consistent manner, beyond the obfuscation done by plugins already. https://wiki.ubuntu.com/SosreportUpdates sos4.0 now enforces archives to be stored in /var/tmp. A debian patch has been made to continue to store in /tmp (current behaviour) to stay align with current behaviour but also because debian's systemd implementation doesn't provide a tmpfiles.d cleaner for /var/tmp. So /tmp remains the default "tmp-dir" location. [Other Information] https://github.com/sosreport/sos/releases/tag/4.0 [Original Description] https://github.com/sosreport/sos/releases/tag/4.0 Major changes Sos has been redesigned to provide functionality beyond the well known report data collection usage. It has been updated to provide more functionality via sub-commands. A new sos binary has replaced the former sosreport binary as the main entry point for the utility. sos report is now used to generate sosreport tarballs. A sosreport binary is maintained as a redirection point and will now invoke sos report. sos collect formally brings sos-collector into the main sos project, and is used to collect sosreports from multiple nodes simultaneously. A sos-collector binary is maintained as a redirection point and will invoke sos collect. This means the standalone sos-collector utility will no longer be independently developed. sos clean formally brings soscleaner-like functionality into the main sos project. This sub command will perform further data obfuscation on reports, such as scrubbing IP addresses, domain names, and user-provided keywords. See below for more information. /etc/sos.conf has been moved to /etc/sos/sos.conf, and the layout of the config file has changed: The general section has been renamed to global, and may be used to specify options that are available to all sos commands and sub-commands. Each sub-command will have its own
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
** Description changed: [Impact] The sos team is pleased to announce the relase of sos-4.0. This is a major version release that represents a significant change to the sos project, new features, and bug fixes. https://github.com/sosreport/sos/releases/tag/4.0 [Test Case] * Install sosreport 4.0-1* package ** Test new main binary 'sos' and it's former binary still present 'sosreport' (e.g. sosreport -a --all-logs & sos report -a --all-logs) ** Test new features: *** sos-collect (Collect sosreport from multiple node simultaneously) *** sos-clean || sos-mask (It's aim is to scrub potentially sensitive information from sosreports in a consistent manner, beyond the obfuscation done by plugins already.) Replacement of the former project called 'soscleaner' which no longer deliver development. [Regression Potential] Main binary formerly known as 'sosreport' has been officially renamed to 'sos' but 'sosreport' still exist and has been carried over for now to help to transition for package maintainer. No impact nor behavioural change for existing user. They are welcome to use the new binary or the former one as they wish. - New functionalities has been added which could lead to possible bugs - ,since they are fairly new addition, not caught by the travis/autopkg - tests but if a problem arise it will be limited to the components itself - and won't affect the main behaviour (which by the way remain the same, - which is to collect a tarball using 'sosreport' or/and now 'sos report' - subcommand. + -rwxr-xr-x 1 root root 1057 Aug 25 16:24 /usr/bin/sosreport + -rwxr-xr-x 1 root root 596 Aug 25 16:24 /usr/bin/sos + + + New functionalities has been added which could lead to possible bugs ,since they are fairly new addition, if not already caught by the travis/autopkg tests but if a problem arise it will be limited to the components itself and won't affect the main behaviour (which by the way remain the same, which is to collect a tarball using 'sosreport' or/and now 'sos report' subcommand. To resume, main known existing behaviour remain the same but some new features which are limited/independent to each other has been added to offer new features such as : * sos collect is a new sub command in this release, and is an integration of the standalone sos-collector project, with the aim being to collect sosreports from multiple systems simultaneously. Note that this sub-command requires python3-pexpect to be available. If the module is not available, sos collect will abort with an appropriate error message * sos clean, also available as sos mask, is a newly added sub-command in this release and is an implementation of the standalone soscleaner project. Its aim is to scrub potentially sensitive information from sosreports in a consistent manner, beyond the obfuscation done by plugins already. https://wiki.ubuntu.com/SosreportUpdates [Other Information] https://github.com/sosreport/sos/releases/tag/4.0 [Original Description] https://github.com/sosreport/sos/releases/tag/4.0 Major changes Sos has been redesigned to provide functionality beyond the well known report data collection usage. It has been updated to provide more functionality via sub-commands. A new sos binary has replaced the former sosreport binary as the main entry point for the utility. sos report is now used to generate sosreport tarballs. A sosreport binary is maintained as a redirection point and will now invoke sos report. sos collect formally brings sos-collector into the main sos project, and is used to collect sosreports from multiple nodes simultaneously. A sos-collector binary is maintained as a redirection point and will invoke sos collect. This means the standalone sos-collector utility will no longer be independently developed. sos clean formally brings soscleaner-like functionality into the main sos project. This sub command will perform further data obfuscation on reports, such as scrubbing IP addresses, domain names, and user-provided keywords. See below for more information. /etc/sos.conf has been moved to /etc/sos/sos.conf, and the layout of the config file has changed: The general section has been renamed to global, and may be used to specify options that are available to all sos commands and sub-commands. Each sub-command will have its own section, e.g. sos report will load options from global and from report. Sos is now a Python3-only utility. Python2 is no longer supported in any capacity. Dropped use of make, building/installing sos from source should now exclusively be done via setuptools Report sos will now generate metadata and save it in sos_reports/manifest.json. 7 new plugins: nvmetcli, drbd, openstack_designate, pmem, containers_common, hyperv, freeipmi The nfsserver plugin has been merged into the nfs plugin sos may now be
[Bug 1892275] Re: [sync][sru] sos upstream 4.0
** Description changed: + [Impact] + + [Test Case] + * Install sosreport 4.0-1* package + ** Test new main binary 'sos' and it's former binary still present 'sosreport' (e.g. sosreport -a --all-logs & sos report -a --all-logs) + ** Test new features: + *** sos-collect (Collect sosreport from multiple node simultaneously) + *** sos-clean || sos-mask (It's aim is to scrub potentially sensitive information from sosreports in a consistent manner, beyond the obfuscation done by plugins already.) Replacement to former project called 'soscleaner'. + + [Regression Potential] + + Main binary formerly known as 'sosreport' has been officially renamed to + 'sos' but 'sosreport' still exist and has been carried over for now to + help to transition for package maintainer. No impact nor behavioural + change for existing user. They are welcome to use the new binary or the + former one as they wish. + + New functionalities has been added which could lead to possible bugs + ,since they are fairly new addition, not caught by the travis/autopkg + tests but if a problem arise it will be limited to the components itself + and won't affect the main behaviour (which by the way remain the same, + which is to collect a tarball using 'sosreport' or/and now 'sos report' + subcommand. + + To resume, main known existing behaviour remain the same but some new + features which are limited/independent to each other has been added to + offer new features such as : + + * sos collect is a new sub command in this release, and is an + integration of the standalone sos-collector project, with the aim being + to collect sosreports from multiple systems simultaneously. Note that + this sub-command requires python3-pexpect to be available. If the module + is not available, sos collect will abort with an appropriate error + message + + * sos clean, also available as sos mask, is a newly added sub-command in + this release and is an implementation of the standalone soscleaner + project. Its aim is to scrub potentially sensitive information from + sosreports in a consistent manner, beyond the obfuscation done by + plugins already. + + https://wiki.ubuntu.com/SosreportUpdates + + [Other Information] + + [Original Description] https://github.com/sosreport/sos/releases/tag/4.0 Major changes Sos has been redesigned to provide functionality beyond the well known report data collection usage. It has been updated to provide more functionality via sub-commands. A new sos binary has replaced the former sosreport binary as the main entry point for the utility. sos report is now used to generate sosreport tarballs. A sosreport binary is maintained as a redirection point and will now invoke sos report. sos collect formally brings sos-collector into the main sos project, and is used to collect sosreports from multiple nodes simultaneously. A sos-collector binary is maintained as a redirection point and will invoke sos collect. This means the standalone sos-collector utility will no longer be independently developed. sos clean formally brings soscleaner-like functionality into the main sos project. This sub command will perform further data obfuscation on reports, such as scrubbing IP addresses, domain names, and user-provided keywords. See below for more information. /etc/sos.conf has been moved to /etc/sos/sos.conf, and the layout of the config file has changed: The general section has been renamed to global, and may be used to specify options that are available to all sos commands and sub-commands. Each sub-command will have its own section, e.g. sos report will load options from global and from report. Sos is now a Python3-only utility. Python2 is no longer supported in any capacity. Dropped use of make, building/installing sos from source should now exclusively be done via setuptools Report sos will now generate metadata and save it in sos_reports/manifest.json. 7 new plugins: nvmetcli, drbd, openstack_designate, pmem, containers_common, hyperv, freeipmi The nfsserver plugin has been merged into the nfs plugin sos may now be used to collect data from within a container, rather than aborting if that container was not configured to allow sos to collect information from the host Added support for Container-Optimized OS (COS) Dropped Mac OSX support Dropped bzip2 compression support Users may now use the --clean or --mask option to process a report- being-generated through sos clean at runtime. Size limits will now apply to add_copy_spec() calls that target a directory The openshift plugin has been re-written to be used for Openshift Container Platform 4 Significantly expanded the amount of API resources the openstack_octavia plugin will collect The networking plugin will no longer execute ethtool -e against NICs using the bnx2x driver The logs plugin will now capture journal information correctly
[Bug 1892275] Re: [sync] sos upstream 4.0
** Also affects: sosreport (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: sosreport (Ubuntu Focal) Status: New => In Progress ** Changed in: sosreport (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Focal) Assignee: (unassigned) => Eric Desrochers (slashd) ** Summary changed: - [sync] sos upstream 4.0 + [sync][sru] sos upstream 4.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync][sru] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: [sync] sos upstream 4.0
This bug was fixed in the package sosreport - 4.0-1 Sponsored for Eric Desrochers (slashd) --- sosreport (4.0-1) unstable; urgency=medium * New 4.0 upstream release. Release information and tarballs are available at: - https://github.com/sosreport/sos/releases/tag/4.0 * Other specific modifications: - d/p/0001-debian-change-tmp-dir-location.patch - d/p/0002-fix-dict-order-py38-incompatiblity.patch * d/control: Maintainer change from Louis to Eric. -- Eric Desrochers Wed, 19 Aug 2020 22:49:24 + ** Changed in: sosreport (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892242] Re: Curtin doesn't handle type:mount entries without 'path' element
@Richard @Ryan, Thanks, much appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892242 Title: Curtin doesn't handle type:mount entries without 'path' element To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1892242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892242] Re: Curtin doesn't handle type:mount entries without 'path' element
@ryan, Are you planning to SRU it ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892242 Title: Curtin doesn't handle type:mount entries without 'path' element To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1892242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892242] Re: Curtin doesn't handle type:mount entries without 'path' element
** Also affects: curtin (Ubuntu) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Bionic) 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/1892242 Title: Curtin doesn't handle type:mount entries without 'path' element To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1892242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: sync | sos upstream 4.0
** Summary changed: - upstream 4.0 is out + sync | sos upstream 4.0 ** Summary changed: - sync | sos upstream 4.0 + [sync] sos upstream 4.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: [sync] sos upstream 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: upstream 4.0 is out
During the Debian packaging, I found a bug that I fixed in: https://github.com/sosreport/sos/commit/1d7bab6c7ce3f78758113ca3cdf3e9fa1762df24 I also divert from upstream by instructing sos.conf to save sosreport contents into /tmp instead of now enforce location /var/tmp in order to keep same behaviour and no tmpfiles.d systemd implementation is in place at the moment for /var/tmp. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: upstream 4.0 is out To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] Re: upstream 4.0 is out
During the Debian packaging, I found a bug that I fixed in: https://github.com/sosreport/sos/commit/1d7bab6c7ce3f78758113ca3cdf3e9fa1762df24 I also divert from upstream by instructing sos.conf to save sosreport contents into /tmp instead of now enforce location /var/tmp in order to keep same behaviour and because no tmpfiles.d cleanup directive in Debian's systemd implementation is in place at the moment for /var/tmp. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: upstream 4.0 is out To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892275] [NEW] upstream 4.0 is out
to preserve topological relationships between discovered addresses Support for hostname, and domain name obfuscation. Support for user-provided keyword obfuscations Users may either use the --clean or --mask flag to sos report to obfuscate a report being generated, or may use sos (clean|mask) $archive to obfuscate an already existing report. Using the former will result in a single obfuscated report archive, while the latter approach will result in two; an obfuscated archive and the un-obfuscated original. For full information on the changes contained in this release, please refer to the Git commit logs. Further release information and tarballs are available at: https://github.com/sosreport/sos/releases/tag/4.0 Please report any problems to the sos-devel mailing list, or the GitHub issue tracker: https://github.com/sosreport/sos/issues/ The team would like to thank everyone who contributed fixes, new features, testing, and feedback for this release. ** Affects: sosreport Importance: Unknown Status: Unknown ** Affects: sosreport (Ubuntu) Importance: Medium Assignee: Eric Desrochers (slashd) Status: In Progress ** Tags: seg sts ** Tags added: seg sts ** Bug watch added: Debian Bug tracker #968690 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968690 ** Also affects: sosreport via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968690 Importance: Unknown Status: Unknown ** Changed in: sosreport (Ubuntu) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: sosreport (Ubuntu) Status: New => In Progress ** Changed in: sosreport (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892275 Title: upstream 4.0 is out To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1892275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892028] [NEW] Impossible to upgrade to 20.04 lts from 18.04
Public bug reported: Probably error in cache: 2020-08-18 13:59:05,049 DEBUG running doUpdate() (showErrors=False) 2020-08-18 13:59:15,107 ERROR IOError/SystemError in cache.update(): ''. Retrying (currentRetry: 0) 2020-08-18 13:59:15,108 ERROR doUpdate() failed completely 2020-08-18 13:59:15,108 DEBUG openCache() ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME Date: Tue Aug 18 14:15:46 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2018-11-27 (629 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-08-18 (0 days ago) mtime.conffile..etc.update-manager.release-upgrades: 2020-08-18T09:56:03.859601 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892028 Title: Impossible to upgrade to 20.04 lts from 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1892028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890846] Re: add output of: rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().'
** Also affects: sosreport (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Groovy) Importance: Undecided Assignee: Nicolas Bock (nicolasbock) Status: New ** Also affects: sosreport (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: + [Impact] + + + [Test Case] + + + [Regression Potential] + + + [Other Info] + + [Original Description] Extend the rabbitmq plugin to include the output of: sudo rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().' This information is useful to get insights of the state of the erlang virtual machine. ** Description changed: [Impact] - [Test Case] - - [Regression Potential] - + [Regression Potential] [Other Info] [Original Description] + Extend the rabbitmq plugin to include the output of: sudo rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().' This information is useful to get insights of the state of the erlang virtual machine. ** Changed in: sosreport (Ubuntu Focal) Assignee: (unassigned) => Nicolas Bock (nicolasbock) ** Changed in: sosreport (Ubuntu Bionic) Assignee: (unassigned) => Nicolas Bock (nicolasbock) ** Changed in: sosreport (Ubuntu Xenial) Assignee: (unassigned) => Nicolas Bock (nicolasbock) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890846 Title: add output of: rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1890846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1874662] Re: Corrupted installation medium
I reimaged my install stick, then tried the installation (install USB -> destination USB) on a bigger and faster computer. It worked fine the second time. I made the first attempt on a repurposed Asus CR-16 Chromebook that had been upgraded to 8 Gb memory and 128 Gb SSD, and the second on an ASRock X99 Extreme based build (6 Core Intel server CPU, 64 Gb error correcting memory). Perhaps the install simply needed more memory, though I cannot see why. Thank you so much. -- Eric On Wed, Aug 12, 2020 at 8:31 AM MADUPOJU SANJAY KUMAR < 1874...@bugs.launchpad.net> wrote: > I'm unable to install > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1891170). > https://bugs.launchpad.net/bugs/1874662 > > Title: > Corrupted installation medium > > Status in Ubuntu: > Fix Released > > Bug description: > > If you have been redirected to this page, it means that your > installation of Ubuntu or a flavour failed. > > If you search in the log file /var/log/syslog, you'll see messages > like above: > > Apr 24 00:01:40 ubuntu kernel: [ 329.409695] SQUASHFS error: zlib > decompression failed, data probably corrupt > Apr 24 00:01:40 ubuntu kernel: [ 329.409704] SQUASHFS error: > squashfs_read_data failed to read block 0x37545 > > This failure is usually caused by bad ISO download, corrupted install > media, or device failure. > > We suggest you verify your ISO download, your installation medium or > use another USB stick. > > You may also find useful information in this tutorial: > https://tutorials.ubuntu.com/tutorial/tutorial-how-to-verify-ubuntu > > If you experienced an issue during installation and think it is not > caused by a corrupted installation media, do not hesitate to report a > bug by running the following command from a terminal: > > $ ubuntu-bug ubiquity > > Thanks for using Ubuntu. > > > [Do not close or re-assign this report] > [It's used to help users using faulty USB sticks] > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+bug/1874662/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874662 Title: Corrupted installation medium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1874662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
https://github.com/sshuttle/sshuttle/issues/503 ** Bug watch added: github.com/sshuttle/sshuttle/issues #503 https://github.com/sshuttle/sshuttle/issues/503 ** Also affects: sshuttle via https://github.com/sshuttle/sshuttle/issues/503 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873368 Title: ssshuttle server fails to connect endpoints with python 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/sshuttle/+bug/1873368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891170] [NEW] Disk I/O error from Install. Removed 40cdrom from install disk to correct last reported error. I have installed successfully from the thumbdrive.
Public bug reported: I have installed from this CD before, and everything went smoothly. The prior install was against an internal SSD. I am now installing on a USB stick, and had to remove /usr/lib/ubuquity /apt-setup/generators/40cdrom to fix a previous failure. (I actually moved the file under the home directory. I hope that didn't cause the problem.) I will reimage the installation stick, reformat the destination stick, and try again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 Date: Tue Aug 11 09:13:18 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu ** Attachment added: "partman" https://bugs.launchpad.net/bugs/1891170/+attachment/5400699/+files/partman -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891170 Title: Disk I/O error from Install. Removed 40cdrom from install disk to correct last reported error. I have installed successfully from the thumbdrive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1891170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658865] Re: Install from USB fails: "An attempt to configure apt to install additional packages from the CD failed"
Happened in 20.04 LTS as well. I have removed usr/lib/ubiquity/apt- setup/generators/40cdrom (actually created ~/RemovedFiles and saved it there) and will try again. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/658865 Title: Install from USB fails: "An attempt to configure apt to install additional packages from the CD failed" To manage notifications about this bug go to: https://bugs.launchpad.net/estobuntu/+bug/658865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890177] Re: rsyslogd: file '/dev/console': open error: Permission denied
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890177 Title: rsyslogd: file '/dev/console': open error: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890177] Re: rsyslogd: file '/dev/console': open error: Permission denied
@zack You could wait until the logrotate happen and restart rsyslog or you could simply do manual restart using 'systemctl restart rsyslog' and then look in /var/log/syslog. What triggers the error is at rsyslog startup from what I have notice during my test. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890177 Title: rsyslogd: file '/dev/console': open error: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890177] Re: rsyslogd: file '/dev/console': open error: Permission denied
@zack You could wait until the logrotate happen that will then restart rsyslog itself or you could simply do a manual restart using 'systemctl restart rsyslog' and then look in /var/log/syslog. What triggers the error is at rsyslog startup from what I have notice during my test. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890177 Title: rsyslogd: file '/dev/console': open error: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881976] Re: apport-gtk and apport-kde install xiterm+thai as dependency (x-terminal-emulator)
The apport (2.20.11-0ubuntu27.6) security channel build haven't been caught in that FTBFS situation because it was tested against the former pycodestyle package: Get:310 http://ftpmaster.internal/ubuntu focal/universe amd64 pycodestyle all 2.5.0-2 [5092 B] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881976 Title: apport-gtk and apport-kde install xiterm+thai as dependency (x -terminal-emulator) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1881976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881976] Re: apport-gtk and apport-kde install xiterm+thai as dependency (x-terminal-emulator)
[sts-sponsor note] Package doesn't build due to new pycodestyle (2.6.0-1~20.04.1) found in focal-proposed as opposed to its former version (2.5.0-2) that now detects the following during the test: Running pycodestyle... ./setup.py:78:33: E741 ambiguous variable name 'l' ./test/test_fileutils.py:380:13: E741 ambiguous variable name 'l' ./test/test_signal_crashes.py:141:13: E741 ambiguous variable name 'l' ./test/test_ui.py:1773:43: E741 ambiguous variable name 'l' ./backends/packaging-apt-dpkg.py:1222:13: E741 ambiguous variable name 'l' ./backends/packaging-apt-dpkg.py:1233:17: E741 ambiguous variable name 'l' ./build/lib/apport/__init__.py:67:13: E741 ambiguous variable name 'l' ./build/lib/apport/fileutils.py:332:9: E741 ambiguous variable name 'l' ./build/lib/apport/hookutils.py:620:9: E741 ambiguous variable name 'l' ./build/lib/apport/hookutils.py:630:9: E741 ambiguous variable name 'l' This has been addressed in apport groovy where ambiguous 'l' have been replaced by 'line'. # d/changelog apport (2.20.11-0ubuntu42) groovy; urgency=medium * Fix pep8 errors regarding ambiguous variables. -- Brian Murray Wed, 24 Jun 2020 09:15:51 -0700 Patch example: ... - for l in lines: - fd.write(l) + for line in lines: + fd.write(line) ... The same fix now need to be applied into focal for the package to start building again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881976 Title: apport-gtk and apport-kde install xiterm+thai as dependency (x -terminal-emulator) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1881976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881976] Re: apport-gtk and apport-kde install xiterm+thai as dependency (x-terminal-emulator)
[sts-sponsor note] Package doesn't build due to new pycodestyle (2.6.0-1~20.04.1) found in focal-proposed as opposed to its former version (2.5.0-2) that now detects the following during the test: Running pycodestyle... ./setup.py:78:33: E741 ambiguous variable name 'l' ./test/test_fileutils.py:380:13: E741 ambiguous variable name 'l' ./test/test_signal_crashes.py:141:13: E741 ambiguous variable name 'l' ./test/test_ui.py:1773:43: E741 ambiguous variable name 'l' ./backends/packaging-apt-dpkg.py:1222:13: E741 ambiguous variable name 'l' ./backends/packaging-apt-dpkg.py:1233:17: E741 ambiguous variable name 'l' ./build/lib/apport/__init__.py:67:13: E741 ambiguous variable name 'l' ./build/lib/apport/fileutils.py:332:9: E741 ambiguous variable name 'l' ./build/lib/apport/hookutils.py:620:9: E741 ambiguous variable name 'l' ./build/lib/apport/hookutils.py:630:9: E741 ambiguous variable name 'l' This has been addressed in apport groovy where ambiguous 'l' have been replaced by 'line'. # d/changelog apport (2.20.11-0ubuntu42) groovy; urgency=medium * Fix pep8 errors regarding ambiguous variables. -- Brian Murray Wed, 24 Jun 2020 09:15:51 -0700 Patch example: ... -for l in lines: -fd.write(l) +for line in lines: +fd.write(line) ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881976 Title: apport-gtk and apport-kde install xiterm+thai as dependency (x -terminal-emulator) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1881976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890177] Re: rsyslogd: file '/dev/console': open error: Permission denied
I have retry the test, it is failing on 'systemd-fsckd'. Let's see. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890177 Title: rsyslogd: file '/dev/console': open error: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890177] Re: rsyslogd: file '/dev/console': open error: Permission denied
I have retried the autpkgtest test on ppc64el. It is failing on 'systemd-fsckd'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890177 Title: rsyslogd: file '/dev/console': open error: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890177] Re: rsyslogd: file '/dev/console': open error: Permission denied
** Description changed: [Impact] At the moment rsyslog cannot have access /dev/console due to a mismatch permission/ownership between '/dev/console' and the Privilege Drop User and Group 'syslog' in rsyslog. [Test Case] - * Deploy focal/20.04LTS + * Deploy focal/20.04LTS (tested in gcloud instance) * Install rsyslog * systemctl restart rsyslog OR systemctl restart rsyslog * Inspect /var/log/syslog for the following error: syslog:Aug 4 14:37:56 rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ] [Regression potential] https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/comments/4 [Other information] Other bug: https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 [Original description] The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to 'syslog' for the user and group, and don't match the ownership/permission of '/dev/console' generating the following: syslog:Aug 3 15:16:58 rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ] Looking in Bionic/18.04LTS, '/dev/console' used to be root:syslog[1], nowadays it's root:tty[2] [1] - Bionic/18.04LTS (Gcloud instance) # ls -l /dev/console crw--w 1 root syslog 5, 1 Aug 3 15:17 /dev/console [2] - Focal/20.04LTS (Gcloud instance) # ls -l /dev/console crw--w 1 root tty 5, 1 Aug 3 17:19 /dev/console # /etc/rsyslog.conf $PrivDropToUser syslog $PrivDropToGroup syslog ** As a debug exercise I did the following: - Cannot reproduce the situation if I intentionally get rid of the PrivDrop* options. - Cannot reproduce the situation if I intentionally add 'syslog' user member of 'tty' group. Meaning that it's pretty obvious with the above statement that the permission denied is caused by the permission/ownership mismatch between '/dev/console' 's ownership permission & syslog user (PrivDropTo[User|Group]). Other bug: https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890177 Title: rsyslogd: file '/dev/console': open error: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890177] Re: rsyslogd: file '/dev/console': open error: Permission denied
Thanks @sil2100 for your pre-approval comment. I have uploaded it into focal upload queue. It is now waiting for the official SRU team approval in order to start building in focal-proposed for the verification test phase. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890177 Title: rsyslogd: file '/dev/console': open error: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890177] Re: rsyslogd: file '/dev/console': open error: Permission denied
** Description changed: + [Impact] + + At the moment rsyslog cannot have access /dev/console due to a mismatch + permission/ownership between '/dev/console' and the Privilege Drop User + and Group 'syslog' in rsyslog. + + [Test Case] + + * Deploy focal/20.04LTS + * Install rsyslog + * systemctl restart rsyslog OR systemctl restart rsyslog + * Inspect /var/log/syslog for the following error: + syslog:Aug 4 14:37:56 rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ] + + [Regression potential] + + https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/comments/4 + + [Other information] + + [Original description] + The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to 'syslog' for the user and group, and don't match the ownership/permission of '/dev/console' generating the following: syslog:Aug 3 15:16:58 rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ] Looking in Bionic/18.04LTS, '/dev/console' used to be root:syslog[1], nowadays it's root:tty[2] [1] - Bionic/18.04LTS (Gcloud instance) # ls -l /dev/console crw--w 1 root syslog 5, 1 Aug 3 15:17 /dev/console [2] - Focal/20.04LTS (Gcloud instance) # ls -l /dev/console crw--w 1 root tty 5, 1 Aug 3 17:19 /dev/console # /etc/rsyslog.conf $PrivDropToUser syslog $PrivDropToGroup syslog ** As a debug exercise I did the following: - Cannot reproduce the situation if I intentionally get rid of the PrivDrop* options. - Cannot reproduce the situation if I intentionally add 'syslog' user member of 'tty' group. Meaning that it's pretty obvious with the above statement that the permission denied is caused by the permission/ownership mismatch between '/dev/console' 's ownership permission & syslog user (PrivDropTo[User|Group]). Other bug: https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 ** Description changed: [Impact] At the moment rsyslog cannot have access /dev/console due to a mismatch permission/ownership between '/dev/console' and the Privilege Drop User and Group 'syslog' in rsyslog. [Test Case] * Deploy focal/20.04LTS * Install rsyslog * systemctl restart rsyslog OR systemctl restart rsyslog * Inspect /var/log/syslog for the following error: syslog:Aug 4 14:37:56 rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ] [Regression potential] https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/comments/4 [Other information] + + Other bug: + https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 [Original description] The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to 'syslog' for the user and group, and don't match the ownership/permission of '/dev/console' generating the following: syslog:Aug 3 15:16:58 rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ] Looking in Bionic/18.04LTS, '/dev/console' used to be root:syslog[1], nowadays it's root:tty[2] [1] - Bionic/18.04LTS (Gcloud instance) # ls -l /dev/console crw--w 1 root syslog 5, 1 Aug 3 15:17 /dev/console [2] - Focal/20.04LTS (Gcloud instance) # ls -l /dev/console crw--w 1 root tty 5, 1 Aug 3 17:19 /dev/console # /etc/rsyslog.conf $PrivDropToUser syslog $PrivDropToGroup syslog ** As a debug exercise I did the following: - Cannot reproduce the situation if I intentionally get rid of the PrivDrop* options. - Cannot reproduce the situation if I intentionally add 'syslog' user member of 'tty' group. Meaning that it's pretty obvious with the above statement that the permission denied is caused by the permission/ownership mismatch between '/dev/console' 's ownership permission & syslog user (PrivDropTo[User|Group]). Other bug: https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890177 Title: rsyslogd: file '/dev/console': open error: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890177] Re: rsyslogd: file '/dev/console': open error: Permission denied
** Changed in: rsyslog (Ubuntu Focal) Status: New => In Progress ** Changed in: rsyslog (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: rsyslog (Ubuntu Focal) Assignee: (unassigned) => Eric Desrochers (slashd) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890177 Title: rsyslogd: file '/dev/console': open error: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890177] Re: rsyslogd: file '/dev/console': open error: Permission denied
One easy fix would possibly be the following: # debian/rsyslog.postinst case "$1" in configure) adduser --system --group --no-create-home --quiet syslog || true adduser syslog adm || true +adduser syslog tty || true I have tested it in a PPA, and it works just fine: Preparing to unpack .../rsyslog_8.2001.0-1ubuntu1+test2020307b1_amd64.deb ... Unpacking rsyslog (8.2001.0-1ubuntu1+test2020307b1) over (8.2001.0-1ubuntu1) ... Setting up rsyslog (8.2001.0-1ubuntu1+test2020307b1) ... The user `syslog' is already a member of `adm'. Adding user `syslog' to group `tty' ... ==> Adding user syslog to group tty <== Done. Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Processing triggers for man-db (2.9.1-1) ... Processing triggers for systemd (245.4-4ubuntu3.1) ... # /etc/group tty:x:5:syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890177 Title: rsyslogd: file '/dev/console': open error: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890177] Re: rsyslogd: file '/dev/console': open error: Permission denied
https://wiki.debian.org/SystemGroups tty: TTY devices are owned by this group. This is used by write and wall to enable them to write to other people's TTYs, but it is not intended to be used directly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890177 Title: rsyslogd: file '/dev/console': open error: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890177] Re: rsyslogd: file '/dev/console': open error: Permission denied
One easy fix would possibly be the following: # debian/rsyslog.postinst case "$1" in configure) adduser --system --group --no-create-home --quiet syslog || true adduser syslog adm || true +adduser syslog tty || true I'll give it a try and test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890177 Title: rsyslogd: file '/dev/console': open error: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890177] [NEW] rsyslogd: file '/dev/console': open error: Permission denied
Public bug reported: The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to 'syslog' for the user and group, and don't match the ownership/permission of '/dev/console' generating the following: syslog:Aug 3 15:16:58 rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ] Looking in Bionic/18.04LTS, '/dev/console' used to be root:syslog[1], nowadays it's root:tty[2] [1] - Bionic/18.04LTS (Gcloud instance) # ls -l /dev/console crw--w 1 root syslog 5, 1 Aug 3 15:17 /dev/console [2] - Focal/20.04LTS (Gcloud instance) # ls -l /dev/console crw--w 1 root tty 5, 1 Aug 3 17:19 /dev/console # /etc/rsyslog.conf $PrivDropToUser syslog $PrivDropToGroup syslog ** As a debug exercise I did the following: - Cannot reproduce the situation if I intentionally get rid of the PrivDrop* options. - Cannot reproduce the situation if I intentionally add 'syslog' user member of 'tty' group. Meaning that it's pretty obvious with the above statement that the permission denied is caused by the permission/ownership mismatch between '/dev/console' 's ownership permission & syslog user (PrivDropTo[User|Group]). Other bug: https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Affects: rsyslog (Ubuntu Focal) Importance: Undecided Status: New ** Tags: seg sts ** Tags added: seg sts ** Also affects: rsyslog (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to 'syslog' for the user and group, and don't match the ownership/permission of '/dev/console' generating the following: syslog:Aug 3 15:16:58 rsyslogd: file '/dev/console': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ] Looking in Bionic/18.04LTS, '/dev/console' used to be root:syslog[1], nowadays it's root:tty[2] [1] - Bionic/18.04LTS (Gcloud instance) # ls -l /dev/console crw--w 1 root syslog 5, 1 Aug 3 15:17 /dev/console [2] - Focal/20.04LTS (Gcloud instance) - # ls -l /dev/console + # ls -l /dev/console crw--w 1 root tty 5, 1 Aug 3 17:19 /dev/console - # /etc/rsyslog.conf $PrivDropToUser syslog $PrivDropToGroup syslog ** As a debug exercise I did the following: - Cannot reproduce the situation if I intentionally get rid of the PrivDrop* options. - Cannot reproduce the situation if I intentionally add 'syslog' user member of 'tty' group. + Meaning that it's pretty obvious with the above statement that the + permission denied is caused by the permission/ownership mismatch between + '/dev/console' 's ownership permission & syslog user + (PrivDropTo[User|Group]). + Other bug: https://github.com/GoogleCloudPlatform/compute-image-packages/issues/889 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890177 Title: rsyslogd: file '/dev/console': open error: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1890177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870585] Re: Not cleaning /var/tmp by default
** Bug watch added: Debian Bug tracker #966621 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966621 ** Also affects: systemd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966621 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870585 Title: Not cleaning /var/tmp by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886491] Re: Applying package profile on Xenial doesn't work
[sts-sponsor] Sponsored for Xenial. It is now waiting for the SRU team approval to start building in xenial-proposed pocket. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886491 Title: Applying package profile on Xenial doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1886491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881976] Re: apport-gtk and apport-kde install xiterm+thai as dependency (x-terminal-emulator)
[sts-sponsor] Sponsored in active development release (groovy) ** Changed in: apport (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881976 Title: apport-gtk and apport-kde install xiterm+thai as dependency (x -terminal-emulator) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1881976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881976] Re: apport-gtk and apport-kde install xiterm+thai as dependency (x-terminal-emulator)
[sts-sponsor] @dgadomski I don't think you can add a runtime dependency from universe to a package found in main apport-gtk | 2.20.11-0ubuntu42 | groovy konsole | 4:20.04.3-0ubuntu1 | groovy/universe This would most likely require an MIR for konsole first. https://wiki.ubuntu.com/MainInclusionProcess Dependencies: All binary dependencies (including Recommends:) must be satisfiable in main (i. e. the preferred alternative must be in main). If not, these dependencies need a separate MIR report (this can be a separate bug or another task on the main MIR bug) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881976 Title: apport-gtk and apport-kde install xiterm+thai as dependency (x -terminal-emulator) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1881976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
IMO, we should not assume that upstream cared or not about py < 3.5. As William and I pointed out, we will most likely have to carry the patch to future release due to ESM. I think that opening the discussion upstream to get their official position on this might be insightful, and then we can see which course of action to follow next. (a) Upstream to merge a patch to remain backward compatible that we can cherry-pick (b) Us to carry a "UBUNTU SAUCE:" patch for sshuttle or else -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873368 Title: ssshuttle server fails to connect endpoints with python 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
@scott, Would it be worth submitting it upstream for them to stay backward compatible within the python3 series ? That way we won't have to carry the patch over and over, if this become part of the upstream code. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873368 Title: ssshuttle server fails to connect endpoints with python 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888854] Re: update ovs plugin
** Description changed: + [Impact] + + The Openvswitch plugin is a little outdated. + + sosreport is in constant development, and since 3.9.1 got released a few + plugin updates, adds, ... has been merged upstream (Some changes has + been reported and/or submitted by Canonical employees). Some changes + will be beneficial for the Canonical support team in order to help + troubleshooting UA customer and may also serve for other 3rd party + vendor. + + [Test Case] + + * Install sosreport + * Run sosreport in different customer scenarios: + server, desktop, cloud, hypervisor, instance (container, vm), physical server, ... + * Extract archive and look at the content, look for 0 size file (and use common sense if legit or not) + * Look under "sos_reports" for full report. + * Look under "sos_logs" for warnings/errors. + $ grep -v "INFO:" sos_logs/sos.log + * Run "simple.sh": A quick port of the travis tests to bash. Generating various type of sosreports collection (which is part of the autopkgtest (d/test/simple.sh) now. + + * https://wiki.ubuntu.com/SosreportUpdates + + [Regression Potential] + + Sosreport, as of today, has ~300 plugins that are all configured + differently and configured to run under certain conditions. We can't + test all possible scenarios. All we can do is identify the most common, + important and Ubuntu/Canonical related one and test them (e.g. + Openstack*, juju, MAAS, kernel, ...). With that being said, it is + definitely possible that certain plugins may not work as expected, but + the risk will be very low (e.g. not collecting the desired information) + and isolated to this specific plugin. It shouldn't affect the other + plugins nor core functionalities of sosreport. + + [Other Information] + [Original description] + Backport OVS changes into sosreport (ubuntu) c2bf52d7 [openvswitch] poll dpdk status from ifaces and ports 96c69385 [openvswitch] pull cfm, qos, and bond info 4703cbaa [openvswitch] Add LACP stats 27ef2569 [openvswitch] List important dpdk related directories bc0c0245 [openvswitch] ensure -t 5 for ovs-vsctl where needed eb145d94 [openvswitch] capture all datapath data 798fc4a5 [openvswitch] pull additional bridge information e1b474af [openvswitch] add support for OpenFlow 1.4 and 1.5 ac1ebcc8 [openvswitch] only check mempool information for dpdk-init=true ** Changed in: sosreport (Ubuntu Focal) Status: New => In Progress ** Changed in: sosreport (Ubuntu Focal) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: sosreport (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/154 Title: update ovs plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888403] Re: sosreport plugins updates
** Changed in: sosreport (Ubuntu Focal) Status: New => In Progress ** Changed in: sosreport (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: sosreport (Ubuntu Focal) Assignee: (unassigned) => Eric Desrochers (slashd) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888403 Title: sosreport plugins updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1888403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888854] Re: update ovs plugin
** Description changed: - Backport OVS changes into sosreport (ubuntu) ? + Backport OVS changes into sosreport (ubuntu) c2bf52d7 [openvswitch] poll dpdk status from ifaces and ports 96c69385 [openvswitch] pull cfm, qos, and bond info 4703cbaa [openvswitch] Add LACP stats 27ef2569 [openvswitch] List important dpdk related directories bc0c0245 [openvswitch] ensure -t 5 for ovs-vsctl where needed eb145d94 [openvswitch] capture all datapath data 798fc4a5 [openvswitch] pull additional bridge information e1b474af [openvswitch] add support for OpenFlow 1.4 and 1.5 ac1ebcc8 [openvswitch] only check mempool information for dpdk-init=true ** Also affects: sosreport (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Xenial) 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/154 Title: update ovs plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888854] Re: update ovs plugin
** Changed in: sosreport (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/154 Title: update ovs plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888962] Re: development is misspelled in prompt for lts
This is on 18.04.4 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888962 Title: development is misspelled in prompt for lts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1888962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888962] [NEW] development is misspelled in prompt for lts
Public bug reported: When trying to upgrade using do-release-upgrade from an lts version, one gets: There is no development version of an LTS available. To upgrade to the latest non-LTS develoment release set Prompt=normal in /etc/update-manager/release-upgrades. "develoment" should be "development". This is a minor cosmetic bug in line 151 of do-release-upgrade ** Affects: ubuntu-release-upgrader (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/1888962 Title: development is misspelled in prompt for lts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1888962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Packing Beginner
All, I'm Eric, from the Southern US. I've been using Ubuntu almost since it's first release, and have always thought about contributing. I work as a developer, and I love my job but I'm very passionate about using my skills to do something good. This is something I've wanted to do for a long time, but convinced myself I wasn't ready, or didn't have the skills. Now, I know the best way to learn is to just jump in. I'm also a ham radio operator (AG5EI), and I love the fact so many hams use Ubuntu. Lately I've been reading some books on Linux in general (such as Linux API and module development). I have followed the MOTU wikki, I have a GPG and SSH key, and set up a launchpad account. I've been looking over the source code for many packages, and am currently experimenting with making minor code changes and testing them. I've also been downloading and installing the daily lives. I've been lurking a couple of the mailing lists, and admit that a lot of what I've read there I just don't understand yet. I have been reading through bugs for various packages, and Ubuntu itself a lot too. I'm willing to help in any way I can, not just programming. If that means simply testing and reporting or verifying bugs. Thanks in advance for helping me, and thanks to everyone who has contributed to this operating system I've had the privilege of using these past 15 years. Eric Stricklin -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
[Bug 1888854] Re: update ovs plugin
** Changed in: sosreport (Ubuntu) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: sosreport (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/154 Title: update ovs plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
I wrote to sil2100 (SRU verification team member) He'll take a look at it when time permit, and he should update the bug anytime soon with his 2 cents about the current situation. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873368 Title: ssshuttle server fails to connect endpoints with python 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888403] Re: sosreport plugins updates
** Description changed: [Impact] sosreport is in constant development, and since 3.9.1 got released a few plugin updates, adds, ... has been merged upstream (Some of the changes has been reported and/or submitted by Canonical employees). Some changes will be beneficial for the Canonical support team in order to help troubleshooting UA customer and may also serve for other 3rd party vendor. [Test Case] * Install sosreport * Run sosreport in different customer scenarios: server, desktop, cloud, hypervisor, instance (container, vm), physical server, ... * Extract archive and look at the content, look for 0 size file (and use common sense if legit or not) * Look under "sos_reports" for full report. * Look under "sos_logs" for warnings/errors. $ grep -v "INFO:" sos_logs/sos.log * Run "simple.sh": A quick port of the travis tests to bash. Generating various type of sosreports collection (which is part of the autopkgtest (d/test/simple.sh) now. * https://wiki.ubuntu.com/SosreportUpdates [Regression Potential] Sosreport, as of today, has ~300 plugins that are all configured differently and configured to run under certain conditions. We can't test all possible scenarios. All we can do is identify the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...). With that being said, it is definitely possible that certain plugins may not work as expected, but the risk will be very low (e.g. not collecting the desired information) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionalities of sosreport. [Other Information] [Original description] List of plugins update under evaluation (so far) for next sosreport SRU: (The list is susceptible to change as it is still an evaluation as we speak) 4be4e4ea [drbd] Add new plugin for DRBD 43b4a9ab [maas] use maas-region instead of deprecated maas-region-admin - c2bf52d7 [openvswitch] poll dpdk status from ifaces and ports - 96c69385 [openvswitch] pull cfm, qos, and bond info - 4703cbaa [openvswitch] Add LACP stats - 27ef2569 [openvswitch] List important dpdk related directories - bc0c0245 [openvswitch] ensure -t 5 for ovs-vsctl where needed - eb145d94 [openvswitch] capture all datapath data - 798fc4a5 [openvswitch] pull additional bridge information - e1b474af [openvswitch] add support for OpenFlow 1.4 and 1.5 - ac1ebcc8 [openvswitch] only check mempool information for dpdk-init=true 31e04678 [networking] collect iptables when proper kernel modules loaded 591cd4cf [networking] Small change to produce more-useful, numbered ufw rule status e8b38048 [systemd] update trigger with better generic file check e9d71c78 [ubuntu] support status command update 3a50987a [sar] Extend command sadf to get more data out of sar 9d572eb4 [kubernetes] Adding support for alternate Ubuntu deployments b34edec3 [pacemaker] Fix scrubbing when password contains an equal sign ** Changed in: sosreport (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888403 Title: sosreport plugins updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1888403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888854] Re: update ovs plugin
The above is under evaluation/investigation. ** Description changed: + Backport OVS changes into sosreport (ubuntu) ? + c2bf52d7 [openvswitch] poll dpdk status from ifaces and ports 96c69385 [openvswitch] pull cfm, qos, and bond info 4703cbaa [openvswitch] Add LACP stats 27ef2569 [openvswitch] List important dpdk related directories bc0c0245 [openvswitch] ensure -t 5 for ovs-vsctl where needed eb145d94 [openvswitch] capture all datapath data 798fc4a5 [openvswitch] pull additional bridge information e1b474af [openvswitch] add support for OpenFlow 1.4 and 1.5 ac1ebcc8 [openvswitch] only check mempool information for dpdk-init=true -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/154 Title: update ovs plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888854] [NEW] update ovs plugin
Public bug reported: Backport OVS changes into sosreport (ubuntu) ? c2bf52d7 [openvswitch] poll dpdk status from ifaces and ports 96c69385 [openvswitch] pull cfm, qos, and bond info 4703cbaa [openvswitch] Add LACP stats 27ef2569 [openvswitch] List important dpdk related directories bc0c0245 [openvswitch] ensure -t 5 for ovs-vsctl where needed eb145d94 [openvswitch] capture all datapath data 798fc4a5 [openvswitch] pull additional bridge information e1b474af [openvswitch] add support for OpenFlow 1.4 and 1.5 ac1ebcc8 [openvswitch] only check mempool information for dpdk-init=true ** Affects: sosreport (Ubuntu) Importance: Undecided Status: New ** Tags: seg sts ** Tags added: seg sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/154 Title: update ovs plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
Thanks Chris ! Will ping SRU team to release it sometime this or next week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873368 Title: ssshuttle server fails to connect endpoints with python 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888403] Re: sosreport plugins updates
** Description changed: [Impact] sosreport is in constant development, and since 3.9.1 got released a few - plugin updates, adds, ... happened. Some changes will be benefit the - Canonical support team in troubleshooting UA customer and may also serve - for other 3rd party vendor. + plugin updates, adds, ... has been merged upstream (Some of the changes + have been proposed by Canonical employees). Some changes will be + beneficial for the Canonical support team in order to help + troubleshooting UA customer and may also serve for other 3rd party + vendor. [Test Case] * Install sosreport * Run sosreport in different customer scenarios: server, desktop, cloud, hypervisor, instance (container, vm), physical server, ... * Extract archive and look at the content, look for 0 size file (and use common sense if legit or not) * Look under "sos_reports" for full report. * Look under "sos_logs" for warnings/errors. $ grep -v "INFO:" sos_logs/sos.log * Run "simple.sh": A quick port of the travis tests to bash. Generating various type of sosreports collection (which is part of the autopkgtest (d/test/simple.sh) now. * https://wiki.ubuntu.com/SosreportUpdates [Regression Potential] Sosreport, as of today, has ~300 plugins that are all configured differently and configured to run under certain conditions. We can't test all possible scenarios. All we can do is identify the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...). With that being said, it is definitely possible that certain plugins may not work as expected, but the risk will be very low (e.g. not collecting the desired information) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionalities of sosreport. [Other Information] [Original description] List of plugins update under evaluation (so far) for next sosreport SRU: (The list is susceptible to change as it is still an evaluation as we speak) 4be4e4ea [drbd] Add new plugin for DRBD 43b4a9ab [maas] use maas-region instead of deprecated maas-region-admin c2bf52d7 [openvswitch] poll dpdk status from ifaces and ports 96c69385 [openvswitch] pull cfm, qos, and bond info 4703cbaa [openvswitch] Add LACP stats 27ef2569 [openvswitch] List important dpdk related directories bc0c0245 [openvswitch] ensure -t 5 for ovs-vsctl where needed eb145d94 [openvswitch] capture all datapath data 798fc4a5 [openvswitch] pull additional bridge information e1b474af [openvswitch] add support for OpenFlow 1.4 and 1.5 ac1ebcc8 [openvswitch] only check mempool information for dpdk-init=true 31e04678 [networking] collect iptables when proper kernel modules loaded 591cd4cf [networking] Small change to produce more-useful, numbered ufw rule status e8b38048 [systemd] update trigger with better generic file check e9d71c78 [ubuntu] support status command update 3a50987a [sar] Extend command sadf to get more data out of sar 9d572eb4 [kubernetes] Adding support for alternate Ubuntu deployments b34edec3 [pacemaker] Fix scrubbing when password contains an equal sign ** Description changed: [Impact] sosreport is in constant development, and since 3.9.1 got released a few plugin updates, adds, ... has been merged upstream (Some of the changes - have been proposed by Canonical employees). Some changes will be + has been proposed by Canonical employees). Some changes will be beneficial for the Canonical support team in order to help troubleshooting UA customer and may also serve for other 3rd party vendor. [Test Case] * Install sosreport * Run sosreport in different customer scenarios: server, desktop, cloud, hypervisor, instance (container, vm), physical server, ... * Extract archive and look at the content, look for 0 size file (and use common sense if legit or not) * Look under "sos_reports" for full report. * Look under "sos_logs" for warnings/errors. $ grep -v "INFO:" sos_logs/sos.log * Run "simple.sh": A quick port of the travis tests to bash. Generating various type of sosreports collection (which is part of the autopkgtest (d/test/simple.sh) now. * https://wiki.ubuntu.com/SosreportUpdates [Regression Potential] Sosreport, as of today, has ~300 plugins that are all configured differently and configured to run under certain conditions. We can't test all possible scenarios. All we can do is identify the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...). With that being said, it is definitely possible that certain plugins may not work as expected, but the risk will be very low (e.g. not collecting the desired information) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionalities of sosreport. [Other Information] [Original description]
[Bug 1888403] Re: sosreport plugins updates
** Description changed: + [Impact] + + sosreport is in constant development, and since 3.9.1 got released a few + plugin updates, adds, ... happens. Those change will be useful for + Canonical support in troubleshooting UA customer and may also server + other 3rd party vendor. + + + [Test Case] + + * Install sosreport + * Run sosreport in different customer scenarios: + server, desktop, cloud, hypervisor, instance (container, vm), physical server, ... + * Extract archive and look at the content, look for 0 size file (and use common sense if legit or not) + * Look under "sos_reports" for full report. + * Look under "sos_logs" for warnings/errors. + $ grep -v "INFO:" sos_logs/sos.log + * Run "simple.sh": A quick port of the travis tests to bash. Generating various type of sosreports collection (which is part of the autopkgtest (d/test/simple.sh) now. + + * https://wiki.ubuntu.com/SosreportUpdates + + [Regression Potential] + + Sosreport, as of today, has ~300 plugins that are all configured + differently and configured to run under certain conditions. We can't + test all possible scenarios. All we can do is identify the most common, + important and Ubuntu/Canonical related one and test them (e.g. + Openstack*, juju, MAAS, kernel, ...). With that being said, it is + definitely possible that certain plugins may not work as expected, but + the risk will be very low (e.g. not collecting the desired information) + and isolated to this specific plugin. It shouldn't affect the other + plugins nor core functionalities of sosreport. + + [Other Information] + [Original description] + List of plugins update under evaluation (so far) for next sosreport SRU: (The list is susceptible to change as it is still an evaluation as we speak) 4be4e4ea [drbd] Add new plugin for DRBD 43b4a9ab [maas] use maas-region instead of deprecated maas-region-admin c2bf52d7 [openvswitch] poll dpdk status from ifaces and ports 96c69385 [openvswitch] pull cfm, qos, and bond info 4703cbaa [openvswitch] Add LACP stats 27ef2569 [openvswitch] List important dpdk related directories bc0c0245 [openvswitch] ensure -t 5 for ovs-vsctl where needed eb145d94 [openvswitch] capture all datapath data 798fc4a5 [openvswitch] pull additional bridge information e1b474af [openvswitch] add support for OpenFlow 1.4 and 1.5 ac1ebcc8 [openvswitch] only check mempool information for dpdk-init=true 31e04678 [networking] collect iptables when proper kernel modules loaded 591cd4cf [networking] Small change to produce more-useful, numbered ufw rule status e8b38048 [systemd] update trigger with better generic file check e9d71c78 [ubuntu] support status command update 3a50987a [sar] Extend command sadf to get more data out of sar 9d572eb4 [kubernetes] Adding support for alternate Ubuntu deployments b34edec3 [pacemaker] Fix scrubbing when password contains an equal sign ** Description changed: [Impact] sosreport is in constant development, and since 3.9.1 got released a few - plugin updates, adds, ... happens. Those change will be useful for - Canonical support in troubleshooting UA customer and may also server - other 3rd party vendor. - + plugin updates, adds, ... happened. Some changes will be benefit the + Canonical support team in troubleshooting UA customer and may also serve + for other 3rd party vendor. [Test Case] * Install sosreport * Run sosreport in different customer scenarios: server, desktop, cloud, hypervisor, instance (container, vm), physical server, ... * Extract archive and look at the content, look for 0 size file (and use common sense if legit or not) * Look under "sos_reports" for full report. * Look under "sos_logs" for warnings/errors. - $ grep -v "INFO:" sos_logs/sos.log + $ grep -v "INFO:" sos_logs/sos.log * Run "simple.sh": A quick port of the travis tests to bash. Generating various type of sosreports collection (which is part of the autopkgtest (d/test/simple.sh) now. * https://wiki.ubuntu.com/SosreportUpdates [Regression Potential] Sosreport, as of today, has ~300 plugins that are all configured differently and configured to run under certain conditions. We can't test all possible scenarios. All we can do is identify the most common, important and Ubuntu/Canonical related one and test them (e.g. Openstack*, juju, MAAS, kernel, ...). With that being said, it is definitely possible that certain plugins may not work as expected, but the risk will be very low (e.g. not collecting the desired information) and isolated to this specific plugin. It shouldn't affect the other plugins nor core functionalities of sosreport. [Other Information] [Original description] List of plugins update under evaluation (so far) for next sosreport SRU: (The list is susceptible to change as it is still an evaluation as we speak) 4be4e4ea [drbd] Add new plugin for DRBD 43b4a9ab [maas] use maas-region instead of
[Bug 1888403] [NEW] sosreport plugins updates
Public bug reported: List of plugins update under evaluation (so far) for next sosreport SRU: (The list is susceptible to change as it is still an evaluation as we speak) 4be4e4ea [drbd] Add new plugin for DRBD 43b4a9ab [maas] use maas-region instead of deprecated maas-region-admin c2bf52d7 [openvswitch] poll dpdk status from ifaces and ports 96c69385 [openvswitch] pull cfm, qos, and bond info 4703cbaa [openvswitch] Add LACP stats 27ef2569 [openvswitch] List important dpdk related directories bc0c0245 [openvswitch] ensure -t 5 for ovs-vsctl where needed eb145d94 [openvswitch] capture all datapath data 798fc4a5 [openvswitch] pull additional bridge information e1b474af [openvswitch] add support for OpenFlow 1.4 and 1.5 ac1ebcc8 [openvswitch] only check mempool information for dpdk-init=true 31e04678 [networking] collect iptables when proper kernel modules loaded 591cd4cf [networking] Small change to produce more-useful, numbered ufw rule status e8b38048 [systemd] update trigger with better generic file check e9d71c78 [ubuntu] support status command update 3a50987a [sar] Extend command sadf to get more data out of sar 9d572eb4 [kubernetes] Adding support for alternate Ubuntu deployments b34edec3 [pacemaker] Fix scrubbing when password contains an equal sign ** Affects: sosreport (Ubuntu) Importance: Medium Assignee: Eric Desrochers (slashd) Status: In Progress ** Affects: sosreport (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: sosreport (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: sosreport (Ubuntu Focal) Importance: Undecided Status: New ** Affects: sosreport (Ubuntu Groovy) Importance: Medium Assignee: Eric Desrochers (slashd) Status: In Progress ** Tags: seg sts ** Also affects: sosreport (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: sosreport (Ubuntu Focal) Importance: Undecided Status: New ** Tags added: seg sts ** Description changed: List of plugins update under evaluation (so far) for next sosreport SRU: 4be4e4ea [drbd] Add new plugin for DRBD 43b4a9ab [maas] use maas-region instead of deprecated maas-region-admin c2bf52d7 [openvswitch] poll dpdk status from ifaces and ports 96c69385 [openvswitch] pull cfm, qos, and bond info 4703cbaa [openvswitch] Add LACP stats 27ef2569 [openvswitch] List important dpdk related directories bc0c0245 [openvswitch] ensure -t 5 for ovs-vsctl where needed eb145d94 [openvswitch] capture all datapath data 798fc4a5 [openvswitch] pull additional bridge information e1b474af [openvswitch] add support for OpenFlow 1.4 and 1.5 ac1ebcc8 [openvswitch] only check mempool information for dpdk-init=true 31e04678 [networking] collect iptables when proper kernel modules loaded 591cd4cf [networking] Small change to produce more-useful, numbered ufw rule status - 1417827a [maas] Add snap support to maas plugin ** Changed in: sosreport (Ubuntu Groovy) Status: New => In Progress ** Changed in: sosreport (Ubuntu Groovy) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: sosreport (Ubuntu Groovy) Importance: Undecided => Medium ** Description changed: List of plugins update under evaluation (so far) for next sosreport SRU: + + (The list is susceptible to change as it is still an evaluation as we + speak) 4be4e4ea [drbd] Add new plugin for DRBD 43b4a9ab [maas] use maas-region instead of deprecated maas-region-admin c2bf52d7 [openvswitch] poll dpdk status from ifaces and ports 96c69385 [openvswitch] pull cfm, qos, and bond info 4703cbaa [openvswitch] Add LACP stats 27ef2569 [openvswitch] List important dpdk related directories bc0c0245 [openvswitch] ensure -t 5 for ovs-vsctl where needed eb145d94 [openvswitch] capture all datapath data 798fc4a5 [openvswitch] pull additional bridge information e1b474af [openvswitch] add support for OpenFlow 1.4 and 1.5 ac1ebcc8 [openvswitch] only check mempool information for dpdk-init=true 31e04678 [networking] collect iptables when proper kernel modules loaded 591cd4cf [networking] Small change to produce more-useful, numbered ufw rule status ** Description changed: List of plugins update under evaluation (so far) for next sosreport SRU: (The list is susceptible to change as it is still an evaluation as we speak) 4be4e4ea [drbd] Add new plugin for DRBD 43b4a9ab [maas] use maas-region instead of deprecated maas-region-admin c2bf52d7 [openvswitch] poll dpdk status from ifaces and ports 96c69385 [openvswitch] pull cfm, qos, and bond info 4703cbaa [openvswitch] Add LACP stats 27ef2569 [openvswitch] List important dpdk related directories bc0c0245 [openvswitch] ensure -t 5 for ovs-vs
[Bug 1865212] Re: simple.sh to be run as part of the autopkgtests
[VERIFICATION XENIAL] I have reviewed all ARCHes under http://autopkgtest.ubuntu.com/ and they all passed # For instance here's the XENIAL for amd64 architecture: http://autopkgtest.ubuntu.com/packages/s/sosreport/xenial/amd64 # Log also confirm the success: Everything worked! autopkgtest [14:31:42]: test simple.sh: ---] simple.shPASS autopkgtest [14:31:42]: test simple.sh: - - - - - - - - - - results - - - - - - - - - - autopkgtest [14:31:42]: summary sos-run-nonroot.py PASS sos-run.py PASS simple.shPASS # pending sru page doesn't reveal anything, meaning everything passed as expected. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865212 Title: simple.sh to be run as part of the autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1865212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886548] Re: setcifsacl: fix adding ACE when owner sid in unexpected location
Thanks for your testing nspmangalore, much appreciated ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886548 Title: setcifsacl: fix adding ACE when owner sid in unexpected location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1886548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886548] Re: setcifsacl: fix adding ACE when owner sid in unexpected location
The release of 'cifs-utils' is likely to happen only next week. As stated in the SRU policy guide : "Please note that SRUs will not be published to the -updates pocket on Friday (or Saturday or Sunday). Any exception will need justification." Let's circle back beginning of next week for its release. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886548 Title: setcifsacl: fix adding ACE when owner sid in unexpected location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1886548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883320] Re: [kvm] change check_enabled to /dev/kvm
[VERIFICATION XENIAL] Test with sosreport: 3.9.1-1ubuntu0.16.04.1 * Running sosreport from for instance an LXD container, no longer reveal KVM details from its host as it was previously (if KVM was installed at the host level): ** ls -altr sos_commands/kvm ls: cannot access 'sos_commands/kvm': No such file or directory * Running sosreport from a system with KVM installed does triggers the KVM plugin as it should and the data is accurate and as expected. * sos_logs/sos.log: INFO: [plugin:kvm] collecting path '/sys/module/kvm/srcversion' INFO: [plugin:kvm] collecting path '/sys/module/kvm_intel/srcversion' INFO: [plugin:kvm] collecting output of 'kvm_stat --once' # ls sos_commands/kvm/ total 20 kvm_stat_--once ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883320 Title: [kvm] change check_enabled to /dev/kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1883320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886494] Re: sosreport does not correctly enable the maas plugin for a snap install
[VERIFICATION XENIAL] This has been tested running sosreport (3.9.1-1ubuntu0.16.04.1) # sos_logs/sos.log revealed that the MAAS plugin has been exercised on a MAAS snap install as expected. # No errors found. # Logs sos.log:2020-07-16 15:27:10,001 INFO: [plugin:maas] added cmd output 'systemctl status snap.maas.supervisor' sos.log:2020-07-16 15:27:10,034 INFO: [plugin:maas] added cmd output 'snap info maas' sos.log:2020-07-16 15:27:10,034 INFO: [plugin:maas] added cmd output 'maas status' sos.log:2020-07-16 15:27:10,034 INFO: [plugin:maas] adding forbidden path '/var/snap/maas/current/bind/session.key' sos.log:2020-07-16 15:27:10,035 INFO: [plugin:maas] added cmd output 'journalctl --no-pager --unit maas-dhcpd' sos.log:2020-07-16 15:27:10,035 INFO: [plugin:maas] added cmd output 'journalctl --no-pager --unit maas-dhcpd6' sos.log:2020-07-16 15:27:10,035 INFO: [plugin:maas] added cmd output 'journalctl --no-pager --unit maas-http' sos.log:2020-07-16 15:27:10,035 INFO: [plugin:maas] added cmd output 'journalctl --no-pager --unit maas-proxy' sos.log:2020-07-16 15:27:10,036 INFO: [plugin:maas] added cmd output 'journalctl --no-pager --unit maas-rackd' sos.log:2020-07-16 15:27:10,036 INFO: [plugin:maas] added cmd output 'journalctl --no-pager --unit maas-regiond' sos.log:2020-07-16 15:27:10,036 INFO: [plugin:maas] added cmd output 'journalctl --no-pager --unit maas-syslog' sos.log:2020-07-16 15:27:10,036 INFO: [plugin:maas] added cmd output 'journalctl --no-pager --unit snap.maas.supervisor' sos.log:2020-07-16 15:27:11,705 INFO: [plugin:maas] collecting path '/var/snap/maas/current/preseeds' sos.log:2020-07-16 15:27:11,709 INFO: [plugin:maas] collecting path '/var/snap/maas/current/supervisord' sos.log:2020-07-16 15:27:11,712 INFO: [plugin:maas] collecting path '/var/snap/maas/common/log' sos.log:2020-07-16 15:27:11,714 INFO: [plugin:maas] collecting path '/var/snap/maas/current/regiond.conf' sos.log:2020-07-16 15:27:11,715 INFO: [plugin:maas] collecting output of 'systemctl status snap.maas.supervisor' sos.log:2020-07-16 15:27:11,729 INFO: [plugin:maas] collecting output of 'snap info maas' sos.log:2020-07-16 15:27:12,477 INFO: [plugin:maas] collecting output of 'maas status' sos.log:2020-07-16 15:27:14,504 INFO: [plugin:maas] collecting output of 'journalctl --no-pager --unit maas-dhcpd' sos.log:2020-07-16 15:27:14,519 INFO: [plugin:maas] collecting output of 'journalctl --no-pager --unit maas-dhcpd6' sos.log:2020-07-16 15:27:14,534 INFO: [plugin:maas] collecting output of 'journalctl --no-pager --unit maas-http' sos.log:2020-07-16 15:27:14,550 INFO: [plugin:maas] collecting output of 'journalctl --no-pager --unit maas-proxy' sos.log:2020-07-16 15:27:14,564 INFO: [plugin:maas] collecting output of 'journalctl --no-pager --unit maas-rackd' sos.log:2020-07-16 15:27:14,580 INFO: [plugin:maas] collecting output of 'journalctl --no-pager --unit maas-regiond' sos.log:2020-07-16 15:27:14,594 INFO: [plugin:maas] collecting output of 'journalctl --no-pager --unit maas-syslog' sos.log:2020-07-16 15:27:14,609 INFO: [plugin:maas] collecting output of 'journalctl --no-pager --unit snap.maas.supervisor' ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886494 Title: sosreport does not correctly enable the maas plugin for a snap install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1886494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884293] Re: Update to maintenance release v3.9.1
[VERIFICATION XENIAL] Test with sosreport: 3.9.1-1ubuntu0.16.04.1 * The simple.sh as part of the autopkgtest 'Passed' doing the following scenarios for all ARCHES: # RUNNING -l # # RUNNING --list-presets # # RUNNING --list-profiles # # RUNNING --batch --build --no-env-vars # # RUNNING --batch --no-report -o hardware # # RUNNING --batch --label TEST -a -c never # # RUNNING --batch --debug --log-size 0 -c always # # RUNNING --batch -z xz --log-size 1 # # RUNNING --batch -z gzip # # RUNNING --batch -z bzip2 -t 1 -n hardware # # RUNNING --batch --quiet -e opencl -k kernel.with-timer # # RUNNING --batch --case-id 10101 --all-logs --since=20191007 # # RUNNING --batch --verbose --no-postproc # -- ### end stdout ### start extraction ### stop extraction # DONE WITH --batch --verbose --no-postproc # Everything worked! -- * Running sosreport manually like a typical UA customer would do revealed no observable legitimate Errors nor Warnings. ** grep -v INFO sos_logs/sos.log ## The below is normal if the modules aren't loaded and permission denied due to apparmor lxd rules. 2020-07-16 15:17:48,030 WARNING: [plugin:networking] skipped command 'ip -s macsec show': required kmods missing: macsec. Use '--allow-system-changes' to enable collection. 2020-07-16 15:17:48,030 WARNING: [plugin:networking] skipped command 'ss -peaonmi': required kmods missing: tcp_diag, netlink_diag, udp_diag, af_packet_diag, inet_diag. Use '--allow-system-changes' to enable collection. 2020-07-16 15:17:51,921 WARNING: [plugin:system] _copy_dir: '/proc/sys/fs' Permission denied Nothing to worry about here. ** ls sos_logs/ sos.log ui.log No Stack Trace file found. * No non-legit 0 size files found. * Commonly used parameter all works as expected. * --upload work and got uploaded into our FTP uploads/ folder. - Eric ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884293 Title: Update to maintenance release v3.9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1884293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886548] Re: setcifsacl: fix adding ACE when owner sid in unexpected location
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886548 Title: setcifsacl: fix adding ACE when owner sid in unexpected location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1886548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874526] Re: [landscape] Substitute oidc conf in service file
** Changed in: sosreport (Ubuntu Xenial) Assignee: (unassigned) => Eric Desrochers (slashd) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874526 Title: [landscape] Substitute oidc conf in service file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1874526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827367] Re: rabbitmq-server outdated
@gpiccoli, One is the bug itself and the other one is the backport request "paperwork". I guess we duplicate to kind of link them together. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827367 Title: rabbitmq-server outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elixir-lang/+bug/1827367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827367] Re: rabbitmq-server outdated
@gpiccoli, One is the bug itself and the other one is the backport request "paperwork". I guess we could mark them as duplicate to kind of link them together. -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1827367 Title: rabbitmq-server outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elixir-lang/+bug/1827367/+subscriptions -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 1827367] Re: rabbitmq-server outdated
@gpiccoli, One is the bug itself and the other one is the backport request "paperwork". I guess we could mark them as duplicate to kind of link them together. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827367 Title: rabbitmq-server outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elixir-lang/+bug/1827367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827367] Re: rabbitmq-server outdated
@gpiccoli, One is the bug itself and the other one is the backport request "paperwork". I guess we duplicate to kind of link them together. -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1827367 Title: rabbitmq-server outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elixir-lang/+bug/1827367/+subscriptions -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 1883320] Re: [kvm] change check_enabled to /dev/kvm
** Changed in: sosreport (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883320 Title: [kvm] change check_enabled to /dev/kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1883320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865212] Re: simple.sh to be run as part of the autopkgtests
** Changed in: sosreport (Ubuntu Xenial) Status: Won't Fix => In Progress ** Changed in: sosreport (Ubuntu Xenial) Assignee: (unassigned) => Eric Desrochers (slashd) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865212 Title: simple.sh to be run as part of the autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1865212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886494] Re: sosreport does not correctly enable the maas plugin for a snap install
** Also affects: sosreport (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: sosreport (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: sosreport (Ubuntu Xenial) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: sosreport (Ubuntu Xenial) 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/1886494 Title: sosreport does not correctly enable the maas plugin for a snap install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1886494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883320] Re: [kvm] change check_enabled to /dev/kvm
** Changed in: sosreport (Ubuntu Xenial) Status: New => In Progress ** Changed in: sosreport (Ubuntu Xenial) Assignee: (unassigned) => Eric Desrochers (slashd) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883320 Title: [kvm] change check_enabled to /dev/kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1883320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884293] Re: Update to maintenance release v3.9.1
** Changed in: sosreport (Ubuntu Xenial) Status: Won't Fix => 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/1884293 Title: Update to maintenance release v3.9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1884293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
** Description changed:
[Impact]
Endpoints that have been updated with python 3.8 seem to cause issues
with sshuttle.
[Test Case]
Client
$ python3 --version
Python 3.8.2
$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
$ apt-cache policy sshuttle
sshuttle:
Installed: 0.78.5-1
Candidate: 0.78.5-1
Server
$ python3 --version
Python 3.8.2
$ lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04
$ apt-cache policy openssh-server
openssh-server:
Installed: 1:8.2p1-4
Candidate: 1:8.2p1-4
$ sshuttle -r ubuntu@{ip-addr} {subnet-1} {subnet-2}
assembler.py:3: DeprecationWarning: the imp module is deprecated in favour of
importlib; see the module's documentation for alternative uses
client: Connected.
Traceback (most recent call last):
File "", line 1, in
File "assembler.py", line 38, in
File "sshuttle.server", line 298, in main
File "/usr/lib/python3.8/socket.py", line 544, in fromfd
return socket(family, type, proto, nfd)
File "/usr/lib/python3.8/socket.py", line 231, in __init__
_socket.socket.__init__(self, family, type, proto, fileno)
OSError: [Errno 88] Socket operation on non-socket
client: fatal: server died with error code 1
[Regression Potential]
- * python 2 has been dropped (support-wise) in Focal.
+ Regression potential is 'low'.
+
+ * In Focal/20.04 LTS, the python included in the base system is Python
+ 3.8.
+
+ * Python 2.7 has been moved to universe and is not included by default
+ in any new installations.
* This fix is actually fixing a regression itself.
This regression was introduced in python 3.8 by bpo#35415 [2], which
restricts socket.fromfd() calls to provide valid socket family file descriptors.
[Other Info]
https://github.com/sshuttle/sshuttle/issues/381
https://bugs.python.org/issue39685
https://bugs.python.org/issue35415
[Original Description]
Client
$ python3 --version
Python 3.8.2
$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
$ apt-cache policy sshuttle
sshuttle:
Installed: 0.78.5-1
Candidate: 0.78.5-1
Server
$ python3 --version
Python 3.8.2
$ lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04
$ apt-cache policy openssh-server
openssh-server:
Installed: 1:8.2p1-4
Candidate: 1:8.2p1-4
$ sshuttle -r ubuntu@{ip-addr} {subnet-1} {subnet-2}
assembler.py:3: DeprecationWarning: the imp module is deprecated in favour of
importlib; see the module's documentation for alternative uses
client: Connected.
Traceback (most recent call last):
File "", line 1, in
File "assembler.py", line 38, in
File "sshuttle.server", line 298, in main
File "/usr/lib/python3.8/socket.py", line 544, in fromfd
return socket(family, type, proto, nfd)
File "/usr/lib/python3.8/socket.py", line 231, in __init__
_socket.socket.__init__(self, family, type, proto, fileno)
OSError: [Errno 88] Socket operation on non-socket
client: fatal: server died with error code 1
The sshuttle upstream tracker is issue#381 [0]. They are waiting on a
response to bpo#39685 [1].
This regression was introduced in python 3.8 by bpo#35415 [2], which
restricts socket.fromfd() calls to provide valid socket family file
descriptors.
[0] https://github.com/sshuttle/sshuttle/issues/381
[1] https://bugs.python.org/issue39685
[2] https://bugs.python.org/issue35415
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
** Tags removed: sts-sponsor-slashd ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873368 Title: ssshuttle server fails to connect endpoints with python 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
[sts-sponsor] Thanks for your contribution Felipe. The debdiff has been sponsored with the following minor changes: - Renamed the quilt patch to "d/p/0001-compatibility-with-python38.patch" - Removed the py2 build dependencies as they are no longer used and prevent to build properly (python-pytest-runner, python-pytest-cov - Added a DEP3 header in the quilt patch. - Slighly modified d/changelog to reflect the minor changes. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873368 Title: ssshuttle server fails to connect endpoints with python 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
** Tags added: sts-sponsor-slashd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873368 Title: ssshuttle server fails to connect endpoints with python 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
** Changed in: sshuttle (Ubuntu Focal) Assignee: Dan Hill (hillpd) => Felipe Reyes (freyes) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873368 Title: ssshuttle server fails to connect endpoints with python 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887426] [NEW] "Error on do-release-upgrade -d 18.04 to 20.04 (mixed destop & server)"
Public bug reported: cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" screenfetch ./+o+- @BazUbu y- -yy+ OS: Ubuntu 18.04 bionic ://+//-yyo Kernel: x86_64 Linux 4.15.0-111-generic .++ .:/++/-.+sss/` Uptime: 1h 54m .:++o: //:--:/- Packages: 4601 o:+o+:++.`..```.-/oo+/ Shell: bash 4.4.20 .:+o:+o/. `+sssoo+/Resolution: 3360x1080 .++/+:+oo+o:` /sssooo. DE: GNOME /+++//+:`oo+o /::--:. WM: GNOME Shell \+/+o+++`o++o ++. WM Theme: Radiance .++.o+++oo+:` /dddhhh. GTK Theme: Ambiance [GTK2/3] .+.o+oo:. `odd+Icon Theme: ubuntu-mono-light \+.++o+o``-.:ohdh+ Font: Ubuntu 11 `:o+++ `oyo++os: CPU: Intel Core i7-2600 @ 8x 3.8GHz .o:`.syhhh/.oo++o` GPU: Mesa DRI Intel(R) HD Graphics 2000 (SNB GT1) /osyyo++ooo+++/ RAM: 3762MiB / 15976MiB ` +oo+++o\: `oo++. I have certainly problem of dependencies, packages installed out of ubuntu... But what to do??? File apt.log shows many things but I don't see the problem. This computer runs first on 12.04 and I migrate up to 18.04 without too much problems (desktop, apache, virtualbox...). How to know which packages are not supported? Best regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18 Uname: Linux 4.15.0-111-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 13 21:08:14 2020 InstallationDate: Installed on 2012-07-21 (2914 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120425-15:28 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-07-13 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: Error checking for authorization org.freedesktop.policykit.exec: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade ** Attachment added: "apt.log" https://bugs.launchpad.net/bugs/1887426/+attachment/5392368/+files/apt.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887426 Title: "Error on do-release-upgrade -d 18.04 to 20.04 (mixed destop & server)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1887426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
** Description changed:
+ [Impact]
+
+ [Test Case]
+
+ [Regression Potential]
+
+ [Other Info]
+
+ [Original Description]
+
Client
$ python3 --version
Python 3.8.2
$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
- $ apt-cache policy sshuttle
+ $ apt-cache policy sshuttle
sshuttle:
- Installed: 0.78.5-1
- Candidate: 0.78.5-1
+ Installed: 0.78.5-1
+ Candidate: 0.78.5-1
Server
$ python3 --version
Python 3.8.2
$ lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04
$ apt-cache policy openssh-server
openssh-server:
- Installed: 1:8.2p1-4
- Candidate: 1:8.2p1-4
+ Installed: 1:8.2p1-4
+ Candidate: 1:8.2p1-4
$ sshuttle -r ubuntu@{ip-addr} {subnet-1} {subnet-2}
assembler.py:3: DeprecationWarning: the imp module is deprecated in favour of
importlib; see the module's documentation for alternative uses
client: Connected.
Traceback (most recent call last):
- File "", line 1, in
- File "assembler.py", line 38, in
- File "sshuttle.server", line 298, in main
- File "/usr/lib/python3.8/socket.py", line 544, in fromfd
- return socket(family, type, proto, nfd)
- File "/usr/lib/python3.8/socket.py", line 231, in __init__
- _socket.socket.__init__(self, family, type, proto, fileno)
+ File "", line 1, in
+ File "assembler.py", line 38, in
+ File "sshuttle.server", line 298, in main
+ File "/usr/lib/python3.8/socket.py", line 544, in fromfd
+ return socket(family, type, proto, nfd)
+ File "/usr/lib/python3.8/socket.py", line 231, in __init__
+ _socket.socket.__init__(self, family, type, proto, fileno)
OSError: [Errno 88] Socket operation on non-socket
client: fatal: server died with error code 1
- The sshuttle upstream tracker is issue#381 [0]. They are waiting on a
response to bpo#39685 [1].
-
- This regression was introduced in python 3.8 by bpo#35415 [2], which
restricts socket.fromfd() calls to provide valid socket family file descriptors.
+ The sshuttle upstream tracker is issue#381 [0]. They are waiting on a
+ response to bpo#39685 [1].
+
+ This regression was introduced in python 3.8 by bpo#35415 [2], which
+ restricts socket.fromfd() calls to provide valid socket family file
+ descriptors.
[0] https://github.com/sshuttle/sshuttle/issues/381
[1] https://bugs.python.org/issue39685
[2] https://bugs.python.org/issue35415
** Description changed:
[Impact]
+
+ Endpoints that have been updated with python 3.8 seem to cause issues
+ with sshuttle.
[Test Case]
+ Client
+ $ python3 --version
+ Python 3.8.2
+ $ lsb_release -rd
+ Description:Ubuntu Focal Fossa (development branch)
+ Release:20.04
+ $ apt-cache policy sshuttle
+ sshuttle:
+ Installed: 0.78.5-1
+ Candidate: 0.78.5-1
+
+ Server
+ $ python3 --version
+ Python 3.8.2
+ $ lsb_release -rd
+ Description:Ubuntu 20.04 LTS
+ Release:20.04
+ $ apt-cache policy openssh-server
+ openssh-server:
+ Installed: 1:8.2p1-4
+ Candidate: 1:8.2p1-4
+
+ $ sshuttle -r ubuntu@{ip-addr} {subnet-1} {subnet-2}
+ assembler.py:3: DeprecationWarning: the imp module is deprecated in favour of
importlib; see the module's documentation for alternative uses
+ client: Connected.
+ Traceback (most recent call last):
+ File "", line 1, in
+ File "assembler.py", line 38, in
+ File "sshuttle.server", line 298, in main
+ File "/usr/lib/python3.8/socket.py", line 544, in fromfd
+ return socket(family, type, proto, nfd)
+ File "/usr/lib/python3.8/socket.py", line 231, in __init__
+ _socket.socket.__init__(self, family, type, proto, fileno)
+ OSError: [Errno 88] Socket operation on non-socket
+ client: fatal: server died with error code 1
+
[Regression Potential]
+ * python 2 has been dropped (support-wise) in Focal.
+
+ * This fix is actually fixing a regression itself.
+ This regression was introduced in python 3.8 by bpo#35415 [2], which
restricts socket.fromfd() calls to provide valid socket family file descriptors.
+
[Other Info]
+
+ https://github.com/sshuttle/sshuttle/issues/381
+ https://bugs.python.org/issue39685
+ https://bugs.python.org/issue35415
[Original Description]
Client
$ python3 --version
Python 3.8.2
$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
$ apt-cache policy sshuttle
sshuttle:
Installed: 0.78.5-1
Candidate: 0.78.5-1
Server
$ python3 --version
Python 3.8.2
$ lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04
$ apt-cache policy openssh-server
openssh-server:
Installed: 1:8.2p1-4
Candidate: 1:8.2p1-4
$ sshuttle -r ubuntu@{ip-addr} {subnet-1} {subnet-2}
assembler.py:3: DeprecationWarning: the imp module is deprecated in favour of
importlib; see the module's documentation for alternative uses
client: Connected.
Traceback (most recent call last):
File "", line 1, in
File
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
@freyes Do you have your focal debdiff handy still ? I'll be happy to sponsor the work you did for sshuttle focal. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873368 Title: ssshuttle server fails to connect endpoints with python 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
Next step is to introduce the fix through SRU into sshuttle version "0.78.5-1". ** Changed in: sshuttle (Ubuntu Groovy) Assignee: Dan Hill (hillpd) => (unassigned) ** Changed in: sshuttle (Ubuntu Focal) Status: Confirmed => 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/1873368 Title: ssshuttle server fails to connect endpoints with python 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
[Groovy]
# Launchpad
https://launchpad.net/ubuntu/+source/sshuttle
# rmadison
sshuttle | 1.0.3-1 | groovy/universe | source, all
# changelog
sshuttle (1.0.3-1) unstable; urgency=medium
[ Brian May ]
* Update to latest upstream version. Closes: #953621.
* Upstream has dropped Python 2 support.
[ Scott Talbert ]
* Remove unused Python 2 dependencies. Closes: #943238.
* Remove ancient X-Python3-Version field
* Add missing ${sphinxdoc:Depends}
* Update debhelper-compat version to 13
* Update Standards-Version to 4.5.0 (no changes needed)
-- Brian May Sun, 12 Jul 2020 19:21:26 +1000
** Changed in: sshuttle (Ubuntu Groovy)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873368
Title:
ssshuttle server fails to connect endpoints with python 3.8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
@smoser, Not for focal, but for the active development release and debian unstable I suggest we bump to 1.0.2. As part of the SRU, just cherry-pick the desired fix. - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873368 Title: ssshuttle server fails to connect endpoints with python 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886494] Re: sosreport does not correctly enable the maas plugin for a snap install
[Autopkgtest regression report (sosreport/3.9.1-1ubuntu0.2] Regression PASSED at 3rd attempts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886494 Title: sosreport does not correctly enable the maas plugin for a snap install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1886494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873368] Re: ssshuttle server fails to connect endpoints with python 3.8
I wrote to the debian maitainer which also seems to be the author of the desired upstream patch. Please see debbugs #953621 I offered him 2 options * (A) Bump "sshuttle" to upstream release "1.0.2" and take benefit of that to modernize the package to a let's say more modern dh compat version, ... * (B) Cherry-pick the 3.8 fix[0] into Debian so that Ubuntu can then follows. - Eric ** Bug watch added: Debian Bug tracker #953621 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953621 ** Also affects: sshuttle (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953621 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873368 Title: ssshuttle server fails to connect endpoints with python 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
