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

Fixes #7038: When promises could have been updated, we still have the… #727

Conversation

ncharles
Copy link
Member

… error messages saying we couldn't update promises

… error messages saying we couldn't update promises
repair_timeout => { "${else}" };

cancel_kept => { "${else}" };
cancel_repaired => { "${else}" };
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't there be "${if}" in cancel_kept and "${kept}" too in cancel_repaired ?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm not sure it would be relevant. If we cancel the repaired class as well, we'll most likely hide the update that occured, and user may scratch their head on why promises are updated, but report kept

Copy link
Member

Choose a reason for hiding this comment

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

So we'll report both a kept and repaired status ?

Copy link
Member Author

Choose a reason for hiding this comment

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

no, the code is clever, and report the worse state (repaired in case of success and repaired, error in case of repaired and error, etc)

Copy link
Member

Choose a reason for hiding this comment

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

OK

@peckpeck
Copy link
Member

Merging

peckpeck added a commit that referenced this pull request Jul 28, 2015
…ve_been_updated_we_still_have_the_error_messages_saying_we_couldn_t_update_promises

Fixes #7038: When promises could have been updated, we still have the…
@peckpeck peckpeck merged commit 264e767 into Normation:branches/rudder/2.11 Jul 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants