Bug 1201602

Summary: /usr/sbin/named-checkconf do not consider chrooted bind
Product: [openSUSE] openSUSE Distribution Reporter: Ralf Kölmel <ralf.koelmel>
Component: Upgrade ProblemsAssignee: Jorik Cronenberg <jorik.cronenberg>
Status: RESOLVED INVALID QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: max
Version: Leap 15.4   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: named journal complaing missing log files

Description Ralf Kölmel 2022-07-18 15:16:55 UTC 
Created attachment 860231 [details]
named journal complaing missing log files

/usr/sbin/named-checkconf is complaining about missing log files under /var/log even if the bind process is started in a chrooted environment where these log files are under <base chroot >/log and the files under /var/log are not used after startup.
This wrong check doesn't allow the startup of the bind service.

The chroot environment is also missing <base chroot >/var/log or has removed this directory, which has to be restored from Leap 15.3.

It is a similiar bug as mentioned under https://bugzilla.opensuse.org/show_bug.cgi?id=1200995 which is mentioning some adaptations to the config which must still manually be done.
Comment 1 Jorik Cronenberg 2022-08-02 12:36:00 UTC 
As stated in bind.changes:

-------------------------------------------------------------------
Tue Oct 19 14:00:56 UTC 2021 - Josef Möllers <josef.moellers@suse.com>
...
  *** MAJOR CHANGE ***
  Changed protection of/against "named" from chroot jail to
  systemd protection. This obsoletes subpackage named-chrootenv.

We don't support the chroot environment in Leap 15.4 anymore, since systemd now handles the protections of the system.