-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support bundle of integrated OVA should collect Admiral logs #225
Comments
Is this something I need to do or will this be functionality in Admiral? |
This is not part of Admiral functionality. I am not aware how support bundle is created, but it should collect Admiral's container logs. |
Let's make sure the Harbor logs and the logs for new components that are introduced in 1.2 are also collected as part of the support bundle. |
Workaround is to manually collect the logs off of Admiral |
This needs to be prioritized for 1.3 or beyond? @karthik-narayan |
Added a pretty pitiful release note in https://github.com/vmware/vic-product/releases/tag/v1.2.0. @angel-ivanov and @andrewtchin how do we a) download the OVA support bundle in the first place and b) download the Admiral logs manually? This really needs to go in the core doc too: #318 |
Here's the release note entry:
|
Repurposing this story to cover creating the support bundle and making sure all logs are under |
@andrewtchin is the release note above OK? Thanks! |
@stuclem release note lgtm |
Thanks @andrewtchin ! |
Closing this as we have an alternative method for gathering all appliance state information #1197 |
@andrewtchin do we need to keep the release note entry about this from 1.3.0 in the 1.3.1 release notes? |
No, the release note can be removed as in 1.3.1 we have the |
Support bundle should collect Admiral container(vic-admiral) logs.
Also it might be useful if logs of the docker which is running in the integrated OVA, to be collected too for more debugging information.
The text was updated successfully, but these errors were encountered: