Skip to content
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

Closed
angel-ivanov opened this issue May 16, 2017 · 14 comments
Closed

Support bundle of integrated OVA should collect Admiral logs #225

angel-ivanov opened this issue May 16, 2017 · 14 comments
Labels
kind/enhancement Behavior that was intended, but we want to make better product/ova Related to the OVA packaging of vSphere Integrated Containers

Comments

@angel-ivanov
Copy link

angel-ivanov commented May 16, 2017

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.

@andrewtchin
Copy link
Contributor

Is this something I need to do or will this be functionality in Admiral?

@angel-ivanov
Copy link
Author

This is not part of Admiral functionality. I am not aware how support bundle is created, but it should collect Admiral's container logs.

@bradmeiseles
Copy link

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.

@andrewtchin andrewtchin added the impact/doc/note Requires creation of or changes to an official release note label May 25, 2017
@andrewtchin
Copy link
Contributor

Workaround is to manually collect the logs off of Admiral
See also vmware/vic#4680

@mdubya66
Copy link
Contributor

This needs to be prioritized for 1.3 or beyond? @karthik-narayan

@stuclem
Copy link
Contributor

stuclem commented Sep 12, 2017

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

@stuclem
Copy link
Contributor

stuclem commented Sep 12, 2017

Here's the release note entry:


  • vSphere Integrated Containers appliance support bundle does not include Management Portal logs. #225
    Workaround: Download the Management Portal logs manually.

@andrewtchin
Copy link
Contributor

andrewtchin commented Sep 12, 2017

Repurposing this story to cover creating the support bundle and making sure all logs are under /var/log/vmware
vmware/vic#4680 and vmware/vic#5265 can probably also be closed when this is resolved
We need to get the admiral logs off of the container
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010705

@stuclem
Copy link
Contributor

stuclem commented Sep 13, 2017

@andrewtchin is the release note above OK? Thanks!

@andrewtchin
Copy link
Contributor

@stuclem release note lgtm

@stuclem
Copy link
Contributor

stuclem commented Sep 18, 2017

Thanks @andrewtchin !

@stuclem stuclem removed the impact/doc/note Requires creation of or changes to an official release note label Sep 18, 2017
@andrewtchin
Copy link
Contributor

Closing this as we have an alternative method for gathering all appliance state information #1197

@stuclem
Copy link
Contributor

stuclem commented Feb 6, 2018

@andrewtchin do we need to keep the release note entry about this from 1.3.0 in the 1.3.1 release notes?

@andrewtchin
Copy link
Contributor

No, the release note can be removed as in 1.3.1 we have the appliance-support.sh script

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Behavior that was intended, but we want to make better product/ova Related to the OVA packaging of vSphere Integrated Containers
Projects
None yet
Development

No branches or pull requests

5 participants