Univention Bugzilla – Bug 43978
clean-up scripts for the exam mode do not clean the "exam mode group" (master and schoolslave)
Last modified: 2017-10-16 21:34:00 CEST
clean up scripts for the exam mode do not clean up the "exam mode group" both on the master and school slaves. The clients have to be removed manually.
The users are removed correctly from the exam group but the computer accounts are still left within the exam group.
Added --skip-exam-computer-removal to skip removal of all computer accounts from the exam groups of all schools. Otherwise it will be done by default. * ce8decc0b6c3ebc75140284d4c931e009db3e094 * 10ec2fa1bf1cd7635489865c5b8797b9f7808f43 * cada98b151b582963cfdef0dfb63bbf46ff0146c Package: ucs-school-umc-exam Version: 7.0.4-14A~4.2.0.201709131826 Branch: ucs_4.2-0 Scope: ucs-school-4.2
Reopened to check, if finish() does or doesn't always remove computer accounts.
(In reply to Daniel Tröder from comment #3) > Reopened to check, if finish() does or doesn't always remove computer > accounts. The UMC command unset_computerroom_exammode / finish_exam() does remove the computer objects from the exam group as long as it knows the room it was conducted in. The information that an exam took place is stored in a file. If that file was somehow corrupted or deleted, the information would be lost. Only in the case that this information was lost, would the the added cleanup function actually do something the unset_computerroom_exammode would not have already done. So IMHO it does make sense to include it, because the whole point of this script is to handle "something that shouldn't be".
Please have a look at the code comments: https://git.knut.univention.de/univention/ucsschool/commit/d5e8aaf4894c531c9cd0b4018ae16b605e7abd9d
437f77e5: initialize udm module only once ucs-school-umc-exam 7.0.4-17A~4.2.0.201710091026
OK: Looks good now. The hosts are removed from the exam group afterwards. OK: YAML
UCS@school 4.2 v4 has been released. http://docs.software-univention.de/changelog-ucsschool-4.2v4-de.html If this error occurs again, please clone this bug.