November 2017 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[kubic-bugs] [Bug 1069906] New: Race: systemd remounts filesystems while apparmor loads profiles
by bugzilla_noreply＠novell.com 19 Apr '18

19 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1069906 Bug ID: 1069906 Summary: Race: systemd remounts filesystems while apparmor loads profiles Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org, systemd-maintainers(a)suse.de Found By: --- Blocker: --- Created attachment 750174 --> http://bugzilla.suse.com/attachment.cgi?id=750174&action=edit output of journalctl >From time to time I still see on openSUSE Kubic/SUSE CaaS Plattform: Nov 27 10:11:02 localhost apparmor.systemd[449]: Loading AppArmor profiles Nov 27 10:11:02 localhost apparmor.systemd[449]: mkstemp: Read-only file system Nov 27 10:11:02 localhost apparmor.systemd[449]: Error: /etc/apparmor.d/bin.ping failed to load The problem is, that the filesystem is mounted in initrd, but after that, systemd remounts all filesystems. And apparmor is running in this time, where the filesystem is not completly mounted. This may work if apparmor would not try to write to disk during this time. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[kubic-bugs] [Bug 1064411] New: salt fails to generate certificates
by bugzilla_noreply＠novell.com 13 Apr '18

13 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1064411 Bug ID: 1064411 Summary: salt fails to generate certificates Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 745294 --> http://bugzilla.suse.com/attachment.cgi?id=745294&action=edit salt/minion.log During bootstrapping the cluster, salt fails to create the needed certificates for velum. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kubic-bugs] [Bug 1069784] New: No repositories after installation
by bugzilla_noreply＠novell.com 22 Jan '18

22 Jan '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1069784 Bug ID: 1069784 Summary: No repositories after installation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: mkravec(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After installation from DVD there are no repositories in the system: I installed: openSUSE-Tumbleweed-Kubic-DVD-x86_64-Snapshot20171123-Media.iso # zypper lr -u # | Alias | Name | Enabled | GPG Check | Refresh | URI --+--------------------------------------+--------------------------------------+---------+-----------+---------+-------------------------------------------------------- 1 | openSUSE-Tumbleweed-Kubic-20171123-0 | openSUSE-Tumbleweed-Kubic-20171123-0 | Yes | (r ) Yes | No | cd:///?devices=/dev/disk/by-id/ata-QEMU_DVD-ROM_QM00001 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kubic-bugs] [Bug 1070170] New: man not working with transactional updates (/var)
by bugzilla_noreply＠novell.com 16 Jan '18

16 Jan '18

http://bugzilla.suse.com/show_bug.cgi?id=1070170 Bug ID: 1070170 Summary: man not working with transactional updates (/var) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Man has a tempfile config, which creates /var/cache/man man initializes this directory in the %posttrans section. This will not work with transactional-updates and the new /var layout. We could e.g. only run the %posttrans if /var/cache/man exists, else we need a service file doing that during first boot after installation/update. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kubic-bugs] [Bug 1070565] New: [20171129] Failed to start Postfix Mail Transport Agent
by bugzilla_noreply＠novell.com 30 Nov '17

30 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1070565 Bug ID: 1070565 Summary: [20171129] Failed to start Postfix Mail Transport Agent Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: dleuenberger(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE Kubic 1129 shows a new error in the log related to postfix: https://openqa.opensuse.org/tests/546268#step/journal_check/10 With snapshot 1129, cronie had a change that newly pulls in an smtp_daemon (and postfix is providing this capability) +Fri Nov 24 17:25:56 UTC 2017 - kstreitova(a)suse.com + +- Requires smtp_daemon (not just Recommends) as it's needed by + run-crons script [bsc#1064834] -- You are receiving this mail because: You are the assignee for the bug.

1 2

[kubic-bugs] [Bug 1064834] run-crons fails with: "Could not find suitable mailer." cronie should require mailer
by bugzilla_noreply＠novell.com 30 Nov '17

30 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1064834 http://bugzilla.opensuse.org/show_bug.cgi?id=1064834#c10 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbrown(a)suse.com --- Comment #10 from Richard Brown <rbrown(a)suse.com> --- Proposed fix https://build.opensuse.org/request/show/546703 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1064834] run-crons fails with: "Could not find suitable mailer." cronie should require mailer
by bugzilla_noreply＠novell.com 30 Nov '17

30 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1064834 Dominique Leuenberger <dleuenberger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1070565 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1064834] run-crons fails with: "Could not find suitable mailer." cronie should require mailer
by bugzilla_noreply＠novell.com 30 Nov '17

30 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1064834 http://bugzilla.suse.com/show_bug.cgi?id=1064834#c9 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |dleuenberger(a)suse.com, | |kubic-bugs(a)opensuse.org Resolution|FIXED |--- Severity|Normal |Critical --- Comment #9 from Thorsten Kukuk <kukuk(a)suse.com> --- The fix is wrong. Why? If you look at the run-crons script, cronie does not need a smtp_daemon at all, but a mail client. So please change: Requires: smtp_daemon Suggests: postfix To: Requires: mail Suggests: mailx The wrong requirement of a smtp_daemon breaks Kubic. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1069906] Race: systemd remounts filesystems while apparmor loads profiles
by bugzilla_noreply＠novell.com 27 Nov '17

27 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1069906 http://bugzilla.opensuse.org/show_bug.cgi?id=1069906#c2 --- Comment #2 from Christian Boltz <suse-beta(a)cboltz.de> --- This is... interesting ;-) John already explained the reason for the errors. Let me add that running "rcapparmor reload" in the running system (when /var/lib/apparmor/ is writeable) will also update the cache. There are more interesting things: apparmor.service has After=var.mount var-lib.mount so I'd expect it to start late enough. (Note that apparmor.service should start as early as possible - the profiles have to be loaded before the programs they confine start.) I also wonder about a few lines in your log, especially Nov 27 10:11:02 localhost systemd[1]: var-lib-overlay.mount: Unit is bound to inactive unit dev-vda2.device. Stopping, too. Nov 27 10:11:02 localhost systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive. Nov 27 10:11:02 localhost systemd[1]: var-lib-overlay.mount: Failed to enqueue stop job, ignoring: Transaction is destructive. I don't know what these messages mean exactly, but (assuming/guessing that they refer to an overlay mount for /var/lib/) they could be a part of the puzzle. I never tried Kubic or Caas, therefore I can only guess what happens, and hope that the above hints help you to understand the problem. If you have an idea how to handle this (ideally without delaying loading the profiles), please tell me ;-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1069906] Race: systemd remounts filesystems while apparmor loads profiles
by bugzilla_noreply＠novell.com 27 Nov '17

27 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1069906 http://bugzilla.opensuse.org/show_bug.cgi?id=1069906#c1 John Johansen <jrjohansen117(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jrjohansen117(a)gmail.com --- Comment #1 from John Johansen <jrjohansen117(a)gmail.com> --- AppArmor is probably not finding a binary cache of policy so it is trying to compile policy. This can be disabled in two ways. 1. provide a binary cache file matching the kernel 2. Disable writing the cache file, and the compile if needed will only go to the kernel and not be cached for further boots. This can be done by editing the /etc/apparmor/parser.conf and commenting out the line that has write-cache Note: doing 2 will potentially slow down boot as if a cache file is not found policy will be recompiled on every boot. -- You are receiving this mail because: You are on the CC list for the bug.

1 0