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.

Sign up for GitHub

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

Jump to bottom

vic-admin should work even it can't speak to vsphere. #3082

Closed
mlh78750 opened this issue Nov 9, 2016 · 4 comments
Closed

vic-admin should work even it can't speak to vsphere. #3082

mlh78750 opened this issue Nov 9, 2016 · 4 comments
Labels
area/appliance component/vicadmin impact/test/integration Requires creation of or changes to an integration test kind/defect Behavior that is inconsistent with what's intended source/customer Reported by a customer, directly or via an intermediary

Comments

@mlh78750
Copy link
Contributor

mlh78750 commented Nov 9, 2016

When the customer hit #3081 the port layer would just quit when it couldn't connect to the target. tether/vic-init would restart it and it would just quit again. During this time you could connect to vic-admin but it never returned any data. When the rest of the system is not working we need vic-admin the most. See also #3079.
@mlh78750 mlh78750 added area/appliance component/vicadmin kind/defect Behavior that is inconsistent with what's intended source/customer Reported by a customer, directly or via an intermediary kind/quality impact/test/integration Requires creation of or changes to an integration test labels Nov 9, 2016
@mlh78750
Copy link
Contributor Author

mlh78750 commented Nov 9, 2016

@corrieb reports that when he was in a similar situation it did work.

@mlh78750 mlh78750 changed the title vic-admin should work even if portlayer is in a panic loop vic-admin should work even it can't speak to vsphere. Nov 9, 2016
@mlh78750
Copy link
Contributor Author

mlh78750 commented Nov 9, 2016

Turns out the log show that vic-admin was crashing from it's inability to reach vsphere. Dup of #2811.

@mlh78750 mlh78750 closed this as completed Nov 9, 2016
@anchal-agrawal
Copy link
Contributor

@mlh78750 Those logs would be very helpful to ensure that I'm addressing this particular issue as part of #2811. Do we still have access to them?

@mlh78750
Copy link
Contributor Author

logs.zip

@mlh78750 mlh78750 mentioned this issue Nov 10, 2016
Closed
@anchal-agrawal anchal-agrawal mentioned this issue Nov 11, 2016
Merged
@anchal-agrawal anchal-agrawal mentioned this issue Jan 5, 2017
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/appliance component/vicadmin impact/test/integration Requires creation of or changes to an integration test kind/defect Behavior that is inconsistent with what's intended source/customer Reported by a customer, directly or via an intermediary
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@anchal-agrawal @mlh78750