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

Use cf-rolling-restart over cf-recycle-plugin. #954

Merged
merged 3 commits into from
Feb 13, 2020
Merged

Conversation

adunkman
Copy link
Member

@adunkman adunkman commented Jan 8, 2020

Related to #943.

Rolling-restart is more recently maintained, is the original fork, and works with the latest CF CLI for when we upgrade.

It’s a bit of a shot-in-the-dark here since I don’t 100% understand what’s going on — the cf-recycle-plugin plugin isn’t correctly detecting process restarts. I had thought this was due to conflicting recycle jobs — one job was recycling a process out from the other — but since removing the concurrent jobs, the issue is not fixed.

Looking at this morning’s run, the CircleCI job output seems to indicate that Instance 0 was never restarted, which caused the job to timeout. However, looking at the cell restart logs, we can see that it was correctly restarted:

Timestamp Message
05:09:33.047 Cell 7e7732c4-f516-4420-a8b9-fb94ccea7405 stopping instance f3c7fa65-22e8-4792-7f95-4141
05:09:49.396 Cell 7e7732c4-f516-4420-a8b9-fb94ccea7405 destroying container for instance f3c7fa65-22e8-4792-7f95-4141
05:09:52.034 Cell 7e7732c4-f516-4420-a8b9-fb94ccea7405 successfully destroyed container for instance f3c7fa65-22e8-4792-7f95-4141
05:10:15.651 Cell 7e7732c4-f516-4420-a8b9-fb94ccea7405 creating container for instance 1c8832a7-4445-4c50-55e7-409e
05:10:16.530 Cell 7e7732c4-f516-4420-a8b9-fb94ccea7405 successfully created container for instance 1c8832a7-4445-4c50-55e7-409e
05:10:16.913 Downloading droplet...
05:10:22.451 Downloaded droplet (69.8M)
05:10:22.451 Starting health monitoring of container
05:10:31.906 Container became healthy

This leads me to believe that this is an issue with the plugin — hence the PR. I’m pretty comfortable just trying something newer and seeing if it works, and moving on with our lives if it does. 🤷‍♂

Rolling-restart is more recently maintained, is the original fork, and works with the latest CF CLI for when we upgrade.
@adunkman
Copy link
Member Author

adunkman commented Jan 8, 2020

Oh, forgot to mention — I tested the changes by spinning up 18fgsa/cloud-foundry-cli on my machine and issuing these commands against a sandbox cloud.gov application, which completed successfully.

@codecov-io
Copy link

Codecov Report

Merging #954 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #954   +/-   ##
=======================================
  Coverage   91.45%   91.45%           
=======================================
  Files          39       39           
  Lines        1685     1685           
=======================================
  Hits         1541     1541           
  Misses        144      144

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 742b690...08f5f64. Read the comment docs.

Copy link
Contributor

@cryptofilegsa cryptofilegsa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cleaner - removes unnecessary use of curl. looks good to me.

@adunkman adunkman merged commit 37cf0a5 into master Feb 13, 2020
@adunkman adunkman deleted the use-rolling-restart branch February 13, 2020 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants