Univention Bugzilla – Bug 54336
61_notifier_protocol_version fails on non-primary even on fresh installations
Last modified: 2022-01-26 20:42:29 CET
The ucr variable notifier/protocol/version is checked in a new diagnostic module since Bug #50733. This check fails even on fresh UCS5 installations if the diagnostic module is installed on e.g replica- or memberservers since the ucr variable is only set when the univention-directory-notifier is installed. Maybe the check should be skipped if the notifier is not installed to avoid confusion.
After fixing this bug, revert the skipping of the checks in ucs-test by reverting git commits f6321a78 and 6e1b818d
For example https://jenkins.knut.univention.de:8181/job/UCS-5.0/job/UCS-5.0-1/view/Default/job/AutotestUpgrade/38/SambaVersion=no-samba,Systemrolle=member/testReport/00_checks/81_diagnostic_checks/test_run_diagnostic_checks/ failed.
univention-management-console-module-diagnostic.yaml 8dcc1814f05b | Bug #54336: yaml ucs-test (10.0.6-95) ec76712270b0 | Bug #54336: adjust notifier-protocol-version-test for memberserver Package: univention-management-console-module-diagnostic Version: 6.0.0-20A~5.0.0.202201211903 Branch: 5.0-1
OK: 61_notifier_protocol_version is skipped on non-master/backup OK: test is not skipped anymore OK: no advisory/yaml entry necessary as the plugin is not yet released.
Since the package has been rebuilt, the existing advisory needs to be updated, otherwise Bug #53969 e.g. cannot be released.
(In reply to Arvid Requate from comment #5) > Since the package has been rebuilt, the existing advisory needs to be > updated, > otherwise Bug #53969 e.g. cannot be released. Well okay but this is just a fixup for the not released Bug #54264. So what to write into the YAML? I don't think for this case a YAML entry is required. I can mark it as duplicate of Bug #54264 otherwise.
Ah sorry, already don via 8dcc1814f0