Univention Bugzilla – Bug 34998
System setup join raises when system already joined
Last modified: 2018-04-14 13:37:18 CEST
Traceback feedback. I am not sure how this happened. Base system is not an option anymore -> Already joined. Probably two concurrent sessions, one already joined, second tried and raised? validate() does not catch that case: _check('server/role', lambda x: not(orgValues.get('joined')) or (orgValues.get('server/role') == values.get('server/role')) Either catch it in validate() or proceed in join() (if newrole == oldrole). Catching it seems to be the better way. UCS Version: 3.2-1 errata51 (Borgfeld) Execution of command 'setup/join' has failed: Exception: Base systems and already joined systems cannot be joined. raise Exception( _('Base systems and already joined systems cannot be joined.') ) File "/usr/lib/pymodules/python2.6/univention/management/console/modules/setup/__init__.py", line 198, in join func( request ) File "/usr/lib/pymodules/python2.6/univention/management/console/modules/__init__.py", line 204, in execute Traceback (most recent call last): Execution of command 'setup/join' has failed:
(In reply to Dirk Wiesenthal from comment #0) > Traceback feedback. I am not sure how this happened. Base system is not an > option anymore -> Already joined. Probably two concurrent sessions, one > already joined, second tried and raised? Maybe a standard installation as base system and then using system setup?
We had also the bug where clicking twice on save was possible while join() runs.
This can currently easily reproduced: → Bug #36807 *** This bug has been marked as a duplicate of bug 36807 ***