Bug 47033 - univention-register-network-address hangs in appliance fast demo mode
univention-register-network-address hangs in appliance fast demo mode
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: System setup
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-05-18 11:54 CEST by Felix Botner
Modified: 2022-08-01 19:06 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Botner univentionstaff 2018-05-18 11:54:16 CEST
One of the appliance tests (kopano) failed because during the network setup all interfaces are "restarted" (down/up) which started /usr/sbin/univention-register-network-address and this command never returned (i could see the umc-command ip/change process which is started by univention-register-network-address).

This caused a timeout in UMC and the setup could not be continued.

But this system was "unjoined", there is no chance univention-register-network-address could have worked anyway

-> better do not start umc-command ip/change in univention-register-network-address if the system is not joined
Comment 1 Felix Botner univentionstaff 2018-05-18 12:16:04 CEST
(In reply to Felix Botner from comment #0)
> One of the appliance tests (kopano) failed because during the network setup
> all interfaces are "restarted" (down/up) which started
> /usr/sbin/univention-register-network-address and this command never
> returned (i could see the umc-command ip/change process which is started by
> univention-register-network-address).
> 
> This caused a timeout in UMC and the setup could not be continued.
> 
> But this system was "unjoined", there is no chance
> univention-register-network-address could have worked anyway
> 
> -> better do not start umc-command ip/change in
> univention-register-network-address if the system is not joined

this was not the problem here, the system was a ucs app appliance with the fast demo mode enabled, /etc/machine.secret existed on the system

but the result is the same univention-register-network-address -> mc-command ip/change hangs forever
Comment 2 Ingo Steuwer univentionstaff 2021-05-14 16:47:16 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.