** Description changed:
[Impact]
sosreport 3.6 has been released in June 2018 with further enhancements
in core sosreport functionality.
I already did the request for debian :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818
and 3.6 has been uploaded in Debian since
** Tags removed: verification-needed-bionic verification-needed-cosmic
verification-needed-xenial
** Tags added: verification-done-bionic verification-done-cosmic
verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Bryan Quigley (bryanquigley) ,
Today's new upload should address the bug you experienced. (I have tested
myself pre-upload)
Could you give it a try as well ? and provide feedback ?
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: sos36
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775195
Title:
[sync][sru]sosreport v3.6
To manage notifications about this bug go to:
** Description changed:
[Impact]
sosreport 3.6 has been released in June 2018 with further enhancements
in core sosreport functionality.
I already did the request for debian :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818
and 3.6 has been uploaded in Debian since
Bug #1803735 has been reported to track the kernel plugin bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775195
Title:
[sync][sru]sosreport v3.6
To manage notifications about this bug go to:
[d6379b5ba0f381ea8ec2403b9985100a946a5866] fix has been push into disco,
stable release will follow soon.
Thanks Bryan.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775195
Title:
I was able to reproduce the situation and did a kernel bisection to
confirm, and it reveals that you were right :
$ git bisect log
...
# first fixed commit: [d6379b5ba0f381ea8ec2403b9985100a946a5866] [kernel] dont
collect some tracing instance files
I test the above commit on Cosmic and
I'm on 18.04 (I would assume this would not affect older releases)
I previously installed rasdaemon and started it. That's all it took to
trigger it on Fedora - https://github.com/sosreport/sos/pull/1445
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(I would assume this would not affect older releases ... as they use
mcelog not rasdaemon.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775195
Title:
[sync][sru]sosreport v3.6
To manage
Bryan,
How did you manage to trigger the hang ? and on which release(s) ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775195
Title:
[sync][sru]sosreport v3.6
To manage notifications about
[ VERIFICATION COSMIC ]
libvirt VM:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.10
DISTRIB_CODENAME=cosmic
DISTRIB_DESCRIPTION="Ubuntu 18.10"
$ dpkg -l | grep sosreport
ii sosreport 3.6-1ubuntu0.18.10.1
amd64Set of tools to
[ VERIFICATION XENIAL ]
libvirt VM:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"
$ dpkg -l | grep sosreport
ii sosreport 3.6-1ubuntu0.16.04.1
amd64Set of
[ VERIFICATION BIONIC ]
Bare metal:
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
$ dpkg -l | grep sosreport
ii sosreport 3.6-1ubuntu0.18.04.1
amd64
Eric, unfortunately - I'm getting a hang in kernel now - I installed
rasdaemon to debug a customer case... between when I tested last...
I believe it's fixed by
https://github.com/sosreport/sos/commit/d6379b5ba0f381ea8ec2403b9985100a946a5866
--
You received this bug notification because you are
[VERIFICATION COSMIC]
I ran sosreport '3.6-1ubuntu0.18.10.1' inside a baremetal AND a
container without any issue.
The test was run with '-a, --alloptions'[1] AND '--all-logs'[2]
[1] - Boolean that set to True for all enabled plugins.
[2] - Tell sosreport to collect all possible log data
Correction I for my above statement ^ I I ran sosreport
'3.6-1ubuntu0.16.04.1' for Xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775195
Title:
[sync][sru]sosreport v3.6
To manage
[VERIFICATION XENIAL]
I ran sosreport '3.6-1ubuntu0.18.04.1' inside a baremetal AND a
container without any issue.
The test was run with '-a, --alloptions'[1] AND '--all-logs'[2]
[1] - Boolean that set to True for all enabled plugins.
[2] - Tell sosreport to collect all possible log data
** Description changed:
[Impact]
sosreport 3.6 has been released in June 2018 with further enhancements
in core sosreport functionality.
I already did the request for debian :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818
and 3.6 has been uploaded in Debian since
[VERIFICATION BIONIC]
# Part 2
I also took another look at the sensible data substitution, and works as
expected :
etc/ssl/openssl.cnf:# input_password = **
etc/ssl/openssl.cnf:# output_password = **
etc/ssl/openssl.cnf:challengePassword = **
[VERIFICATION BIONIC]
I ran sosreport '3.6-1ubuntu0.18.04.1' inside a baremetal AND a
container without any issue.
The test was run with '-a, --alloptions'[1] AND '--all-logs'[2]
[1] - Boolean that set to True for all enabled plugins.
[2] - Tell sosreport to collect all possible log data
Hello Eric, or anyone else affected,
Accepted sosreport into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/sosreport/3.6-1ubuntu0.18.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Fix has been push into Disco.
sosreport v3.6, is now waiting in the upload queue for C/B/X.
Thanks all for your testing !
I will need testing again during the testing phase in $RELEASE-proposed.
- Eric
** Changed in: sosreport (Ubuntu Trusty)
Status: In Progress => Won't Fix
--
You
Hi Eric,
I confirm with the sosreport in ppa:slashd/lp1775195 I no longer see the
passwords anymore:
# grep password
sosreport-xeniallandscape-20181114150420/etc/landscape/service.conf
password = []
password = []
store_password = []
I couldn't find any other issues with
On my side, it looks good now using the package I have just built found
on "ppa:slashd/lp1775195"
$ sosreport -o landscape
$ cd /tmp
$ tar Jxvf sosreport-lds-20181113210218.tar.xz
$ grep -i password sosreport-lds-20181113210218/etc/landscape/service.conf
password = []
password =
I have re-package w/ the upstream fix to address the substitution method
failure :
Can you give it a try and let me know the outcome ?
sudo add-apt-repository ppa:slashd/lp1775195
sudo apt-get update
Regards,
Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
[Impact]
sosreport 3.6 has been released in June 2018 with further enhancements
in core sosreport functionality.
I already did the request for debian :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818
and 3.6 has been uploaded in Debian since
Hi Dave,
You are right, after a bisection from upstream code, I found the necessary fix
to address this situation:
https://github.com/sosreport/sos/commit/b96bdab03f06408e162b1733b20e8ba9fbf8e012
I'll re-package, and would appreciate you to test again.
** Description changed:
[Impact]
** Description changed:
[Impact]
sosreport 3.6 has been released in June 2018 with further enhancements
in core sosreport functionality.
I already did the request for debian :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818
and 3.6 has been uploaded in Debian since
I'm setting this to Incomplete based on comment #6 and the possibility
of a password being leaked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775195
Title:
[sync][sru]sosreport v3.6
To manage
I'm setting this to Incomplete based on comment #6 and the possibility
of a password being leaked.
** Changed in: sosreport (Ubuntu Cosmic)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ran test in Xenial LXD container:
# dpkg -l | grep sosreport
ii sosreport3.6-1ubuntu0.16.04.1
amd64Set of tools to gather troubleshooting data from
a system
# apt-cache policy sosreport
sosreport:
Installed:
** Description changed:
[Impact]
sosreport 3.6 has been released in June 2018 with further enhancements
in core sosreport functionality.
I already did the request for debian :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818
and 3.6 has been uploaded in Debian since
** Description changed:
[Impact]
sosreport 3.6 has been released in June 2018 with further enhancements
in core sosreport functionality.
I already did the request for debian :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818
and 3.6 has been uploaded in Debian since
** Description changed:
[Impact]
sosreport 3.6 has been released in June 2018 with further enhancements
in core sosreport functionality.
I already did the request for debian :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818
and 3.6 has been uploaded in Debian since
Testing results:
LXD containers:
Xenial: ran and created an output file that looked fine. It outputted a single
seemingly harmless error during run: [plugin:kvm] debugfs not mounted and mount
attempt failed
Bionic: ran with no errors, output file appeared fine
Cosmic: ran with no errors, output
** Description changed:
[Impact]
sosreport 3.6 has been released in June 2018 with further enhancements
in core sosreport functionality.
I already did the request for debian :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818
and 3.6 has been uploaded in Debian since
** Description changed:
[Impact]
sosreport 3.6 has been released in June 2018 with further enhancements
in core sosreport functionality.
I already did the request for debian :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818
and 3.6 has been uploaded in Debian since
I ran sosreport -a on bionic with maas 2.4, corosync, pacemaker and
postgres all in a very unhappy state. The output looks good. During
execution I recieved the following:
[plugin:pacemaker] crm_from parameter 'True' is not a valid date: using
default
A couple of minor notes from the output:
** Changed in: sosreport (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu Trusty)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu Bionic)
Status: New => In Progress
** Changed in: sosreport
** Changed in: sosreport (Ubuntu Bionic)
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/1775195
Title:
[sync][sru]sosreport v3.6
To manage
** Description changed:
+ ## SRU JUSTIFICATION ##
+ ## DRAFT ##
+
+ [Impact]
+
sosreport 3.6 has been released in June 2018 with further enhancements
in core sosreport functionality.
A sync can be done since all Ubuntu patches has been integrated in 3.6
I already did the request
** Changed in: sosreport (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775195
Title:
[sync][sru]sosreport v3.6
To manage notifications about this bug
43 matches
Mail list logo
