Support dump
TechPreview
Support dump described in this section specifically targets OpenStack components, providing valuable insights for troubleshooting OpenStack-related problems.
To generate a support dump for your MOSK environment,
use the osctl sos report tool present within the rockoon
image.
This section focuses only on the essential capabilities of the tool. For all available parameters, consult osctl sos report --help.
Collectors
The support dump is modular. Each module is responsible for specific
functionality. To enable or disable specific modules during support
dump creation, use the --collector option. If not specified,
all collectors are used.
Components
Given the substantial amount of information, you can manage the components
included in a support dump using the mutually exclusive --component
or --all-components options. Within the elastic collector component,
you can specify which loggers to gather logs for. For example,
the --component nova option restricts log collection to pods related
to Nova, which names start with nova-* and libvirt-*.
Hosts
Another filtering criterion involves specifying the host for which you intend
to collect support information. This can be accomplished through the use of
mutually exclusive --host or --all-hosts options. This feature is
particularly valuable for limiting the volume of data included in
the support dump.
Modes
Support dump works in the following modes:
reportGeneric report is created, no specific information such as resource UUID is included. The tool collects as much information as possible.
traceProvides more sophisticated filtering criteria rather than the
reportmode. For example, you can search for specific message patterns in OpenSearch.
Usage
You can execute the osctl sos commands directly in the rockoon
pod. For example:
kubectl -n osh-system exec -it deployment/rockoon bash
osctl sos --since 1d \
--all-hosts \
--component neutron \
--collector elastic \
--workspace /tmp/ report
To get trace for a specific resource UUID in Neutron for a specific host, use the following command as an example:
kubectl -n osh-system exec -it deployment/rockoon bash
osctl sos --since 1d \
--host kaas-node-fe0734de-20e8-4493-9f7d-52c4f8a8a98c \
--component neutron \
--workspace /workspace/ \
--collector elastic trace --message ".4a055675-89b0-45c2-a3b3-a10dffa07f31."