-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
must-gather/sosreport support
-
False
-
-
False
-
OSPRH-811Red Hat OpenStack 18.0 Greenfield Deployment
-
Committed
-
Committed
-
To Do
-
OSPRH-811 - Red Hat OpenStack 18.0 Greenfield Deployment
-
openstack-must-gather-container-1.0.0-46
-
Committed
-
Committed
-
0% To Do, 0% In Progress, 100% Done
-
-
Enhancement
-
Done
-
Rejected
-
-
-
Approved
In the podified world the way we must gather our SOS reports will greatly differ:
- Control Plane Services can be spread across many OpenShift nodes.
- For some services we may require little information (API service) while for others we may require a lot including kernel messages from the host (cinder volume).
- We will require both OpenShift and OSP information
- Logging for OpenStack services will be retrieved differently
We need to ensure we have a well define mechanism and procedure to gather the right SOS reports before our first customer case comes in.
Related links:
Documentation to test the tool is available since DP2 and specifically, from DP3 it is at: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/18.0-dev-preview/html/deploying_red_hat_openstack_platform_18.0_development_preview_3_on_red_hat_openshift_container_platform/assembly_collecting-diagnostic-information-for-support
- depends on
-
OSPRH-131 As a cloud operator, i want all service log generated by openstack on OpenstackDataplaneNodes to be stored in the systemd journal
- Closed