Skip to content
This repository has been archived by the owner on Jul 25, 2022. It is now read-only.

Fix client mount in run_stratagem #2085

Merged
merged 2 commits into from
Jul 20, 2020
Merged

Conversation

ip1981
Copy link
Member

@ip1981 ip1981 commented Jul 17, 2020

Ref: f10ba6b

Closes #2084.

Signed-off-by: Igor Pashev pashev.igor@gmail.com


This change is Reviewable

Ref: f10ba6b

Signed-off-by: Igor Pashev <pashev.igor@gmail.com>
@ip1981 ip1981 added the bug label Jul 17, 2020
@ip1981 ip1981 requested a review from a team July 17, 2020 12:59
@ip1981 ip1981 self-assigned this Jul 17, 2020
@jgrund
Copy link
Member

jgrund commented Jul 17, 2020

This made it into the 6.1 release, so it will need to be backported there as well

Copy link
Member

@jgrund jgrund left a comment

Choose a reason for hiding this comment

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

Change looks good, waiting for jenkins testing to pass

@jgrund jgrund merged commit a2fc50f into master Jul 20, 2020
@jgrund jgrund deleted the ip1981/2084-stratagem-clientmount branch July 20, 2020 23:58
beevans pushed a commit to beevans/integrated-manager-for-lustre that referenced this pull request Aug 6, 2020
Ref: f10ba6b

Signed-off-by: Igor Pashev <pashev.igor@gmail.com>

Co-authored-by: Joe Grund <jgrund@whamcloud.io>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

stratagem: Tried to update field chroma_core.LustreClientMount.filesystem with a model instance
3 participants