17.4.472. drpcli support bundle

Create a support bundle for the RackN engineering team.

17.4.472.1. Synopsis

Create a support bundle for the RackN engineering team. This command is currently only supported on a Linux host and expects to be running on the drp endpoint.

By default the command will run:
    journalctl -u dr-provision --since yesterday
It captures that output and puts it into a file.
Next we take the contents of /var/lib/dr-provision
excluding some folders and add them along with the
log output to a zip file that can be sent to support@rackn.com

If your drp endpoint runs as some other user you can set the user with the --dr-user flag.
If your drp endpoint has a different base dir than /var/lib/dr-provision
you can set that with the --drp-basedir flag.
If you need to include additional directories that are excluded by default above
you can add them with  --extra-dirs This is only needed if directed by support.
drpcli support bundle [flags]

17.4.472.2. Options

    --dr-user string       dr-user dr-provision (default "dr-provision")
    --drp-basedir string   drp-basedir /var/lib/dr-provision (default "/var/lib/dr-provision/")
    --extra-dirs string    extra-dirs job-logs,saas-content,ux,plugins
-h, --help                 help for bundle
    --since string         since 'something valid that journalctl supports' (default "yesterday")

17.4.472.3. Options inherited from parent commands

-c, --catalog string          The catalog file to use to get product information (default "https://repo.rackn.io")
-C, --colors string           The colors for JSON and Table/Text colorization.  8 values in the for 0=val,val;1=val,val2... (default "0=32;1=33;2=36;3=90;4=34,1;5=35;6=95;7=32;8=92")
-d, --debug                   Whether the CLI should run in debug mode
-D, --download-proxy string   HTTP Proxy to use for downloading catalog and content
-E, --endpoint string         The Digital Rebar Provision API endpoint to talk to (default "https://127.0.0.1:8092")
-X, --exit-early              Cause drpcli to exit if a command results in an object that has errors
-f, --force                   When needed, attempt to force the operation - used on some update/patch calls
-F, --format string           The serialization we expect for output.  Can be "json" or "yaml" or "text" or "table" (default "json")
-N, --no-color                Whether the CLI should output colorized strings
-H, --no-header               Should header be shown in "text" or "table" mode
-x, --no-token                Do not use token auth or token cache
-P, --password string         password of the Digital Rebar Provision user (default "r0cketsk8ts")
-J, --print-fields string     The fields of the object to display in "text" or "table" mode. Comma separated
-r, --ref string              A reference object for update commands that can be a file name, yaml, or json blob
-T, --token string            token of the Digital Rebar Provision access
-t, --trace string            The log level API requests should be logged at on the server side
-Z, --trace-token string      A token that individual traced requests should report in the server logs
-j, --truncate-length int     Truncate columns at this length (default 40)
-u, --url-proxy string        URL Proxy for passing actions through another DRP
-U, --username string         Name of the Digital Rebar Provision user to talk to (default "rocketskates")

17.4.472.4. SEE ALSO