public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: "Pavel Machek" <pavel@ucw.cz>
To: cip-dev@lists.cip-project.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	nobuhiro1.iwamatsu@toshiba.co.jp, Chris.Paterson2@renesas.com,
	Quirin Gylstorff <quirin.gylstorff@siemens.com>
Subject: Re: [cip-dev] Everything failed in gitlab
Date: Thu, 27 Aug 2020 15:10:25 +0200	[thread overview]
Message-ID: <20200827131025.GA28744@duo.ucw.cz> (raw)
In-Reply-To: <20200827082132.ca3vmztk43723bas@kratos.fritz.box>


[-- Attachment #1.1: Type: text/plain, Size: 990 bytes --]

Hi!

> > Michael, Quirin, any ideas?
> 
> yes. I took a brief look at the logs and found the problem:
> 
> ===============================================================================
> Aug 27 08:16:05 ip-172-20-42-140 kubelet[2152]: E0827 08:16:05.109337    2152 kuberuntime_manager.go:784] container start failed: ErrImagePull: rpc error: code = Unknown desc = Error response from daemon: Get https://registry.gitlab.com/v2/cip-project/cip-testing/linux-cip-ci/manifests/build-v3: unauthorized: HTTP Basic: Access denied
> ===============================================================================
> 
> => HTTP Basic: Access denied
> 
> Please check your setup/permissions?

I believe that Chris is unavailable this week. Is there anyone else
that knows how this is supposed to work?

Best regards,
								Pavel

--
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5284): https://lists.cip-project.org/g/cip-dev/message/5284
Mute This Topic: https://lists.cip-project.org/mt/76423839/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2020-08-27 13:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26  7:24 [cip-dev] Everything failed in gitlab Pavel Machek
2020-08-27  6:48 ` Nobuhiro Iwamatsu
2020-08-27  7:36   ` Jan Kiszka
2020-08-27  8:21     ` Michael Adler
2020-08-27 13:10       ` Pavel Machek [this message]
2020-08-27 21:40         ` Nobuhiro Iwamatsu
2020-08-28  4:44           ` Jan Kiszka
2020-08-28  7:11             ` Nobuhiro Iwamatsu
2020-08-28  7:51               ` Jan Kiszka
2020-08-28 16:53                 ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200827131025.GA28744@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Chris.Paterson2@renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@siemens.com \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=quirin.gylstorff@siemens.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox