Is the obs appliance or the OBS Appliance Installer ISO supposed to work?
Hi all, see $SUBJECT. I need a clean 2.10 install to file bugs against osc on SLES15SP6. I checked https://openbuildservice.org/download/, downloaded the qcow image and booted it in a VM but it never came up ("a start job is running for OBS API setup", killed the VM after 10 minutes). The root password listed in the kiwi file did not work (it is not specified in plaintext apparently and having characters that are subject to keyboard layout issues in it would make it impossible to type anyway). The password was not documented anywhere else I could find it. Ok, so use the "OBS Appliance Installer ISO". However this is exactly the same as it also just dumps what is probably the same binary image onto the blockdevice and then hangs exactly the same waiting for OBS API setup and is inaccessible. Is this supposed to work at all? I followed all available documentation from openbuildservice.org but to no avail. Have fun, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
Am 04.04.25 um 10:00 schrieb Stefan Seyfried:
Is this supposed to work at all? I followed all available documentation from openbuildservice.org but to no avail.
Ok, waiting even longer after 10 minutes it finally showed the greeting screen. obsapisetup was waiting for FQDN, which it did not get because the appliance did not request via DHCP. And then of course nothing did work because "http://localhost" is not going to fly. I suggest setting a default static hostname (to be overridden by a dhcp-provided one) in the appliance would make this much more user-friendly. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
Am 04.04.25 um 10:00 schrieb Stefan Seyfried:
Is this supposed to work at all? I followed all available documentation from openbuildservice.org but to no avail.
Ok, waiting even longer after 10 minutes it finally showed the greeting screen. obsapisetup was waiting for FQDN, which it did not get because the appliance did not request via DHCP. And then of course nothing did work because "http://localhost" is not going to fly. I suggest setting a default static hostname (to be overridden by a dhcp-provided one) in the appliance would make this much more user-friendly. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
participants (1)
-
Stefan Seyfried