Open Build Service network setup failed

English Virtualization
#1

I’m trying to setup OBS in virtualbox. I set up network adapter in bridged mode for the virtual machine. And after OBS start I see:
https://dl.dropboxusercontent.com/u/9926406/obs_fail_01.png

here is ifconfig:
https://dl.dropboxusercontent.com/u/9926406/obs_fail_02.png

and wget is working, so connection to internet and working dns server present:
https://dl.dropboxusercontent.com/u/9926406/obs_fail_03.png

where should I start to fix the OBS problem with network?

#2

On Sun 07 Jun 2015 10:06:02 AM CDT, g4852251 wrote:

I’m trying to setup OBS in virtualbox. I set up network adapter in
bridged mode for the virtual machine. And after OBS start I see:
[image: https://dl.dropboxusercontent.com/u/9926406/obs_fail_01.png]

here is ifconfig:
[image: https://dl.dropboxusercontent.com/u/9926406/obs_fail_02.png]

and wget is working, so connection to internet and working dns server
present:
[image: https://dl.dropboxusercontent.com/u/9926406/obs_fail_03.png]

where should I start to fix the OBS problem with network?

Hi
That looks all normal, you need to configure a FQDN (set up a
hostname), assign a fixed ip address and all should be good to
go for connecting from a web browser.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

#3

That’s odd, but if I use http://my_virtualbox_ip, the server gives me a page with:
OBS appliance could not get setup, no network found

But if I open https://my_virtualbox_ip, the server really tries to start obs webgui, but throws an error:
https://dl.dropboxusercontent.com/u/9926406/obs_fail_04.png

So, it is much better. Now I see, that it tries to start.
Any ideas what can fix the error? Or maybe it should be in another thread?

#4

On Mon 08 Jun 2015 05:06:01 PM CDT, g4852251 wrote:

malcolmlewis;2713967 Wrote:
> Hi
> That looks all normal, you need to configure a FQDN (set up a
> hostname), assign a fixed ip address and all should be good to
> go for connecting from a web browser.
>

That’s odd, but if I use http://my_virtualbox_ip, the server gives me a
page with:
OBS appliance could not get setup, no network found

But if I open https://my_virtualbox_ip, the server really tries to start
obs webgui, but throws an error:
[image: https://dl.dropboxusercontent.com/u/9926406/obs_fail_04.png]

So, it is much better. Now I see, that it tries to start.
Any ideas what can fix the error? Or maybe it should be in another
thread?

Hi
Not sure, it was awhile back I set a build service instance up, but
wound up installing yast2-network to configure the FQDN, static ip
address and then all was good.

I can do a test install in a vm to check it out if you like?

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

#5

Strictly speaking re: the error… and of course error output isn’t always accurate…

Is there some reason why you didn’t configure your VM as a NAT connection and configured the VM networking as a DHCP client? Doing so would have automatically configured a DHCP configuration complete with DNS fulfilling both the supposed “missing” network configurations.

Am speculating that’s what the setup is configured to expect, so although you might think that might not be necessary, why not give the config what it wants?

Since it looks like your configured physical network is a Class C private network, the only gotcha to be careful of is that your NAT address space isn’t the same as the physical network.

TSU