lp:sosreport

Created by Adam Stokes on 2013-04-17 and last modified on 2020-02-19
Get this branch:
bzr branch lp:sosreport

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
sosreport
Project:
sosreport
Status:
Development

Import details

Import Status: Reviewed

This branch is an import of the HEAD branch of the Git repository at git://github.com/sosreport/sosreport.git.

The next import is scheduled to run in 5 hours.

Last successful import was 15 minutes ago.

Import started 15 minutes ago on alnitak and finished 15 minutes ago taking 20 seconds — see the log
Import started 6 hours ago on alnitak and finished 6 hours ago taking 20 seconds — see the log
Import started 12 hours ago on alnitak and finished 12 hours ago taking 20 seconds — see the log
Import started 18 hours ago on alnitak and finished 18 hours ago taking 20 seconds — see the log
Import started on 2020-02-22 on alnitak and finished on 2020-02-22 taking 20 seconds — see the log
Import started on 2020-02-22 on alnitak and finished on 2020-02-22 taking 20 seconds — see the log
Import started on 2020-02-22 on alnitak and finished on 2020-02-22 taking 20 seconds — see the log
Import started on 2020-02-21 on alnitak and finished on 2020-02-21 taking 25 seconds — see the log
Import started on 2020-02-21 on alnitak and finished on 2020-02-21 taking 20 seconds — see the log
Import started on 2020-02-21 on alnitak and finished on 2020-02-21 taking 25 seconds — see the log

Recent revisions

3029. By Jan Jansky <email address hidden> on 2020-02-19

[networking] namespace pattern fix

Fixing pattern from using * to .* and also adding
$ on end of each namespace.

For example:
if you have namespaces
test1 test11 test2 test3 test333 and will use
-k networking.namespace_pattern="test3 test1*"
pattern will result as (?:test3$|test1.*$) and
only test3, test1 and test11 will be used.

Before this fix with same namespaces as
above and same input parameter pattern will
result as (?:test3|test1*)
because of * instead of .* also test2 will be
used and because of mising $ also test333
will be used.

Input parameter using same syntax as before
"ens* eth* test1 test5", * is wildcard in this
case.

Resolves: #1961

Signed-off-by: Jan Jansky <email address hidden>
Signed-off-by: Jake Hunsaker <email address hidden>

3028. By Bryn M. Reeves <email address hidden> on 2020-02-14

[sos] bump release

Signed-off-by: Bryn M. Reeves <email address hidden>

3027. By Jake Hunsaker <email address hidden> on 2020-02-14

[man] Update manpage for --upload and related options

Adds manage entries for the various --upload options added as part of
the previous patches adding upload functionality.

Signed-off-by: Jake Hunsaker <email address hidden>

3026. By Jake Hunsaker <email address hidden> on 2020-02-14

[Policies] Fix case id being overridden by blank input

Previously if `--case-id` was specific, and a user provided a blank
input for the case-id prompt (when `--batch` isn't used), this would
override the case id to be blank.

Now we properly default to `--caseid` if it is provided if a user
doesn't provide it again for the actual prompt.

Signed-off-by: Jake Hunsaker <email address hidden>

3025. By Jake Hunsaker <email address hidden> on 2020-02-14

[ubuntu] Add Canonical Support file upload functionality

This commit adds the needed bits to allow sos users on Ubuntu systems to
upload to the Canonical Support File Server as part of PR #1911.

Signed-off-by: Jake Hunsaker <email address hidden>

3024. By Jake Hunsaker <email address hidden> on 2020-02-14

[redhat] Add ability to upload to customer cases

Adds the ability to the Red Hat policy for users to upload archives
directly to existing technical support cases on the Red Hat Customer
Portal.

If a case number is provided, uploading to the case is the
preferred/default option the policy will take. If `--upload-user` is not
provided, users will be prompted for one as well as the password for the
Customer Portal account. Note that Red Hat's case management API
requires that the user credentials provided here have access to the case
number referenced on the Customer Portal.

If a case number is not provided, or if one is provided but Customer
Portal credentials are not provided, the policy will fallback to using
the public dropbox location for upload.

Signed-off-by: Jake Hunsaker <email address hidden>

3023. By Jake Hunsaker <email address hidden> on 2020-02-14

[redhat] Define policy-default FTP location and credentials

Adds connection and authentication defaults to the Red Hat policy to use
the publicly available dropbox that Red Hat Global Support Services
makes available for support cases.

Signed-off-by: Jake Hunsaker <email address hidden>

3022. By Jake Hunsaker <email address hidden> on 2020-02-14

[sosreport|Policy] Add ability to upload archive

Adds the option to automatically upload a generated sosreport archive to
a provided location such as HTTPS or FTP servers.

Using --upload will use policy-defined defaults (if available) to upload
to a specific vendor's defined location.

Otherwise, users may supply --upload-url, --upload-directory,
--upload-user, and --upload-pass to specify a custom location/server,
directory on that server, and authentication credentials.

Resolves: #1911

Signed-off-by: Jake Hunsaker <email address hidden>

3021. By Kyle Walker <email address hidden> on 2020-02-14

[yum] Add "yum -C repolist --verbose" command output

Following the upstream DNF commit below, the "yum -C repolist" command
output will no longer include package count information:

    c4f57476 Do not load metadata for repolist commands...

This information is helpful for those searching for client-side
mismatches to upstream repositories. Such as in the case of two
repositories, where one is missing content that another includes, this
information can be crucial for determinining the source of the problem.

This change includes a "yum -C repolist --verbose" command in the
resulting sosreport which includes information such as the following:

   Repo-id : <repoid>
   Repo-name : <full reponame>
   Repo-revision : <version>
   Repo-updated : <datestamp>
   Repo-pkgs : <total repo package count>
   Repo-available-pkgs: <package count>
   Repo-size : <size>
   Repo-baseurl : <url>
   Repo-expire : <datestamp>
   Repo-filename : <path>

Resolves: #1951

Signed-off-by: Kyle Walker <email address hidden>
Signed-off-by: Bryn M. Reeves <email address hidden>

3020. By Jan Jansky <email address hidden> on 2020-02-14

[archive] handle OSErrors

If file/folder will be present during file list creation, but will be
missing during collection OSError will throw exception

FileNotFoundError: [Errno 2] No such file or directory

Added handling of OSError into sos/archive.py and new log message with
info level to sos_logs/sos.log

Resolves: #1890

Signed-off-by: Jan Jansky <email address hidden>
Signed-off-by: Bryn M. Reeves <email address hidden>

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.

Subscribers