search

redhat-cop / must-gather-operator

An operator to simplify the creation and upload of cluster diagnostics from the must-gather tool
Apache License 2.0
10 stars 15 forks source link

must-gather operator doesn't recognize successful upload #30

Closed zene22 closed 2 years ago

zene22 commented 2 years ago

Hi Raffaele,

we were using the must-gather operator successfully since months, but now the behaviour of the collect/upload has changed. The operator is not recognizing the successful upload of the must-gather archive, so after uploading it it repeats collection and will upload a next version. This is an endless loop which can only be stopped by deleting the must-gather instance.

As the operator didn't change we assume that the handling of the upload has changed on Red Hat side (access.redhat.com). Is there any chance that you could look into this?

The logging of the process is sparse, the only thing we can see when uplaoding it in the container is the following: 

Uploading 'must-gather-20220408_112247Z.tar.gz' to Red Hat Customer Portal case 03193350
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  412M    0     0  100  412M      0  2926k  0:02:24  0:02:24 --:--:--     0
curl: (52) Empty reply from server

I assume that the Empty reply from server is not expected.

zene22 commented 2 years ago

I tried to manually reproduce this with no success. Copying the job that is created by the operator and oc apply job.yaml worked in our case. As for us there is no difference in creating a mustgather custom resource or a job with such a template (we just have to replace the case number) wa take this as a workaround.

The curl: (52) error is for sure server side related, so anyway not an issue for the operator as such. So I close this issue again. Sorry for the noise.