openshift
[release-4.18] OCPBUGS-48389: only provision workloads when network creation has started
This is an automated cherry-pick of #29348
/assign jluhrsen
@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: SDN-5568
In response to this:
This is an automated cherry-pick of #29348
/assign jluhrsen
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.
/retitle [release-4.18] OCPBUGS-48389: only provision workloads when network creation has started
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-48389, which is valid.
7 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.18.0) matches configured target version for branch (4.18.0)
- bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
- release note type set to "Release Note Not Required"
- dependent bug Jira Issue OCPBUGS-48391 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
- dependent Jira Issue OCPBUGS-48391 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
- bug has dependents
Requesting review from QA contact: /cc @anuragthehatter
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 #29348
/assign jluhrsen
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.
@stbenjam could you please set the backport-risk-assessed label on this PR ?
@anuragthehatter: Can not set label cherry-pick-approved: Must be member in one of these teams: [openshift-staff-engineers]
In response to this:
/label cherry-pick-approved
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.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dgoodwin, knobunc, maiqueb, openshift-cherrypick-robot
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [dgoodwin]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/retest-required
Remaining retests: 0 against base HEAD 1187d3a92874651cd075c4724dd160c1ca3faefb and 2 for PR HEAD 88eadb586bb1de042d7fc4436d9440dabb26ac7e in total
/retest-required
Remaining retests: 0 against base HEAD 2774b2b307da1b3bc24f7f915d7d089d8648b397 and 2 for PR HEAD 88eadb586bb1de042d7fc4436d9440dabb26ac7e in total
PR needs rebase.
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.
@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 | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | false | /test e2e-aws-ovn-single-node-upgrade |
| ci/prow/e2e-aws-ovn-kube-apiserver-rollout | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | false | /test e2e-aws-ovn-kube-apiserver-rollout |
| ci/prow/e2e-aws-ovn-single-node | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | false | /test e2e-aws-ovn-single-node |
| ci/prow/e2e-gcp-csi | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | false | /test e2e-gcp-csi |
| ci/prow/e2e-aws-ovn-fips | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | unknown | /test e2e-aws-ovn-fips |
| ci/prow/e2e-aws-ovn-serial | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | unknown | /test e2e-aws-ovn-serial |
| ci/prow/e2e-aws-ovn-edge-zones | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | unknown | /test e2e-aws-ovn-edge-zones |
| ci/prow/unit | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | unknown | /test unit |
| ci/prow/e2e-metal-ipi-ovn-ipv6 | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | unknown | /test e2e-metal-ipi-ovn-ipv6 |
| ci/prow/verify | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | unknown | /test verify |
| ci/prow/e2e-aws-ovn-microshift-serial | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | unknown | /test e2e-aws-ovn-microshift-serial |
| ci/prow/e2e-gcp-ovn-upgrade | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | unknown | /test e2e-gcp-ovn-upgrade |
| ci/prow/e2e-aws-ovn-microshift | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | unknown | /test e2e-aws-ovn-microshift |
| ci/prow/lint | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | unknown | /test lint |
| ci/prow/okd-scos-images | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | unknown | /test okd-scos-images |
| ci/prow/e2e-gcp-ovn | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | unknown | /test e2e-gcp-ovn |
| ci/prow/images | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | unknown | /test images |
| ci/prow/verify-deps | 88eadb586bb1de042d7fc4436d9440dabb26ac7e | link | unknown | /test verify-deps |
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.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closed this PR.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
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.
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-48389. The bug has been updated to no longer refer to the pull request using the external bug tracker.
In response to this:
This is an automated cherry-pick of #29348
/assign jluhrsen
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.