Bug 43352 - Setting UCR variables during the setup cleanup scripts fails?
Setting UCR variables during the setup cleanup scripts fails?
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: System setup
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on: 42808
Blocks: 43067
  Show dependency treegraph
 
Reported: 2017-01-17 15:09 CET by Alexander Kläser
Modified: 2019-01-03 07:20 CET (History)
5 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 5: Will affect all installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.171
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2017-01-17 15:09:12 CET
I ran into this problem, as well, with my local docker instance. Inspecting the log, I am a bit puzzled. The log file says that the UCR variable system/setup/boot/start is set (in this case to "false") and the variable umc/module/setup/wizard/disabled for disabling the setup wizard, as well. However, inspecting my system reveals that both variables are not set! Could that be some sort of bug with UCR? I just want to make sure that there is no other problem here that we previously missed.

The removal of the package fails due to missing aptitude. This has been resolved by bug 42808
.

=== Running cleanup-pre scripts (2017-01-11 10:23:04) ===
= Running 05_updating_setup_status_file
= Running 80_ucr_unset_system_setup_boot
Setting system/setup/boot/start
Create umc/module/setup/wizard/disabled
Setting nssldap/timelimit
Setting apache2/startsite
File: /etc/apache2/ucs-sites.conf.d/ucs-sites.conf
Unsetting system/setup/prev/apache2/startsite
Reloading web server config: apache2 failed!
= Running 95_unset_temporary_interfaces
= Running 99_restart_umc
Unsetting apache2/ssl/certificate
Unsetting apache2/ssl/key
Unsetting apache2/ssl/ca
Multifile: /etc/simplesamlphp/metadata/saml20-idp-hosted.php
Multifile: /etc/apache2/sites-available/default-ssl
Restarting Univention Management Console Server.
done.
Restarting Univention Management Console Web Server.
done.
Restarting web server: apache2 ... waiting .
=== done (2017-01-11 10:23:09) ===

=== Running cleanup-post scripts (2017-01-11 10:23:09) ===
= Running 05_remove_setup_status_file
= Running 08_activate_license
= Running 09_update_app_center_cache
Downloading "https://appcenter.software-univention.de/meta-inf/4.1/index.json.gz"...
Downloading "https://appcenter.software-univention.de/meta-inf/4.1/index.json.gz.gpg"...
Downloading "https://appcenter.software-univention.de/meta-inf/categories.ini"...
Downloading "https://appcenter.software-univention.de/meta-inf/rating.ini"...
Downloading "https://appcenter.software-univention.de/meta-inf/license_types.ini"...
0 file(s) are new
= Running 10_notifier_listener_restart
= Running 20_amavis_restart
= Running 80_clear_package_cache
= Running 90_remove_univention_system_setup_boot
/tmp/tmp7Tbyxf/post/90_remove_univention_system_setup_boot: 38: /tmp/tmp7Tbyxf/post/90_remove_univention_system_setup_boot: aptitude: not found
= Running 95_remove_setup_status_file
=== done (2017-01-11 10:23:16) ===

========== 8< ==========
$ ucr search --brief boot/start
system/setup/boot/start: true
$ ucr search --brief umc.*disable
umc/module/.*/.*/disabled: <empty>
umc/module/udm/users/self/disabled: true
========== 8< ==========


+++ This bug was initially created as a clone of Bug #42808 +++

Happend in technical training on 8 machines and possibly on a customer system:
http://forum.univention.de/viewtopic.php?f=56&t=6180

All machines in technical training have been installed via ISO on a USB stick. The debian installer and the webbased system setup part have been successfully gone through. But: network was not available during system setup part AND automatic update in the end of installation has been deselected.
The systems seemed to be fine after installation and rebootet fine to commandline. 

Later on, the network connectivity was restored and univention-upgrade has been performed on command line. After reboot, univention system setup was shown ==> UCRV system/setup/boot/start was "true"

I was able to reproduce this problem on a system installed without network access (ethernet interface was present, but no switch attached). I would bet that the script 
univention-system-setup/usr/lib/univention-system-setup/cleanup-post.d/90_remove_univention_system_setup_boot
is the culprit. The following aptitude command seems to have failed or performed only half-way:

aptitude -q -y markauto univention-system-setup-boot- \
     univention-management-console-web-server \
     univention-management-console-module-setup </dev/null

When reproducing the problem, aptitude showed the status "id" (installed, marked for deletion) right before calling univention-upgrade 
→ univention-system-setup-boot is still installed.

# dpkg --get-selections univention-system-setup-boot
univention-system-setup-boot       install
#
Comment 1 Erik Damrose univentionstaff 2017-01-17 15:15:00 CET
Please check if the UCRv is not set in any other UCR layer (ldap, force)
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:20:43 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

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