openSUSE Build Service June 2018

buildservice@lists.opensuse.org

34 participants
27 discussions

[opensuse-buildservice] Public Key not available SLE_12_SP3 s390x

by Usman Haider

Hi, I am new and trying local build on s390x with SLE_12_SP3 using the following command sudo osc build but I get the public key not available for many packages. You can see the output by clicking the following link https://pastebin.com/YBQk3vGe I know that I can use --noverify option to bypass this and builds complete successfully when I use --noverify option but how can I fix this? What will happen if I don't fix it? -- Usman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 years, 5 months

[opensuse-buildservice] OBS Appliance - Unable to Update

by Khalil Graves

I am running OBS Appliance 2.8.2 on VMware ESX. When the appliance boots I get an error "Failed to start LSB: Finds the storage device to be used for OBS server and/or worker." I have included a dump of systemctl status obsstoagesetup.service below. I Just want to confirm if this is normal or should be addressed. I also attempted and update of a clone of my appliance via zypper but 2 GB root drive is not sufficient for upgrades. Update begins but end with "Error Code: Write Error". I checked root drive and it was up to 100% utilization from 93% prior to update. I decided to install latest version of OBS appliance over existing install. New appliance adopts my old setting but now I am getting and error on boot "Failed to start LSB: open build service source service server." In addition I am unable to build rpms in this current state. Not sure what to do next to get the cloned appliance to build a package. SYSTEMCTL status obsstoragesetup.service obsstoragesetup.service - LSB: Finds the storage device to be used for OBS server and/or worker Loaded: loaded (/etc/init.d/obsstoragesetup; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2018-03-06 18:44:59 UTC; 16min ago Docs: man:systemd-sysv-generator(8) Process: 1365 ExecStart=/etc/init.d/obsstoragesetup start (code=exited, status=1/FAILURE) Mar 06 18:44:59 linux obsstoragesetup[1365]: OBS_SERVER_SIZE=38912 Mar 06 18:44:59 linux obsstoragesetup[1365]: TOTAL_SWAP_SIZE=1024 Mar 06 18:44:59 linux obsstoragesetup[1365]: FINAL_VG_SIZE = 12284 - 38912 - 25600 - 1024 Mar 06 18:44:59 linux obsstoragesetup[1365]: FINAL_VG_SIZE=-53252 Mar 06 18:44:59 linux obsstoragesetup[1365]: OBS_WORKER_ROOT_SIZE=-26626 Mar 06 18:44:59 linux obsstoragesetup[1365]: MIN_WORKER_ROOT_SIZE=4096 Mar 06 18:44:59 linux systemd[1]: obsstoragesetup.service: Control process exited, code=exited status=1 Mar 06 18:44:59 linux systemd[1]: Failed to start LSB: Finds the storage device to be used for OBS server and/or worker. Mar 06 18:44:59 linux systemd[1]: obsstoragesetup.service: Unit entered failed state. Mar 06 18:44:59 linux systemd[1]: obsstoragesetup.service: Failed with result 'exit-code'. SYSTEMCTL status obsservice.service obsservice.service - LSB: open build service source service server Loaded: loaded (/etc/init.d/obsservice; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2018-03-09 11:59:39 UTC; 3min 34s ago Docs: man:systemd-sysv-generator(8) Process: 1761 ExecStart=/etc/init.d/obsservice start (code=exited, status=7) Mar 09 11:59:38 linux systemd[1]: Starting LSB: open build service source service server... Mar 09 11:59:39 linux startproc[1788]: startproc: exit status of parent of /usr/lib/obs/server/bs_service: 13 Mar 09 11:59:39 linux obsservice[1761]: Initializing obsservice..failed Mar 09 11:59:39 linux systemd[1]: obsservice.service: Control process exited, code=exited status=7 Mar 09 11:59:39 linux systemd[1]: Failed to start LSB: open build service source service server. Mar 09 11:59:39 linux systemd[1]: obsservice.service: Unit entered failed state. Mar 09 11:59:39 linux systemd[1]: obsservice.service: Failed with result 'exit-code'. '. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 years, 1 month

[opensuse-buildservice] OBS + GitHub - deprecation of GitHub Services

by Linux Kamarada

Hello, guys! I searched how to integrate OBS with GitHub so that a git push would cause OBS to fetch the source code and build. I followed directions on these pages: https://openbuildservice.org/2013/11/22/source-update-via_token/ https://github.com/seccubus/obs_autobuild_test (CC their authors, thank you for the great material!) But when I opened GitHub's Integration & services to add the Obs service, I read this: "Note: [GitHub Services are being deprecated][1]. Please contact your integrator for more information on how to migrate or replace a service with [webhooks][2] or [GitHub Apps][3]." [1]: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ [2]: https://developer.github.com/webhooks/ [3]: https://developer.github.com/apps/differences-between-apps/#about-github-ap… The news is from April 25, 2018. The first paragraph summarizes it: "GitHub plans on shutting down GitHub Services so we can shift focus to other areas of the API, such as strengthening GitHub Apps and GraphQL, and improving webhooks. The intention of GitHub Services was to allow third-party developers to submit code for integrating with their services, but this functionality has been superseded by GitHub Apps and webhooks. GitHub Services has not supported new features since April 25, 2016, and we plan to officially deprecate it on October 1st, 2018." Although I successfully integrated OBS with GitHub using a GitHub Service, is it already possible to do that same integration using GitHub Apps or webhooks? Thank you! Antonio The Linux Kamarada Project http://kamarada.github.io/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 years, 2 months

[opensuse-buildservice] No metadata when using obs_scm service

by Giovanni Santini

Good afternoon, I am having a quite singular problem; as of now, I am using the `tar_scm` service for my package and I would like to switch to `obs_scm` as requested upstream. The problem is that, as of now, when using the latter one, the Git metadata (AKA the .git folder) is not repacked inside the CPIO archive. Why is it so? I need the Git metadata in order to properly build the package. The service is as it follows:  <service name="tar_scm"> <param name="scm">git</param> <param name="url">https://github.com/telegramdesktop/tdesktop.git</param> <param name="revision">v1.3.7</param> <param name="version">obs</param> <param name="package-meta">yes</param> </service> Thanks in advance. -- Giovanni Santini My blog: http://giovannisantini.tk My code: https://git{hub,lab}.com/ItachiSan My GPG: 2FADEBF5 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 years, 9 months

[opensuse-buildservice] tumbleweed refreshes since [18-Aug-2017] and [hosts unreachable ] on [ http://ftp5.gwdg.de and http://download.opensuse.org ]

by doiggl＠velocitynet.com.au

Hello, Hosts http://ftp5.gwdg.de and http://download.opensuse.org unreachable tumbleweed refreshes since [18-Aug-2017] and cannot get to [ http://ftp5.gwdg.de or http://download.opensuse.org] I tried following: [no response from] # ping http://download.opensuse.org ping: unknown host http://download.opensuse.org # ping http://ftp5.gwdg.de ping: unknown host http://ftp5.gwdg.de http://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/suse/repodata ping http://download.opensuse.org ping: unknown host http://download.opensuse.org -I tried to ping google.com -seems ok # ping google.com PING google.com (172.217.25.142) 56(84) bytes of data. 64 bytes from syd15s03-in-f14.1e100.net (172.217.25.142): icmp_seq=1 ttl=52 time=19.4 ms 64 bytes from syd15s03-in-f14.1e100.net (172.217.25.142): icmp_seq=2 ttl=52 time=19.8 ms 64 bytes from syd15s03-in-f14.1e100.net (172.217.25.142): icmp_seq=3 ttl=52 time=19.9 ms 64 bytes from syd15s03-in-f14.1e100.net (172.217.25.142): icmp_seq=4 ttl=52 time=20.1 ms 64 bytes from syd15s03-in-f14.1e100.net (172.217.25.142): icmp_seq=5 ttl=52 time=19.5 ms ^C --- google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4005ms rtt min/avg/max/mdev = 19.480/19.790/20.153/0.287 ms Also: Are there any updates to tumbleweed since 18-Aug-2017 I do not see any updates on mirrors since then. Tried mirrors on: [has date details on] http://sfo-korg-mirror.kernel.org/opensuse/tumbleweed/repo/oss/suse/repodat… [local time is] # date Mon Aug 21 15:00:25 EST 2017 Cheers --Glenn -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 years, 9 months

[opensuse-buildservice] Is it possible to have prjconf settings per package/image?

by Johannes Kastl

Hi all, this question comes up from time to time in our team, so finally I am hoping for an answer ;-) Example setting: Building multiple kiwi images in a OBS project SLES12SP3 and SLES12SP2 images need different Preinstall settings, as some stuff (skopeo, umoci, ...) is not available in SP2 but required in SP3. I know I can specify different settings per repository (if %_repository == images), but is it possible to set it per package/image? Something like %_packagename or %_name or similar? Or somehow find out the OS version and set stuff accordingly? Not sure if images are accepting the suse_version macros... Thanks in advance. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

3 years, 10 months

[opensuse-buildservice] KVM build type and dns resolving in a chroot

by Mitya Ivanov

Hi all! At firsts i want to thank Stefan Seyfried for help with my previous problem with "badhost" thing. I have lost my creds of my previous mailbox, sorry :) So i have another question. Is there any info about workers setup using KVM as build VM type? Any requierements? Is qemu-kvm etc. would be enough or for example i need to generate initramfs for target distro? And another question - how to workaround situation when package require working dns resolver in a chroot while build process? For example libguestfs.spec wants to resolve libguestsfs.org name. I know that having /etc/resolv.conf in a chroot would be enough but how to autogenerate it? Maybe there some undocumented OBS features that allow to seed needed files in a chroot? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 years, 10 months

[opensuse-buildservice] Questions regarding building KIWI images on OBS

by Johannes Kastl

Hi all, while building KIWI images on OBS, I came across some questions that I found no answer for in the documentation. ##################################### 1. Why is it that some images have an "alias" or link in the repository, while others do not have that? I just can't find an example, though, the Leap15.0 images seem to have that now. I guess it is due to the "staticlinks" in the prjconf, but I saw projects that have that and were missing the links. %if "%_repository" == "images" Type: kiwi Repotype: staticlinks Patterntype: none %endif ##################################### 2. Why do some of the projects, that are only used for images, have build targets for not only "images", but also the image's base release? I.e. Cloud:Images:Leap15.0 has a build target against openSUSE:Leap:15.0 but building the image is excluded. ##################################### 3. I had some issues with the this-is-only-for-build-envs package that seems to be a requirement needed for building stuff. I had copied over the prjconf to a new project, copied an image from Cloud:Images:... and saw this error. I worked around it with an Ignore, but should this not somehow be automatically provided? I found nothing related to that in the Cloud:Images prjconf or that of it's subprojects. ##################################### Maybe someone has more insight and can help me fit together the missing pieces. Thanks in advance! Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

3 years, 10 months

[opensuse-buildservice] Stuck at "scheduled" state

by Mitya Ivanov

Hi all! I wanted to try KVM builds instead of chroot, so i changed OBS_VM_TYPE to "kvm". After that build process of "package1" stucked at "scheduled" state. Then i reverted back to chroot build, but build state stays the same. Even after deletion of package and creation back it still "scheduled". Any other package build is successful, if package not named "package1". Seems like some stale info about "package1" stored in db? Where to find it and how to clean this out? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 years, 10 months

[opensuse-buildservice] own OBS instance: worker -> putjob performance problem

by Stefan Seyfried

Hi all, I'm running an instance of OBS 2.9.3 with two workers, building all sorts of stuff including kiwi images. Sometimes, it takes very long to upload the build results. Right now, the worker is uploading an image, which finished build at 09:21: # ls -lh /srv/obs/worker-root/root_9/.build.packages/KIWI/SLES_12SP2_SAAS_VM1.x86_64-2.4.0-Build3.1.tbz -rw-r--r-- 1 root root 457M Jun 27 09:21 /srv/obs/worker-root/root_9/.build.packages/KIWI/SLES_12SP2_SAAS_VM1.x86_64-2.4.0-Build3.1.tbz obs:~ # l /srv/obs/jobs/x86_64/.putjob.17789/SLES_12SP2_SAAS_VM1.x86_64-2.4.0-Build3.1.tbz -h -rw-r--r-- 1 obsrun obsrun 88M Jun 27 12:31 /srv/obs/jobs/x86_64/.putjob.17789/SLES_12SP2_SAAS_VM1.x86_64-2.4.0-Build3.1.tbz As you can see, it's three hours for 88MB... a bit slow for a multi-gbit ethernet link ;) stracing the worker process, I see it sending packets: 12:39:37 read(5, "\16\245\0Y\fEw\237M\16\367\227\30}\265'"..., 8192) = 8192 12:39:37 write(4, "2000\r\n\16\245\0Y\fEw\237M\16"..., 8200) = 8200 12:39:42 read(5, "\342\233\332\370\36W\331\177g=\272\337pbll"..., 8192) = 8192 12:39:42 write(4, "2000\r\n\342\233\332\370\36W\331\177g="..., 8200) = 8200 and the 5 seconds pause in between looks like it might be some missing tcp flag, or timing parameter or such? this is my iperf summary for this link: [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 6.82 GBytes 5.86 Gbits/sec 0 sender [ 4] 0.00-10.00 sec 6.82 GBytes 5.86 Gbits/sec receiver So the network itself should be fine. Any hints how to debug that? I have not seen this before the update from 2.8.4 to 2.9.3. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 years, 10 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service June 2018