Add vexxhost-only nodesets for edpm jobs #3568
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
There is a networking issue affecting the communications between vexxhost and ibm providers. In order to mitigate the issue, I am proposing to run edpm jobs in vexxhost so that the provider and edpm jobs run in vexxhost. Depends-On: openstack-k8s-operators/ci-framework#3568 Signed-off-by: Alfredo Moralejo <[email protected]>
amoralej
force-pushed
the
vexxhost-only
branch
from
269ed20 to
1d332a6
Compare
There is a networking issue affecting the communications between vexxhost and ibm providers. In order to mitigate the issue, I am proposing to run edpm or kuttl jobs in vexxhost so that the provider and edpm jobs run in vexxhost. Depends-On: openstack-k8s-operators/ci-framework#3568 Signed-off-by: Alfredo Moralejo <[email protected]>
|
this might be related to recent zuul changes as well. it certainty can happen at the build set level. in anycase even if we do not have that zuul functionlaity we shoudl avoid having jobs that consume output form other jobs in diffent providers if we can. |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/94614bea6cf841d0aa4d1cbc8e0e7e6c ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 47m 26s |
|
check-rdo |
|
Could you also add 4.20 crc-cloud + 2.56 for crc please? Let's keep consistency. |
Sure, I will send new patch. |
Actually, there is not multinode nodeset with 2.56, all the nodesets for 4.20 are based on crc-cloud, so I will include only the crc-cloud one. |
There is a networking issue affecting the communications between vexxhost and ibm providers. In order to mitigate the issue, I am creating some nodesets which will run in vexxhost only so that we can be sure that provider and edpm or kuttl jobs run in the same infrastructure. Signed-off-by: Alfredo Moralejo <[email protected]>
amoralej
force-pushed
the
vexxhost-only
branch
from
1d332a6 to
02d2bbc
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/dc5d2cad3ad64d49b573fe0808e180fa ❌ openstack-k8s-operators-content-provider FAILURE in 6m 08s |
|
check-rdo |
There is a networking issue affecting the communications between vexxhost and ibm providers. In order to mitigate the issue, I am proposing to run edpm or kuttl jobs in vexxhost so that the provider and edpm jobs run in vexxhost. Depends-On: openstack-k8s-operators/ci-framework#3568 Signed-off-by: Alfredo Moralejo <[email protected]>
There is a networking issue affecting the communications between vexxhost and ibm providers. In order to mitigate the issue, I am proposing to run edpm or kuttl jobs in vexxhost so that the provider and edpm jobs run in vexxhost. Depends-On: openstack-k8s-operators/ci-framework#3568 Signed-off-by: Alfredo Moralejo <[email protected]> (cherry picked from commit 05a604e)
There is a networking issue affecting the communications between vexxhost and ibm providers. In order to mitigate the issue, I am proposing to run edpm or kuttl jobs in vexxhost so that the provider and edpm jobs run in vexxhost. Depends-On: openstack-k8s-operators/ci-framework#3568 Signed-off-by: Alfredo Moralejo <[email protected]> (cherry picked from commit 05a604e)
5 participants
There is a networking issue affecting the communications between vexxhost and ibm providers. In order to mitigate the issue, I am creating some nodesets which will run in vexxhost only so that we can be sure that provider and edpm jobs run in the same provider.