Mailinglist Archive: opensuse-buildservice (105 mails)

< Previous Next >
Re: [opensuse-buildservice] CentOS Modules: Error 400 unknown parameter module
  • From: Moritz Röhrich <moritz@xxxxxxxxxxx>
  • Date: Mon, 9 Dec 2019 12:36:25 +0100
  • Message-id: <CACU65bcZX_aPQPEJHi1URzwQj2NPrgg4gC=54BeL3K1gAitNWg@mail.gmail.com>
Thank you a lot. The patch solved that issue. Now I have been able to
start build jobs for CentOS 8.

Best regards, Moritz




On Fri, Dec 6, 2019 at 2:38 PM Adrian Schröter <adrian@xxxxxxx> wrote:

On Freitag, 6. Dezember 2019, 13:12:16 CET Moritz Röhrich wrote:
Hi OBS Community,

I am trying to build for CentOS 8 using OBS but I am getting the
following error:

400 remote error: unknown parameter 'module'
(http://obs-srcserver:5352/getbinaries?workerid=obs-worker-75d5b98b45-9d2vj:1&project=openSUSE.org:CentOS:CentOS-8:Stream&repository=appstream&arch=x86_64&module=python27-2.7&binaries=acl,attr,bash,coreutils,diffutils,filesystem,glibc,grep,libacl,libattr,libgcc,m4,ncurses,pam,

This is when your local worker starts a job?

[...]

,dbus,SDL,vim-filesystem,device-mapper-libs,json-c,libpcap,dbus-daemon,dbus-libs,dbus-tools,dbus-common)
(worker was obs-worker-75d5b98b45-9d2vj:1)

Indeed, when I curl for the requested URL, I get:
$ curl
"http://obs-srcserver:5352/getbinaries?workerid=obs-worker-75d5b98b45-ndnpg:1&project=openSUSE.org:CentOS:CentOS-8&repository=appstream&arch=x86_64&module=common&module=python27-2.7&module=python36-3.6&binaries=acl";
<status code="400">
<summary>unknown parameter 'module'</summary>
</status>

This is also reflected in the src-server logs

[...]bind-libs-lite,bind-license,python3-bind,libss,fuse-libs,gettext-common-devel
,gpm-libs,linuxconsoletools,systemd,libfdisk,libutempter,vim-common,libpipeline,libmodman,python3-ply,SDL,kmod-libs,cryptsetup-libs,libseccomp,iptables-libs,systemd-pam,dbus,vim-filesystem,device-mapper-libs,json-c,libpcap,dbus-daemon,dbus-libs,dbus-tools,dbus-common
10.244.1.133 [2276]: unknown parameter 'module'

I am however running the latest version of OBS 2.11 alpha
(2.11~alpha.20191206T090330.3a29f5dec7-9316.1). I thought fedora
modularity was supposed to be supported? This problem was also present
in my previous version of OBS, which was the 2.11 alpha from late
November.

Is this intentional? Am I missing something? Any help is much apprechiated.

No ... we have not tested interconnect for this yet ... is the attached patch
helping?

rcobssrcserver restart

is needed afterwards.

--

Adrian Schroeter <adrian@xxxxxxx>
Build Infrastructure Project Manager

SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
(HRB 247165, AG München), Geschäftsführer: Felix Imendörffer

--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups