[release-4.20] OCPBUGS-63136: client: re-use a single file for building the session instead of randomly named files

[openshift-cherrypick-robot]

This is an automated cherry-pick of #140

/assign openshift-ci-robot

[openshift-ci-robot]

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-38759 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-4.20] OCPBUGS-63136: client: re-use a single file for building the session instead of randomly named files

In response to this:

This is an automated cherry-pick of #140

/assign openshift-ci-robot

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-63136, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-38759 to target a version in 4.21.0, but it targets "4.21" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #140

/assign openshift-ci-robot

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[chrischdi]

/jira sync

[chrischdi]

/jira refresh

/lgtm
/approve

[openshift-ci-robot]

@chrischdi: This pull request references Jira Issue OCPBUGS-63136, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

/lgtm
/approve

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[chrischdi]

/jira refresh

[openshift-ci-robot]

@chrischdi: This pull request references Jira Issue OCPBUGS-63136, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.0) matches configured target version for branch (4.20.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-38759 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-38759 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
• bug has dependents

Requesting review from QA contact:
/cc @sunzhaohua2

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[chrischdi]

/verify bypass

Verified on #140

[chrischdi]

/verified bypass

Verified on #140

[openshift-ci-robot]

@chrischdi: The verified label has been added.

In response to this:

/verified bypass

Verified on #140

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[chrischdi]

/verified cancel

[openshift-ci-robot]

@chrischdi: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

In response to this:

/verified cancel

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[chrischdi]

/verified bypass

• Verified on OCPBUGS-38759: client: re-use a single file for building the session instead of randomly named files #140
• Change is hard to verify without adding another change to reproduce the issue which makes it not easy to test and not testing the exact code
• Also there are no other related code which could influence it, so considering it as a low risk.

[openshift-ci-robot]

@chrischdi:

In response to this:

/verified bypass

• Verified on OCPBUGS-38759: client: re-use a single file for building the session instead of randomly named files #140
• Change is hard to verify without adding another change to reproduce the issue which makes it not easy to test and not testing the exact code
• Also there are no other related code which could influence it, so considering it as a low risk.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/okd-scos-e2e-aws-ovn	92a43f7	link	false	/test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[damdo]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrischdi, damdo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [damdo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[chrischdi]

/backport risk-assessed

[chrischdi]

/label backport-risk-assessed

[sdodson]

/label staff-eng-approved

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-63136 is in an unrecognized state (Verified) and will not be moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #140

/assign openshift-ci-robot

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.