Bug 27168 - 98univention-samba4-dns.inst not called on post-install
98univention-samba4-dns.inst not called on post-install
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Samba4
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
:
: 27910 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-18 13:29 CEST by Andreas Büsching
Modified: 2019-11-21 17:50 CET (History)
6 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?: 2: Will only affect a few 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.023
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
console dump (30.08 KB, text/plain)
2016-02-02 15:07 CET, Philipp Hahn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Büsching univentionstaff 2012-05-18 13:29:27 CEST
Nach der Installation eines singlemaster waren die folgenden Join-Skripte noch nicht ausgeführt:

98univention-samba4-dns.inst
98univention-squid-samba4.inst

Mit univention-run-join-scripts konnte die Skripte ausgeführt werden.
Comment 1 Janis Meybohm univentionstaff 2012-06-04 14:57:01 CEST
Das tritt auch auf UCS Systemen auf. In internen Testumgebungen und bereits bei Kunden beobachtet. Z.B.: Ticket#: 2012053121002431
Comment 2 Rico Schäfer 2013-01-13 16:41:58 CET
Ich konnte es soeben auch auf einem Kundensystem reproduzieren. Das Ausführen von "univention-run-join-scripts" schlug auch fehl:
Running 98univention-samba4-dns.inst                       failed (exitcode: 1)

Gibt es noch einen anderen Lösungsvorschlag?
Comment 3 Stefan Gohmann univentionstaff 2013-01-13 20:12:54 CET
In diesem Bug geht es nur darum, dass die Join Skripte beim Nachinstallieren von Samba 4 nicht automatisch ausgeführt werden.

(In reply to comment #2)
> Ich konnte es soeben auch auf einem Kundensystem reproduzieren. Das Ausführen
> von "univention-run-join-scripts" schlug auch fehl:
> Running 98univention-samba4-dns.inst                       failed (exitcode: 1)
> 
> Gibt es noch einen anderen Lösungsvorschlag?

Es müsste ein Hinweis in /var/log/univention/join.log stehen. Am besten alles weitere über Forum oder über unseren Support:
 http://forum.univention.de
Comment 4 Arvid Requate univentionstaff 2014-08-28 14:27:05 CEST
*** Bug 27910 has been marked as a duplicate of this bug. ***
Comment 5 Arvid Requate univentionstaff 2014-08-28 14:27:31 CEST
Alternatively the univention-s4-connector.postinst could also run the univention-samba4-dns joinscript on a master.
Comment 6 Philipp Hahn univentionstaff 2016-02-02 15:07:55 CET
Created attachment 7449 [details]
console dump

# univention-install univention-samba4 univention-s4-connector
...
Vormals nicht ausgewähltes Paket univention-samba4 wird gewählt.
...
Joinscript 31univention-nagios-s4-connector.inst finished with exitcode 0
...
Joinscript 96univention-samba4.inst finished with exitcode 0
...
Joinscript 97univention-s4-connector.inst finished with exitcode 0
...

# univention-check-join-status 
Warning: 'univention-samba4-dns' is not configured.
Error: Not all install files configured: 1 missing

# dpkg -S univention-samba4-dns
univention-samba4: /usr/lib/univention-install/98univention-samba4-dns.inst

# grep -n call_joinscript /var/lib/dpkg/info/univention-samba4.postinst
349:call_joinscript 96univention-samba4.inst

# univention-run-join-scripts
...
Running 98univention-samba4-dns.inst                       done

So why is it not called by default from any .postinst?
Comment 7 Arvid Requate univentionstaff 2016-02-02 16:33:05 CET
> Alternatively the univention-s4-connector.postinst could also run the univention-samba4-dns joinscript on a master

98univention-samba4-dns.inst is part of the package univention-samba4 but it needs to be run after there is a S4-Connector running in the Domain.
Comment 8 Stefan Gohmann univentionstaff 2019-01-03 07:23:23 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.