Alexandre Quinteiro

Results 11 comments of Alexandre Quinteiro

FYI I have seen this problem [above](https://github.com/SeleniumHQ/docker-selenium/issues/2093#issuecomment-1968291763) in my test pipeline, and it randomly happens... I have noticed also that when it happens once, no matter how many tests I...

@VietND96 @diemol just a quick update after we upgraded our images to 4.18 and chart 0.28.x I have noticed that when "Session cloud not be created" problem happens... when we...

Just to add some additional context about the problem above... it is the same mentioned here: https://github.com/SeleniumHQ/docker-selenium/issues/2129#issuecomment-1970446915 At that time @VietND96 though preStop was stuck and suggested to get some...

@VietND96 our runtime is really running in containers in the same cluster, which are connected with hub via remote web driver (java client). We are not using `containerd` though. I...

Just to add two more examples... I have in my live env here one chrome node in running state and one chrome node in terminating state... both are stuck (usually...

@VietND96 just to give some feedback: we did not notice any node hanging so far, after: - upgrade images to 4.18 and helm to 0.28 - set `global.seleniumGrid.stdoutProbeLog=false` We will...

@VietND96 @Aymen-Ben-S noticed hanging in one of our environments. Follow some details: List of Pods in selenium namespace sorted by Created Date: Only the top chrome node is really runnning,...

Thanks @VietND96... we plan to upgrade our images to the most recent release and try again. Considering we are using `job` scaling type, do you think worth setting `terminationGracePeriodSeconds` to...

Follow detailed investigation on how I got to this problem: ---- When subscribing to Red Hat Openshift Pipelines latest channel, currently pointing to `openshift-pipelines-operator-rh.v1.11.0`, installation is not able to be...

@unnati-solanki-git as we discussed, considering provisioning command runs ansible-devops playbook and considering that playbook/role is already prepared to receive IPI_ROOTVOLUME_SIZE, for this particular issue we have to enforce the IPI_ROOTVOLUME_SIZE=250...