[release-4.13] OCPBUGS-12700: update-etcd-scaling-test

[openshift-cherrypick-robot]

This is an automated cherry-pick of #27788

/assign Elbehery

[Elbehery]

/test e2e-aws-ovn-fips

[Elbehery]

/assign @tjungblu
/assign @hasbro17

[Elbehery]

/assign @DennisPeriquet

[Elbehery]

/jira refresh

[openshift-ci-robot]

@Elbehery: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

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 kubernetes/test-infra repository.

[Elbehery]

/retitle [release-4.13] OCPBUGS-12700: update-etcd-scaling-test

[openshift-ci]

@openshift-cherrypick-robot: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.13] OCPBUGS-12700: update-etcd-scaling-test

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/test-infra repository.

[openshift-ci-robot]

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

• expected Jira Issue OCPBUGS-12700 to depend on a bug targeting a version in 4.14.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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 #27788

/assign Elbehery

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/test-infra repository.

[Elbehery]

/jira refresh

[openshift-ci-robot]

@Elbehery: This pull request references Jira Issue OCPBUGS-12700, which is invalid:

• expected Jira Issue OCPBUGS-12700 to depend on a bug targeting a version in 4.14.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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

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/test-infra repository.

[Elbehery]

/jira refresh

[openshift-ci-robot]

@Elbehery: This pull request references Jira Issue OCPBUGS-12700, which is invalid:

• expected Jira Issue OCPBUGS-12700 to depend on a bug targeting a version in 4.14.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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

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/test-infra repository.

[Elbehery]

/jira refresh

[openshift-ci-robot]

@Elbehery: This pull request references Jira Issue OCPBUGS-12700, which is invalid:

• expected dependent Jira Issue OCPBUGS-12701 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead
• expected dependent Jira Issue OCPBUGS-12701 to target a version in 4.14.0, but it targets "4.14" 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.

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 kubernetes/test-infra repository.

[Elbehery]

/jira refresh

[tjungblu]

/retest

[tjungblu]

I think approval needs to be done through @hasbro17
Maybe worth updating the https://github.com/openshift/origin/blob/release-4.13/test/extended/etcd/OWNERS at some point for the etcd folder

[Elbehery]

/retest

[Elbehery]

/retest

[Elbehery]

/retest

[Elbehery]

@hasbro17 ptal a look here

I have ran the test against 4.13 cluster and it passes

1 pass, 0 skip (33m37s)

mustafa@mustafas-MacBook-Pro origin % oc get machines -o wide -n openshift-machine-api

NAME                                                PHASE     TYPE         REGION      ZONE         AGE    NODE                                         PROVIDERID                              STATE

ci-ln-56dql7b-76ef8-447ml-master-1                  Running   m6a.xlarge   us-east-2   us-east-2a   131m   ip-10-0-222-112.us-east-2.compute.internal   aws:///us-east-2a/i-0e461fa2d21e87774   running

ci-ln-56dql7b-76ef8-447ml-master-2                  Running   m6a.xlarge   us-east-2   us-east-2c   131m   ip-10-0-189-178.us-east-2.compute.internal   aws:///us-east-2c/i-0417c686c26919da8   running

ci-ln-56dql7b-76ef8-447ml-master-gvgjl-0            Running   m6a.xlarge   us-east-2   us-east-2c   55m    ip-10-0-185-220.us-east-2.compute.internal   aws:///us-east-2c/i-04d7b4cff30979fa2   running

ci-ln-56dql7b-76ef8-447ml-worker-us-east-2a-fsp7r   Running   m6a.xlarge   us-east-2   us-east-2a   128m   ip-10-0-254-99.us-east-2.compute.internal    aws:///us-east-2a/i-0b06867346b2f9f26   running

ci-ln-56dql7b-76ef8-447ml-worker-us-east-2c-w2zph   Running   m6a.xlarge   us-east-2   us-east-2c   128m   ip-10-0-161-234.us-east-2.compute.internal   aws:///us-east-2c/i-02b026fbf67b128a7   running

