Bug 1215000 - Challenges and Confusions Encountered While Using Localized OBS Service
Summary: Challenges and Confusions Encountered While Using Localized OBS Service
Status: NEW
Alias: None
Product: openSUSE.org
Classification: openSUSE
Component: BuildService (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Adrian Schröter
QA Contact: Adrian Schröter
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-05 11:54 UTC by Houge Langley
Modified: 2023-10-08 15:12 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Houge Langley 2023-09-05 11:54:39 UTC
1. After completing the system installation, the startup gets stuck at the OBS API, hanging for 10 minutes. This happens every time the OBS system is rebooted.

In the script located at /usr/lib/obs/server/functions.setup-appliance.sh, specifically in the function get_hostname section, fetching the local IP address takes up to 30 seconds. (In the stable version provided by OBS, it takes up to 600 seconds.) Only after reaching the 'fallback in non-interactive mode' section does it finally obtain the localhost IP address to be used for login.

2. During the compilation process in OBS, only one core is allocated by default for compiling. The official documentation does not specify where to modify the runtime environment variables. After some trial and error, we found that the configuration file is located at /etc/sysconfig/obs-server. We suggest that the documentation be improved to explain what each variable parameter represents. Currently, the documentation does not mention this, leading to confusion for most users who are using the local OBS for building and packaging."