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

Functional improvements needed to VCH endpoint restart policy #2099

Open
kjplatz opened this issue Aug 23, 2016 · 3 comments
Open

Functional improvements needed to VCH endpoint restart policy #2099

kjplatz opened this issue Aug 23, 2016 · 3 comments
Labels
component/portlayer kind/defect Behavior that is inconsistent with what's intended severity/4-minor Low usability or functional impact. Often has an easy workaround.

Comments

@kjplatz
Copy link

kjplatz commented Aug 23, 2016

Test setup:

  1. Login to VCH appliance
  2. Remove/rename /sbin/port-layer-server
  3. Kill the port-layer-server

(Note: this works with the docker-engine-server and the vicadmin processes as well)
Expected behavior:
System attempts to restart a finite number of times, and then reports an error, leaving the VCH up and running in order to download logs

Actual behavior:
VCH immediately reboots.
@mdubya66 mdubya66 added this to the VIC GA Release milestone Sep 5, 2016
@mdubya66 mdubya66 added the kind/defect Behavior that is inconsistent with what's intended label Sep 5, 2016
@mdubya66 mdubya66 added the impact/doc/note Requires creation of or changes to an official release note label Sep 20, 2016
@mdubya66 mdubya66 removed this from the VIC GA Release milestone Sep 20, 2016
@mdubya66
Copy link
Contributor

Moving to Icebox per 9/20 Triage

@stuclem
Copy link
Contributor

stuclem commented Nov 7, 2016

Already in the release notes, so removing the kind/note tag.

@kjplatz kjplatz removed the impact/doc/note Requires creation of or changes to an official release note label Nov 7, 2016
@sgairo sgairo removed their assignment Jan 18, 2017
@chengwang86 chengwang86 self-assigned this Jan 18, 2017
@hickeng
Copy link
Member

hickeng commented Jan 18, 2017

Immediately rebooting is intentional to attempt to restore function - this should look into:

  • marking the VCH as having had a failure of some kind
  • suppressing subsequent restarts if the first restart was not beneficial
  • suppressing restart at all if deployed with debug

@corrieb corrieb changed the title VCH restarts if required process cannot be restarted. Functional improvements needed to VCH endpoint restart policy Jul 19, 2017
@zjs zjs added component/portlayer severity/4-minor Low usability or functional impact. Often has an easy workaround. and removed priority/p2 labels Mar 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/portlayer kind/defect Behavior that is inconsistent with what's intended severity/4-minor Low usability or functional impact. Often has an easy workaround.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@zjs @hickeng @kjplatz @mdubya66 @stuclem @sgairo @chengwang86