For SRU, I have already contacted sil2100 that should take care of it, but just in case of someone else have a look at the upload and wonder why there is 2 uploads for the same thing.
I have uploaded the sosreport package twice for each release because I forgot to add the (LP: #XXXX) syntax in the d/changelog. For this reason, I have to upload the package a second time (keeping the same version). Feel free to reject the less recent upload and proceed with the most recent ones for AZXT. Regards, Eric ** Description changed: [Impact] Canonical support team (AKA STS) largely depend on sosreport package to troubleshoot system. sosreport is always in constant development including new bugfixes, new features such as new plugins[1], .... that can be interesting to have in a support context. v3.5 is already found in devel release (bionic). We create this LP in the attempt to justify the SRU of v3.5 backport into current supported stable releases. [1] - New plugins for : * perl * boom * vdo * os_net_config * conntrackd * ovirt_imageio * nss * sas3ircu * openstack_aodh * docker_distribution * gluster_block * snappy Plugin API enhancements * Plugin triggers by executable name * Improved log size limit handling * Better handling of compressed log files * Per-plugin package verification lists Updates to 227 plugins This will also allow us to close some sosreport LP bugs: *Docker plugin uses the wrong command for Ubuntu (LP: #1693574) [Test Case] * Install sosreport $ apt-get install sosreport * Run sosreport $ sosreport -a $ sosreport -o <PLUGIN> $ ... * Make sure it generate a tar.xz file in /tmp in the form of "/tmp/sosreport-<HOSTNAME>-<DATE>.tar.xz" - + * Extract files from archive - tar Jxvf /tmp/sosreport-<HOSTNAME>-<DATE>.tar.xz + $ tar Jxvf /tmp/sosreport-<HOSTNAME>-<DATE>.tar.xz * Look the content of sosreport, make sure the information is accurate and valid, .... + + * Make sure all files that should to be collected by sosreport aren't 0 size. (Files that should be collected may varies from one system to another, it depends on what packages are installed, ...) + $ find /tmp/sosreport-<HOSTNAME>-<DATE> -size 0 + + # Note : + It is normal to see some 0 size files here and there, again it depend on how the plugin is run (package detection or not inside the plugins, ...) and if the package is installed or not on the system where you run sosreport. But in most cases, if the package is installed and if sosreport has a plugin for it then it should gather information, if not then it might be a problem with the plugins itself that need adjustments. [Regression Potential] * autopkgtest[2] didn't reveal any [2] - See Comment #1 - * We have tested the package and found a severe regression that we already took action to fix it via : + * We,STS, have intensively tested the package and found a severe regression that we already took action to fix it via : Upstream issue - https://github.com/sosreport/sos/issues/1155 - and submitted to Ubuntu Devel release via debdiff : + and submitted to Ubuntu Devel release via debdiff : lp1734983_bionic.debdiff [Other Info] * Sosreport upstream : https://github.com/sosreport/sos * rmadison -u debian,ubuntu sosreport debian: sosreport | 3.2-2 | oldstable | source, amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x sosreport | 3.2-2 | oldstable-kfreebsd | source, kfreebsd-amd64, kfreebsd-i386 sosreport | 3.3+git50-g3c0349b-2 | stable | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x sosreport | 3.5-1 | testing | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x sosreport | 3.5-1 | unstable | source, amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x ubuntu: sosreport | 3.0-1~ubuntu12.04.1 | precise-backports/universe | source, amd64, armel, armhf, i386, powerpc sosreport | 3.1-1ubuntu2 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el sosreport | 3.1-1ubuntu2.2 | trusty-security | source, amd64, arm64, armhf, i386, powerpc, ppc64el sosreport | 3.2-2~ubuntu14.04.1 | trusty-backports | source, amd64, arm64, armhf, i386, powerpc, ppc64el sosreport | 3.2+git276-g7da50d6-3ubuntu1 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x sosreport | 3.3+git50-g3c0349b-2 | zesty | source, amd64, arm64, armhf, i386, ppc64el, s390x sosreport | 3.4-1~ubuntu14.04.1 | trusty-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el sosreport | 3.4-1~ubuntu16.04.1 | xenial-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x sosreport | 3.4-1~ubuntu17.04.1 | zesty-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x sosreport | 3.4-1 | artful | source, amd64, arm64, armhf, i386, ppc64el, s390x sosreport | 3.5-1 | bionic | source, amd64, arm64, armhf, i386, ppc64el, s390x ** Description changed: [Impact] Canonical support team (AKA STS) largely depend on sosreport package to troubleshoot system. sosreport is always in constant development including new bugfixes, new features such as new plugins[1], .... that can be interesting to have in a support context. v3.5 is already found in devel release (bionic). We create this LP in the attempt to justify the SRU of v3.5 backport into current supported stable releases. [1] - New plugins for : * perl * boom * vdo * os_net_config * conntrackd * ovirt_imageio * nss * sas3ircu * openstack_aodh * docker_distribution * gluster_block * snappy Plugin API enhancements * Plugin triggers by executable name * Improved log size limit handling * Better handling of compressed log files * Per-plugin package verification lists Updates to 227 plugins This will also allow us to close some sosreport LP bugs: *Docker plugin uses the wrong command for Ubuntu (LP: #1693574) [Test Case] * Install sosreport $ apt-get install sosreport * Run sosreport $ sosreport -a $ sosreport -o <PLUGIN> $ ... * Make sure it generate a tar.xz file in /tmp in the form of "/tmp/sosreport-<HOSTNAME>-<DATE>.tar.xz" - + * Extract files from archive $ tar Jxvf /tmp/sosreport-<HOSTNAME>-<DATE>.tar.xz * Look the content of sosreport, make sure the information is accurate and valid, .... - * Make sure all files that should to be collected by sosreport aren't 0 size. (Files that should be collected may varies from one system to another, it depends on what packages are installed, ...) - $ find /tmp/sosreport-<HOSTNAME>-<DATE> -size 0 + * Make sure all files that should to be collected by sosreport aren't 0 size. (Files that should be collected may varies from one system to another, it depends on what packages are installed, ...) + $ find /tmp/sosreport-<HOSTNAME>-<DATE> -size 0 # Note : It is normal to see some 0 size files here and there, again it depend on how the plugin is run (package detection or not inside the plugins, ...) and if the package is installed or not on the system where you run sosreport. But in most cases, if the package is installed and if sosreport has a plugin for it then it should gather information, if not then it might be a problem with the plugins itself that need adjustments. [Regression Potential] * autopkgtest[2] didn't reveal any [2] - See Comment #1 - * We,STS, have intensively tested the package and found a severe regression that we already took action to fix it via : - Upstream issue - https://github.com/sosreport/sos/issues/1155 + * We,STS, have intensively tested the package. - and submitted to Ubuntu Devel release via debdiff : - lp1734983_bionic.debdiff + During our testing, we found a severe regression that we already took + action to fix it via : + + - Upstream issue - https://github.com/sosreport/sos/issues/1155 + - Debian bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537 + - Fix Released in Ubuntu Devel release (bionic) via debdiff : lp1734983_bionic.debdiff [Other Info] * Sosreport upstream : https://github.com/sosreport/sos * rmadison -u debian,ubuntu sosreport debian: sosreport | 3.2-2 | oldstable | source, amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x sosreport | 3.2-2 | oldstable-kfreebsd | source, kfreebsd-amd64, kfreebsd-i386 sosreport | 3.3+git50-g3c0349b-2 | stable | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x sosreport | 3.5-1 | testing | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x sosreport | 3.5-1 | unstable | source, amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x ubuntu: sosreport | 3.0-1~ubuntu12.04.1 | precise-backports/universe | source, amd64, armel, armhf, i386, powerpc sosreport | 3.1-1ubuntu2 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el sosreport | 3.1-1ubuntu2.2 | trusty-security | source, amd64, arm64, armhf, i386, powerpc, ppc64el sosreport | 3.2-2~ubuntu14.04.1 | trusty-backports | source, amd64, arm64, armhf, i386, powerpc, ppc64el sosreport | 3.2+git276-g7da50d6-3ubuntu1 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x sosreport | 3.3+git50-g3c0349b-2 | zesty | source, amd64, arm64, armhf, i386, ppc64el, s390x sosreport | 3.4-1~ubuntu14.04.1 | trusty-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el sosreport | 3.4-1~ubuntu16.04.1 | xenial-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x sosreport | 3.4-1~ubuntu17.04.1 | zesty-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x sosreport | 3.4-1 | artful | source, amd64, arm64, armhf, i386, ppc64el, s390x sosreport | 3.5-1 | bionic | source, amd64, arm64, armhf, i386, ppc64el, s390x -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1734983 Title: Request to backport sosreport v3.5 Status in sosreport: New Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Trusty: In Progress Status in sosreport source package in Xenial: In Progress Status in sosreport source package in Zesty: In Progress Status in sosreport source package in Artful: In Progress Status in sosreport source package in Bionic: Fix Released Status in sosreport package in Debian: New Bug description: [Impact] Canonical support team (AKA STS) largely depend on sosreport package to troubleshoot system. sosreport is always in constant development including new bugfixes, new features such as new plugins[1], .... that can be interesting to have in a support context. v3.5 is already found in devel release (bionic). We create this LP in the attempt to justify the SRU of v3.5 backport into current supported stable releases. [1] - New plugins for : * perl * boom * vdo * os_net_config * conntrackd * ovirt_imageio * nss * sas3ircu * openstack_aodh * docker_distribution * gluster_block * snappy Plugin API enhancements * Plugin triggers by executable name * Improved log size limit handling * Better handling of compressed log files * Per-plugin package verification lists Updates to 227 plugins This will also allow us to close some sosreport LP bugs: *Docker plugin uses the wrong command for Ubuntu (LP: #1693574) [Test Case] * Install sosreport $ apt-get install sosreport * Run sosreport $ sosreport -a $ sosreport -o <PLUGIN> $ ... * Make sure it generate a tar.xz file in /tmp in the form of "/tmp/sosreport-<HOSTNAME>-<DATE>.tar.xz" * Extract files from archive $ tar Jxvf /tmp/sosreport-<HOSTNAME>-<DATE>.tar.xz * Look the content of sosreport, make sure the information is accurate and valid, .... * Make sure all files that should to be collected by sosreport aren't 0 size. (Files that should be collected may varies from one system to another, it depends on what packages are installed, ...) $ find /tmp/sosreport-<HOSTNAME>-<DATE> -size 0 # Note : It is normal to see some 0 size files here and there, again it depend on how the plugin is run (package detection or not inside the plugins, ...) and if the package is installed or not on the system where you run sosreport. But in most cases, if the package is installed and if sosreport has a plugin for it then it should gather information, if not then it might be a problem with the plugins itself that need adjustments. [Regression Potential] * autopkgtest[2] didn't reveal any [2] - See Comment #1 * We,STS, have intensively tested the package. During our testing, we found a severe regression that we already took action to fix it via : - Upstream issue - https://github.com/sosreport/sos/issues/1155 - Debian bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537 - Fix Released in Ubuntu Devel release (bionic) via debdiff : lp1734983_bionic.debdiff [Other Info] * Sosreport upstream : https://github.com/sosreport/sos * rmadison -u debian,ubuntu sosreport debian: sosreport | 3.2-2 | oldstable | source, amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x sosreport | 3.2-2 | oldstable-kfreebsd | source, kfreebsd-amd64, kfreebsd-i386 sosreport | 3.3+git50-g3c0349b-2 | stable | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x sosreport | 3.5-1 | testing | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x sosreport | 3.5-1 | unstable | source, amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x ubuntu: sosreport | 3.0-1~ubuntu12.04.1 | precise-backports/universe | source, amd64, armel, armhf, i386, powerpc sosreport | 3.1-1ubuntu2 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el sosreport | 3.1-1ubuntu2.2 | trusty-security | source, amd64, arm64, armhf, i386, powerpc, ppc64el sosreport | 3.2-2~ubuntu14.04.1 | trusty-backports | source, amd64, arm64, armhf, i386, powerpc, ppc64el sosreport | 3.2+git276-g7da50d6-3ubuntu1 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x sosreport | 3.3+git50-g3c0349b-2 | zesty | source, amd64, arm64, armhf, i386, ppc64el, s390x sosreport | 3.4-1~ubuntu14.04.1 | trusty-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el sosreport | 3.4-1~ubuntu16.04.1 | xenial-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x sosreport | 3.4-1~ubuntu17.04.1 | zesty-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x sosreport | 3.4-1 | artful | source, amd64, arm64, armhf, i386, ppc64el, s390x sosreport | 3.5-1 | bionic | source, amd64, arm64, armhf, i386, ppc64el, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/sosreport/+bug/1734983/+subscriptions -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
