ARSN-392 [7.70] Put metadata to a standalone null master breaks CloudServer CRUD

[nicolas2bert]

NOTE: This change is only impacting the "file" metadata backend logic. Similar fixes will be implemented in scality/Metadata using Arsenal.updateOrAppendNullVersionId() method.

Description:

1653fd2ad37b209f66bc995c2e9823813a504634: "File" metadata backend should be "mocking" the V0 scality/Metadata backend. To fix it, we imported the V0 processVersionSpecificPut from scality/Metadata.

58d06229383a692f073e75db2e6033217bcf29e9:

• For "null key" backward compatibility (if isNull is undefined), add the nullVersionId field to the master update. The nullVersionId is needed for listing, retrieving, and deleting null versions.

• For the new null key implementation (if isNull is defined): add the isNull2 field and set it to true to specify that the new version is null AND has been put with a Cloudserver handling null keys (i.e., supporting S3C-7352).

• Manage scenarios in which a version is marked with the isNull attribute set to true, but without a version ID. This happens after BackbeatClient.putMetadata() is applied to a standalone null master.

[bert-e]

Hello nicolas2bert,

My role is to assist you with the merge of this pull request. Please type @bert-e help to get information on this process, or consult the user documentation.

Status report is not available.

[bert-e]

Incorrect fix version

The Fix Version/s in issue ARSN-392 contains:

• None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

• 7.70.24

• 8.1.123

Please check the Fix Version/s of ARSN-392, or the target branch of this pull request.

[bert-e]

Incorrect fix version

The Fix Version/s in issue ARSN-392 contains:

• 7.10.58

• 7.70.24

• 8.1.123

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

• 7.70.24

• 8.1.123

Please check the Fix Version/s of ARSN-392, or the target branch of this pull request.

[bert-e]

Incorrect fix version

The Fix Version/s in issue ARSN-392 contains:

• 7.10.59

• 7.70.26

• 8.1.124

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

• 7.70.26

• 8.1.124

Please check the Fix Version/s of ARSN-392, or the target branch of this pull request.

[nicolas2bert]

ping

[bert-e]

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically create the integration branches.

[nicolas2bert]

/create_integration_branches

[bert-e]

Integration data created

I have created the integration data for the additional destination branches.

• this pull request will merge bugfix/ARSN-392/null7.70 into development/7.70
• w/8.1/bugfix/ARSN-392/null7.70 will be merged into development/8.1

The following branches will NOT be impacted:

• development/6.4
• development/7.10
• development/7.4

You can set option create_pull_requests if you need me to create integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: create_integration_branches

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

The following options are set: create_integration_branches

[nicolas2bert]

@bert-e approve

[bert-e]

In the queue

The changeset has received all authorizations and has been added to the relevant queue(s). The queue(s) will be merged in the target development branch(es) as soon as builds have passed.

The changeset will be merged in:

• :heavy_check_mark: development/7.70

• :heavy_check_mark: development/8.1

The following branches will NOT be impacted:

• development/6.4
• development/7.10
• development/7.4

There is no action required on your side. You will be notified here once the changeset has been merged. In the unlikely event that the changeset fails permanently on the queue, a member of the admin team will contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

• Any commit you add on the source branch will trigger a new cycle after the current queue is merged.
• Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a member of the admin team now.

The following options are set: approve, create_integration_branches

[bert-e]

I have successfully merged the changeset of this pull request into targetted development branches:

• :heavy_check_mark: development/7.70

• :heavy_check_mark: development/8.1

The following branches have NOT changed:

• development/6.4
• development/7.10
• development/7.4

Please check the status of the associated issue ARSN-392.

Goodbye nicolas2bert.