I verified the new Docker plugin fix in sosreport 3.5-1 in -proposed and
everything is fine now. No more docker plugin errors in sos_logs and no
errors in the output, and I verified the data collected looks good:
trusty: sosreport 3.5-1~ubuntu14.04.2
# ls
Hello Eric, or anyone else affected,
Accepted sosreport into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/sosreport/3.5-1~ubuntu16.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Eric, or anyone else affected,
Accepted sosreport into artful-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/sosreport/3.5-1~ubuntu17.10.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Mark the bug to verification-failed-$RELEASE for now until the Docker
plugin fix land in -proposed.
- Eric
** Changed in: sosreport (Ubuntu Trusty)
Status: Fix Committed => In Progress
** Changed in: sosreport (Ubuntu Xenial)
Status: Fix Committed => In Progress
** Changed in:
Fix minor regression in Docker plugin (explained in comment #20) for
Trusty [lp1734983-trusty-docker.debdiff]
** Patch added: "lp1734983-trusty-docker.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1734983/+attachment/5043143/+files/lp1734983-trusty-docker.debdiff
--
You
Fix minor regression in Docker plugin (explained in comment #20) for
Xenial [lp1734983-xenial-docker.debdiff]
** Patch added: "lp1734983-xenial-docker.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1734983/+attachment/5043142/+files/lp1734983-xenial-docker.debdiff
--
You
lp1734983-bionic-docker.debdiff
** Patch added: "lp1734983-bionic-docker.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1734983/+attachment/5040994/+files/lp1734983-bionic-docker.debdiff
--
You received this bug notification because you are a member of STS
Sponsors, which
lp1734983-bionic-docker-plugin.debdiff
--
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
1 minor regression found in the docker plugin execution.
-
When running soreport with docker installed we get an exception in the plugin
as follow :
...
Setting up archive ...
Setting up plugins
Ran 3.5 version for Trusty, Xenial, and Artful on a VM that was MAAS-
deployed. I have not been able to discover any issues. I also installed
it on a bare-metal server running Xenial with no problems as well.
--
You received this bug notification because you are a member of STS
Sponsors, which
Ran 3.5 version for Trusty, Xenial, and Artful. No problems appear to
have been introduced by this version.
--
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
Marked Zesty as invalid as it reached end of like on Jan 13 2018.
** Changed in: sosreport (Ubuntu Zesty)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
Testing done for Trusty, Xenial and Arful with no errors noticed.
--
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:
Hello Eric, or anyone else affected,
Accepted sosreport into artful-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/sosreport/3.5-1~ubuntu17.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
sil2100 has rejected the first upload and kept the second which include
the (LP: #X) syntax in d/changelog.
Things are a bit blocked everywhere. Accepting the uploads now will do
nothing as we have no builders. sil2100 will review the uploads later
when there will be some builders available.
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: #) syntax in
v3.5 sponsored for AZXT, waiting for SRU verification team to approve to
start building in -proposed.
- Eric
--
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
Here's the debdiff fixing the regression found by Bryan Quigley.
I talked with the SRU team and it is okay to proceed with the upload of
this fix in Devel and Stable release if waiting too long for upstream to
merge.
In this case, the fix will likely be merge in April 2018 for v3.6, and
by then
** Description changed:
*** DRAFT in progress ***
[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
** Changed in: sosreport
Status: Unknown => New
--
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
** Also affects: sosreport via
https://github.com/sosreport/sos/issues/1155
Importance: Unknown
Status: Unknown
** Description changed:
*** DRAFT in progress ***
[Impact]
Canonical support team (AKA STS) largely depend on sosreport package to
troubleshoot system.
Upstream issue - https://github.com/sosreport/sos/issues/1155
** Bug watch added: github.com/sosreport/sos/issues #1155
https://github.com/sosreport/sos/issues/1155
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
Seems like something is broken in the "package=" mechanism behaviour.
The no longer running plugins that we have identified coincide with recent
package add commit :
18ab068 [dbus] add missing packages list
3d0ea25 [cron] add missing packages list
0348833 [acpid] add missing packages list
Found a severe regression in that it appears many packages = lines no
longer work which prevent automatic package detection. Bionic is also
affected.
This in an upstream issue and investigating is ongoing.
--
You received this bug notification because you are a member of STS
Sponsors, which is
I can reproduce the situation as well with sosreport upstream and v3.5
debian package that I have built for pre-SRU testing.
Example:
Plugin such as [acpid], [boot], ... are no longer running with 'sosreport -a'
even if "packages=" are installed.
Let's put the SRU on hold until we or upstream
** Description changed:
*** DRAFT in progress ***
[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
26 matches
Mail list logo
