Vadim Rutkovsky comments

Results 190 comments of


                                            Vadim Rutkovsky

template: wait for pod to teardown (if container is present) during delete

/cc @stevekuznetsov

template: wait for pod to teardown (if container is present) during delete

>Why are we making this change? When test gets cancelled - a new commit pushed in rehearse tests for instance - ci-operator would send termination signal and wait for pod...

template: wait for pod to teardown (if container is present) during delete

Reworked this to leverage polls and watches: * `waitForTeardownToComplete` polls for a list of containers * `waitForPodDeletion` watches for pod to be removed with a timeout

template: wait for pod to teardown (if container is present) during delete

Simplified this: * If pod has teardown container timeout is extended by 10 mins (average teardown takes 10 min on AWS, but might take longer on openstack) * `waitForPodDeletion` now...

template: wait for pod to teardown (if container is present) during delete

Extending the timeout is the simplest approach, and its valid, however it would apply to all ci-operator pods. e2e-aws's teardown is the only one I know of which takes longer...

template: wait for pod to teardown (if container is present) during delete

Right, it appears a larger timeout would act the same. Created #358 instead. I'll keep this open for now

WIP MGMT-17250 Replace xinetd with firewallcmd port forwards

>did you tested it works locally No, I don't have the hardware for this. My plan is: * ensure e2e tests pass on rhel8 * run test with rhel9 via...

Some room names keep changing to `#` name only and back and forth

Perhaps https://github.com/mautrix/slack/commit/7e379049f1c0be2bb6d0b38eaff331f2eb000591 fixes it?

ServiceMonitor rejected on OCP 4.14

It was rc1 and rc2 on GCP, most likely the trigger was user-level monitoring. I'll play with this a few more times to see what's causing it

Use ct_s2i_build_as_df

>No package go-toolset-7 available. in rhel7 test and ``` Step 1/11 : FROM registry.fedoraproject.org/f30/s2i-base:latest Trying to pull repository registry.fedoraproject.org/f30/s2i-base ... latest: Pulling from registry.fedoraproject.org/f30/s2i-base received unexpected HTTP status: 503 Service...