|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast Installtion server can be started in multiple instances only last configuration is saved | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Birger Kollstrand <birger.kollstrand> |
| Component: | YaST2 | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED FEATURE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Milestone 8 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Yast log files form save_y2logs | ||
You should not start multiple YaST instances, that's an unsupported scenario. (Sorry, no time to implement proper locking....) Please, In stead of closing this. Can it be moved to 11.3? I'd suggest entering the feature to openfate (https://features.opensuse.org/). If the responsible managers find the request interesting they can allocate resources for implementation. Done. Thanks for the suggestion Ladislav. https://features.opensuse.org/307912 |
Created attachment 320969 [details] Yast log files form save_y2logs User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-1.3 Firefox/3.5.3 When setting up MS8 for testing I use the Installation server. To be smart I opened two instances to ready both 32 and 64 bit at the same time. That worked, both are copied to the correct directory at /srv/install/. The problem is that when I now start the "Installation Server" again it only shows one of the builds. I guess the problem is that it saves the configuration at program exit and the one that is closed last "wins". As I see it, either the Installation Server should not accept being started in multiple instances or it should lock the config file for writing so there is no race condition risk. Reproducible: Always Steps to Reproduce: 1.Install "Installation Server" 2.Start Installation server and add a new repository/build 3.Without closing the first instance, open a new Installation server and load a second repository/build 4.When both ar completed. Close one. 5.Close the second. Actual Results: Start the installation server again and you will se that only one configuration remains. not both loaded/installed. Expected Results: Eiter only accept one instance at a time or lock the config file for writing, read file, add data, close config file, remove lock.(An atomic operation)