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

bf: ZENKO-147 Check site when setting failed hash #267

Merged
merged 1 commit into from
Apr 24, 2018

Conversation

bennettbuchanan
Copy link

@bennettbuchanan bennettbuchanan commented Apr 23, 2018

Now that we have a single replication status processor so that operations occur sequentially, the replicationInfo backends may contain a 'FAILED' status from a previous operation. This change ensures that the failure hash field is set only once.

I will aim to get https://github.com/scality/Integration/pull/660 merged to avoid this kind of unexpected problem going forward.

@ironman-machine
Copy link
Contributor

PR has been updated. Reviewers, please be cautious.

@bennettbuchanan
Copy link
Author

@ironman-machine
RUN_BACKBEAT_CRR_TESTS=true
try

@ironman-machine
Copy link
Contributor

Hello @bennettbuchanan

"RUN_BACKBEAT_CRR_TESTS=true": Success
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/21463' with the following env. args:

{
    "RUN_BACKBEAT_CRR_TESTS": "true",
    "DEFAULT_BRANCH": "master",
    "SCALITY_INTEGRATION_BRANCH": "ultron/master",
    "REPO_NAME": "backbeat",
    "SCALITY_BACKBEAT_BRANCH": "bf/ZENKO-147/setFailedFieldSite"
}

@jonathan-gramain jonathan-gramain merged commit fcb0d61 into master Apr 24, 2018
@jonathan-gramain jonathan-gramain deleted the bf/ZENKO-147/setFailedFieldSite branch April 24, 2018 18:48
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