[6.16.z] removing cloned_from_id key from template object #16844
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.
Cherrypick of PR: #16813
Problem Statement
The value of
cloned_from_id
differs between the two instances, while the rest of the data matches. Sincedupe_json
is cloned fromtemplate
, it inherits the id fromtemplate
, whereas the template object itself was created directly and does not have a clone id . And it causes an assertion error. I removecloned_from_id
to prevent the assertion from failing.Solution
I remove
cloned_from_id
key to prevent the assertion from failing and removingcloned_from_id
does not impact the test.