Bug 56363 - 91univention-saml.inst assumes it failed if it was already executed
91univention-saml.inst assumes it failed if it was already executed
Status: NEW
Product: UCS
Classification: Unclassified
Component: SAML
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2023-07-28 14:38 CEST by Jürn Brodersen
Modified: 2023-08-28 14:12 CEST (History)
1 user (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?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.086
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
error message (15.54 KB, text/plain)
2023-07-28 14:38 CEST, Jürn Brodersen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jürn Brodersen univentionstaff 2023-07-28 14:38:05 CEST
Created attachment 11100 [details]
error message

The join script checks the last return code to see if it failed. This way it assumes it failed because "joinscript_init" returns 1 and exits the joinscript if it was already executed. The message doesn't break anything, but is confusing. I noticed it during a package upgrade.

How to reproduce:
apt install --reinstall univention-saml

I think moving the trap registration part under the "joinscript_init" command, should help. https://git.knut.univention.de/univention/ucs/-/tree/5.0-4/saml/univention-saml#L95

By the way, that whole debug print is an interesting idea :)
Comment 1 Christina Scheinig univentionstaff 2023-08-28 14:12:52 CEST
(In reply to Jürn Brodersen from comment #0)
> Created attachment 11100 [details]
> error message
> 
> The join script checks the last return code to see if it failed. This way it
> assumes it failed because "joinscript_init" returns 1 and exits the
> joinscript if it was already executed. The message doesn't break anything,
> but is confusing. I noticed it during a package upgrade.
> 
> How to reproduce:
> apt install --reinstall univention-saml
> 
> I think moving the trap registration part under the "joinscript_init"
> command, should help.
> https://git.knut.univention.de/univention/ucs/-/tree/5.0-4/saml/univention-
> saml#L95
> 
> By the way, that whole debug print is an interesting idea :)

I could find other words for that. I thing this must be configurable, otherwise we need to modify the joinscript, getting rid of this messages everytime to find the error. This is worse than spam, for a non developer. ( no offense )
I searched for the Bug where this was introduced, but did not find it.