Resolved the deployer cann't connect to agent error[Fixed Issue#159] #160
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When do deploy micro bosh, there is a deadlock between agent running in stemcell vm and deployer. So, I adjusted the sequence of the deployer process in order that deployer could create & attach volume to stemcell vm first and then waiting for agent done. Also we can change the process in agent, but because of agent is builded in stemcell image, I think it's not a graceful way considering compatibility issue detailis are in #159
|
We received the CLA agreement for Wei Tie and it is now on-file with the project, so any contributions from him may proceed. |
|
Hi TieWie, |
Merge Codes from cloudfoundry/bosh master
The mount disk operation should not be retried, which is not like the agent.ping operation. And this adjustment will ensure the @deployer.renderer.index == total == 11( a retriable step will make this value can't be count)
|
Hi @ajackson , |
|
In #159 Ferran and I found out my mistake of the execution sequence, I dead lock is not exist, close the pull request |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When do deploy micro bosh, there is a deadlock between agent running in
stemcell vm and deployer.
So, I adjusted the sequence of the deployer process in order that
deployer could create & attach volume to stemcell vm first and then
waiting for agent done.
Also we can change the process in agent, but because of agent is
builded in stemcell image, I think it's not a graceful way considering
compatibility
issue detailis are in #159