ci-ln-56dql7b-76ef8-447ml-worker-us-east-2c-wpgb6   Running   m6a.xlarge   us-east-2   us-east-2c   128m   ip-10-0-187-77.us-east-2.compute.internal    aws:///us-east-2c/i-0419bcd1f880b6077   running

mustafa@mustafas-MacBook-Pro origin %

 

[hasbro17]

/approve
/label backport-risk-assessed

[openshift-ci]

@hasbro17: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-staff-engineers]

In response to this:

/approve
/label backport-risk-assessed

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/test-infra repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: geliu2016, hasbro17, openshift-cherrypick-robot, tjungblu

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:

• test/extended/etcd/OWNERS [hasbro17]

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

[Elbehery]

@mfojtik @deads2k hello ✋🏽

can we please get these labels here backport-risk-assessed, cherry-pick-approved

[damdo]

@Elbehery you might want to ping them on slack, I know some of them are drowned in GH notifications.

[deads2k]

/staff-eng-approved
/hold

hold until after 4.13 GA.

[damdo]

We should be able to unhold this now that 4.13 is GA :)

[deads2k]

/hold cancel

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 893ae57 and 2 for PR HEAD 2af700f in total

[openshift-ci]

@openshift-cherrypick-robot: The following tests 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/e2e-aws-ovn-single-node-upgrade	2af700f	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-single-node-serial	2af700f	link	false	/test e2e-aws-ovn-single-node-serial

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/test-infra repository. I understand the commands that are listed here.

[Elbehery]

verify ci fails on

INFO[2023-05-23T[16](https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/27892/pull-ci-openshift-origin-release-4.13-verify/1661037437029191680#1:build-log.txt%3A16):13:39Z] Executing test verify                        
WARN[2023-05-23T16:13:39Z] Unable to create pod verify, may be temporary.  error=pods "verify" is forbidden: the string value of PreemptionPolicy (PreemptLowerPriority) must not be provided in pod spec; priority admission controller computed Never from the given PriorityClass name
WARN[2023-05-23T16:13:40Z] Unable to create pod verify, may be temporary.  error=pods "verify" is forbidden: the string value of PreemptionPolicy (PreemptLowerPriority) must not be provided in pod spec; priority admission controller computed Never from the given PriorityClass name
WARN[2023-05-23T16:13:42Z] Unable to create pod verify, may be temporary.  error=pods "verify" is forbidden: the string value of PreemptionPolicy (PreemptLowerPriority) must not be provided in pod spec; priority admission controller computed Never from the given PriorityClass name
WARN[2023-05-23T16:13:46Z] Unable to create pod verify, may be temporary.  error=pods "verify" is forbidden: the string value of PreemptionPolicy (PreemptLowerPriority) must not be provided in pod spec; priority admission controller computed Never from the given PriorityClass name
INFO[2023-05-23T16:13:49Z] Ran for [18](https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/27892/pull-ci-openshift-origin-release-4.13-verify/1661037437029191680#1:build-log.txt%3A18)m23s                               
ERRO[[20](https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/27892/pull-ci-openshift-origin-release-4.13-verify/1661037437029191680#1:build-log.txt%3A20)23-05-23T16:13:49Z] Some steps failed:                           
ERRO[2023-05-23T16:13:49Z] 
  * could not run steps: step verify failed: failed to create or restart test pod: unable to create pod: timed out waiting for the condition 
INFO[20[23](https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/27892/pull-ci-openshift-origin-release-4.13-verify/1661037437029191680#1:build-log.txt%3A23)-05-23T16:13:49Z] Reporting job state 'failed' with reason 'executing_graph:step_failed:running_pod'

[Elbehery]

ran make verify locally and it passes

/retest-required

[openshift-ci-robot]

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

In response to this:

This is an automated cherry-pick of #27788

/assign Elbehery

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/test-infra repository.