February 2019 - openSUSE Build Service

[opensuse-buildservice] Public Key not available SLE_12_SP3 s390x
by Usman Haider 27 Nov '19

27 Nov '19

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

4 9

[opensuse-buildservice] OBS Appliance - Unable to Update
by Khalil Graves 15 Apr '19

15 Apr '19

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

2 4

[opensuse-buildservice] OBS + GitHub - deprecation of GitHub Services
by Linux Kamarada 19 Mar '19

19 Mar '19

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

7 12

[opensuse-buildservice] build stalls due to KVM running out of entropy
by Hans-Peter Jansen 26 Feb '19

26 Feb '19

Hi, I found a couple of certain packages suffering from build stalls until the build is aborted. When retrying the build many times, it eventually succeeds (most probably due to building on a build host, that doesn't suffer from this issue for some reason). While occasionally observable with all (x86) targets, it is reproducible with a probability near 100 with old distributions like 13.2 (yeah, lame, I know..). Given, that BS attempts to be target agnostic, let's take this as a chance to determine and avoid this pitfall in the future for all kinds of targets. Often, these stalls happen after a python3 sphinx-build is executed. Another regular pattern for these stalls is during py.test3 runs. I was able to track this issue down with "osc build --vm-type=kvm" for a 13.2 build and running build-sphinx with strace: [ 11s] + cat /proc/sys/kernel/random/entropy_avail [ 11s] 0 [ 11s] + PYTHONPATH=/home/abuild/rpmbuild/BUILDROOT/python-pyOpenSSL-18.0.0-0.x86_64/usr/lib/python3.7/site-packages [ 11s] + strace -fttvs4096 -o.trc python3 setup.py build_sphinx [ 11s] running build_sphinx [ 11s] creating /home/abuild/rpmbuild/BUILD/pyOpenSSL-18.0.0/build/sphinx [ 11s] creating /home/abuild/rpmbuild/BUILD/pyOpenSSL-18.0.0/build/sphinx/doctrees [ 11s] creating /home/abuild/rpmbuild/BUILD/pyOpenSSL-18.0.0/build/sphinx/html [ 11s] Running Sphinx v1.7.6 where the trace log ends with: 1125 20:07:26.812659 open("/dev/random", O_RDONLY) = 4 1125 20:07:26.812741 fcntl(4, F_GETFD) = 0 1125 20:07:26.812765 fcntl(4, F_SETFD, FD_CLOEXEC) = 0 1125 20:07:26.812783 poll([{fd=4, events=POLLIN}], 1, 4294967295 As far as I can tell, the /dev/random reads are initiated from python3 (v3.7.2). No idea, why it isn't using /dev/urandom, though. Since KVM IS started with some rng mechanics in place: /usr/bin/qemu-kvm -nodefaults -no-reboot -nographic -vga none -cpu host \ -object rng-random,filename=/dev/random,id=rng0 -device virtio-rng-pci,rng=rng0 [...] I wonder, why it doesn't appear inside the build: /proc/sys/kernel/random/entropy_avail is 0 here. In an attempt to fix this issue, I added this to the prjconf: Preinstall: haveged Runscripts: haveged but that doesn't change the picture. So the question boils down to: How do I get (enough) entropy into the building KVM locally and in the BS? Thanks, Pete https://build.opensuse.org/package/show/home:frispete:python/python-pyOpenS… Local system uses Linux 4.20.12, qemu-kvm-3.1.0, osc-0.164.2, build-20190123, python 3.7.2 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Preventing a project from being changed/rebuilt
by Morschhäuser, Mark 22 Feb '19

22 Feb '19

Hi, what do I have to do to prevent a project from being changed/rebuilt (because it is finished and must stay as is)? Regards, Mark -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] Is "staticlinks" still working for images?
by Julio González Gil 22 Feb '19

22 Feb '19

We upgraded one of our products to use the new version of product definitions, and it seems "staticlinks" does not work anymore, as the repositories are generated with buildnumbers. So far I discovered that using: Repotype: slepool:nobuildid OBS able to generate repositories without build numbers. However: is it possible to have both repositories with and without build numbers at the same time, as I think it was the case with "staticlinks"? -- Julio González Gil <jgonzalez(a)suse.com> Release Engineer SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

3 8

[opensuse-buildservice] git login credentials for obs source services
by Morschhäuser, Mark 20 Feb '19

20 Feb '19

Hi, I have a git host that requires logins and I want to use the obs_scm service without providing a url like user:login@host/... for every package. So I created a .gitconfig & .git-credentials file for the obsservicerun user in the obsservicerun home directory (/usr/lib/obs according to passwd) with read permissions but it seems that this file is not used by the service. If I execute the checkout command from src_service.log manually it works though. How should this be done? Do I use the wrong user account? I get this error service tar_scm failed: ERROR(128): "Cloning into '/srv/obs/service/11565/out/tmpLgoRio/testpackage'... fatal: could not read Username for 'http://giturl/foo': No such device or address <- if I use user@host, I get "could not read Password" instead " Traceback (most recent call last): File "/usr/lib/obs/service//tar_scm", line 30, in main() File "/usr/lib/obs/service//tar_scm", line 26, in main TarSCM.run() File "/usr/lib/obs/service/TarSCM/__init__.py", line 35, in run task_list.process_list() File "/usr/lib/obs/service/TarSCM/tasks.py", line 116, in process_list self.process_single_task(task) File "/usr/lib/obs/service/TarSCM/tasks.py", line 184, in process_single_task scm_object.fetch_upstream() File "/usr/lib/obs/service/TarSCM/scm/base.py", line 90, in fetch_upstream self.fetch_upstream_scm() File "/usr/lib/obs/service/TarSCM/scm/git.py", line 91, in fetch_upstream_scm <- that basically executes git clone <what> <where> os.removedirs(os.path.join(wdir, self.clone_dir)) File "/usr/lib64/python2.7/os.py", line 170, in removedirs rmdir(name) OSError: [Errno 2] No such file or directory: '/srv/obs/service/11565/out/tmpLgoRio/testpackage' Regards, Mark -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 1

[opensuse-buildservice] Combine obs_scm service with extract_file service -> unresolvable build state
by Morschhäuser, Mark 20 Feb '19

20 Feb '19

Hi, I want to use obs_scm with the extract_file service because my spec files are checked in with my sources. I used tar_scm so far and it works perfectly. So now I created a new package and added a git source to it: osc add git://url/foo.git which creates a minimal _service file. The webinterface shows me the obscpio file and obsinfo from the service but also the state is shown as "excluded" because I have no directly available spec file yet. Then I add an entry like <service name="extract_file"> <param name="archive">*.obscpio</param> <param name="files">*/*.spec</param> </service> This creates a _service:extract_file:foo.spec from the sources but then OBS is showing me an "unresolvable" build state: "nothing provides obs-service-tar, nothing provides obs-service-recompress, nothing provides obs-service-set_version" If I change the _service file back to tar_scm and remove mode="buildtime" from everywhere, then it starts building immediately. How can I do this properly? Regards, Mark -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] News from the OBS Team
by Dany Marcoux 19 Feb '19

19 Feb '19

Hey everyone, We released today a new set of changes for the revamped user interface of OBS. This time, it is for the Request pages. For details on this release, we invite you to read our blog post: https://openbuildservice.org/2019/02/15/revamping-request-ui/ We are looking forward to hearing from you The OBS Team -- Dany Marcoux <dmarcoux(a)suse.de> Full Stack Web Developer - Open Build Service SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] build flags not used for pkgs in linked project
by Olaf Hering 15 Feb '19

15 Feb '19

In a prj A, there are several pkgs that have <build><disable/><enable repository="X/></build>. If prj A is linked from another prj B to inherit all pkgs from A into B, such pkgs are built anyway in all repositories, not just in repository=X. Is there a way that prj B really considers the <build> flags of individual pkgs, without the need to _link each and every pkg from A into B? The prj of B looks like this: <project name="B"> <link project="A"/> <repository name="X" block="all" linkedbuild="all"> <path project="A" repository="X"/> <arch>x86_64</arch> </repository> <repository name="Y" block="all" linkedbuild="all"> <path project="A" repository="Y"/> <arch>x86_64</arch> </repository> </project> prj A has a similar <repository> layout, except that it does no linkedbuild. Olaf

1 0