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
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
Hi guys,
can it be that the public keys for Fedora 25/26/27 and Rawhide are not
setup correctly on the OBS? I get "public key not available" errors
when building locally.
Not sure if this is a local issue or to be fixed on the OBS, because I
find mails stating both...
Kind Regards,
Johannes
Hi,
this morning, I get warnings that the file repomd.xml from some repos
has been signed with an unknown key.
devel_languages_go AF4CFE4D307D7BF9
devel_languages_python 27163A4EEDF0D733
devel_languages_ruby_extensions 9AF0C9A20E9AF123
devel_tools_scm 30A8343A498D5A23
network 62EB1A0917280DDF
Packman 45A1D0671ABD1AFB
What's gone wrong? Did I miss something? The repo's URLs all start with
<http://download.opensuse.org/repositories/>, and there are several
repos that have their repomd.xml signed with the usual key.
BTW, I'm not asked to accept a changed key for the repos, so the repo
keys should be unchanged, just those files have been signed with other keys.
Werner
--
Hi All,
In OBS at:
https://github.com/openSUSE/open-build-service/blob/master/src/backend/bs_w…
the '--lint' option is unconditionally always passed to the 'build' command:
push @args, '--lint';
And in the build command at:
https://github.com/openSUSE/obs-build/blob/master/build#L1214
this results in 'rpmlint-Factory' being unconditionally added to
$ADDITIONAL_PACKS
test -z "$DO_LINT" || ADDITIONAL_PACKS="$ADDITIONAL_PACKS rpmlint-Factory"
This will be case even for non rpm builds, such as Debian .dsc builds, and
for target rpm distribution repositories that might have or support this
additional package such Fedora. This seems clearly wrong.
This will result in an invocation like:
/bin/bash /usr/lib/build/init_buildsystem --configdir
/usr/lib/build/configs --cachedir /var/cache/build --rpmlist
/var/tmp/osc-buildpackage/rpmlist.nRE0pS
/var/tmp/osc-buildpackage/my_package_1.2.3.dsc rpmlint-Factory
(init_build appears to ignore the rpmlint-Factory argument, thought I'm not
sure specifically why as I'm don't understand how init_build and expanddeps
work, but it's clearly wrong to pass rpmlint-Factory to .dsc build
targeting a Debian distribution repository)
Should the above $DO_LINT test also test $BUILDTPYE to make sure it's a
.spec build? (And thus not add the additional package for .dsc builds)
Going even further should the '--lint' option perhaps be removed from the
build command, and OBS not set this? It seems that simply using 'Support:
rpmlint-Factory' in the prjconf for those projects that want and can use
this would be the appropriate way to control this.
(It appears the actual invocation of 'rpmlint' for .spec builds is
controlled by '$DO_CHECKS' and passing '--nochecks')
Thanks,
Nick
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Good evening there,
I have noticed that builds for my repository are stuck to 2 days ago.
Using `osc rbuild PACKAGE` doesn't work too.
My repository is: home:ItachiSan:archlinux
Is this a known problem (server maintenance?) or should I report it?
Regards
--
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
Is there a way to force the usage of build-compare for all pkgs in a prj?
According to the buildlog build-compare gets installed, but at the end of the build it is not used.
That behavior is probably cool for bootstrap, but bad for everything else.
Olaf
Dear OBS community,
from last night onwards pretty much all of our aarch64 builds are failing
due to what appears to be some serious problems on the buildhost (see attached
mails with log snippets).
among the "interesting" messages are:
[ 328s] [ 291.436030] dracut-initqueue[468]: Warning: Could not boot.
[ 347s] qemu-system-aarch64: terminating on signal 15 from pid 38856 (fuser)
[ 340s] dracut:/# ### WATCHDOG TRIGGERED, KILLING VM ###
[ 18s] objdump: /boot/Image.guest: File format not recognized
[ 322s] Warning: /dev/disk/by-uuid/00750419-b769-40be-aa7a-a81dca13c577 does not exist
This is not critical for us, but I guess somebody will want to have a look at this
at some point :) Thanks!
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)