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
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
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
How does one get a copy of a deleted package?
For owned projects 'undelete' would work, for foreign project it does not.
'osc log' is apparently capable of working with a deleted package, while checkout and copypac just fail.
Olaf
Hi guys,
I remember someone describing how to do this on the list, but I cannot
find it for the life of me.
I think there was a way to keep "branches"-subprojects, that are
automatically created by OBS when doing "osc branch foo/bar". But they
are also deleted when the only package in there is being submitted and
the SR is accepted.
Am I remembering this right? Is there a way to achieve that? Or is my
memory playing tricks on me?
Kind Regards
Johannes
Hello,
It seems that since 20180319 the armv7 remaining jobs were burn down
twice (16.4. and 22.4.) and the workers became idle at that time. But
there was nothing released to the repos. So the latest release was 20180319.
There is also a job hanging since more than 20 days due to a kernel
crash of the build host:
https://build.opensuse.org/package/live_build_log/hamradio/conlogv/openSUSE…
Can some admin please check this?
Br,
Frank
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Since around easter, when I build a docker image, instead of the image
file, I get a new file
Name
https://download.opensuse.org/repositories/isv:/B1-Systems:/Horde5:/opensus…
Content
Container can be pulled via:
docker pull docker://https://obs-registry.obsmgmt.opensuse.org:444/isv/b1-systems/horde5/opensuse-appliance/images/x86_64/horde5-developer:latest
Web Searching around, I did not find any docs related to this change (may have used the wrong terms though).
The published URL looks broken, but even several mutations of this string did not yield anything.
Can you point me to existing docs or bug reports which I can watch? Can I somehow directly access the container file like before?
Regards
Ralf
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi!
I'm experimenting with mass producing R packages for opensuse
using some scripts.
Therefore I set up a test project home:dsteuer:CRANtest .
Experiments work ok so far, but if I have to start from scratch
for a package there are problems I don't understand.
A current package with problems is "abe" in OBS it is called "R-abe".
It worked *once* to put it into the OBS. Then I wanted to test
my script and tried to delete it from OBS.
I did:
osc delete R-abe
checked in the webinterface and it was gone there.
I now can't (how I expected)
osc co R-abe
any longer without an error:
steuer@gaia:~/OBS/home:dsteuer:CRANtest> osc co R-abe
Server returned an error: HTTP Error 404: Not Found
Error getting meta for project 'home%3Adsteuer%3ACRANtest' package
'R-abe'
When I try
steuer@gaia:~/OBS/home:dsteuer:CRANtest> osc rdelete R-abe
I get
steuer@gaia:~/OBS/home:dsteuer:CRANtest> osc rdelete R-abe
Waiting for Emacs...
Server returned an error: HTTP Error 404: Not Found
R-abe
So the package is somehow gone, but somehow still there.
As probably expected it is possible to do
osc mkpac R-abe
(the directory is created and empty)
but copying files there and than
osc addremove
osc ci
results in
steuer@gaia:~/OBS/home:dsteuer:CRANtest/R-abe> osc ci
Deleting R-abe
Server returned an error: HTTP Error 404: Not Found
home:dsteuer:CRANtest/R-abe
Why that Deleting line?
My questions now:
How to clean up the test project? (I can start over, but there must be
a proper way.) There is a handful of packages with that problem.
What is the correct dance of commands to reliably remove a package
from a project such that it can be recreated later.
Thx
Detlef
--
'People who say "I have nothing to hide" misunderstand the purpose of
surveillance. It was never about privacy. It's about power.' E. Snowden
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org