On Wed, Jun 23, 2021 at 10:29 AM Marcin Sobczyk
<msobczyk(a)redhat.com> wrote:
>
>
> On 6/23/21 7:31 AM, Yedidyah Bar David wrote:
>> Hi all,
>>
>> On Mon, Jun 21, 2021 at 8:55 PM <jenkins(a)jenkins.phx.ovirt.org> wrote:
>>> Project:
https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/
>>> Build:
https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_night...
>> This is a week-old build, but some (but not all) of the check-patch
>> OST runs I did yesterday failed the same way, e.g. [1][2]:
>>
>> ======================================================================
>> failed on setup with "ost_utils.shell.ShellError: Command failed with
>> rc=125. Stdout:
>>
>> Stderr:
>> Trying to pull docker.io/selenium/hub:3.141.59-20210422...
>> unable to retrieve auth token: invalid username/password:
>> unauthorized: incorrect username or password
>> Error: 1 error occurred:
>> * Error initializing source docker://selenium/hub:3.141.59-20210422:
>> unable to retrieve auth token: invalid username/password:
>> unauthorized: incorrect username or password"
>> ======================================================================
>>
>> Is this a known issue? Perhaps related to docker's rate-limiting?
> Also stumbled upon this some time ago, but it stopped reproducing somehow.
> There's a bug filed for this - CPDEVOPS-176.
Link, please? This one says "Something's gone wrong":
https://ovirt-jira.atlassian.net/browse/CPDEVOPS-176
This now happened again:
https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/17456/
I've copied selenium images to our own ovirt repository in quay.io
and posted a patch for OST to make the switch: