[Bug 1905212] Re: On 20.04 arm64 (raspberry) can't install cockpit from focal-backports

2020-11-24 Thread Martin Pitt
Sorry, it wasn't built on armhf/arm64 yet: https://launchpad.net/ubuntu/+source/cockpit/231-1~ubuntu20.04.1 There's currently some hw maintenance going on: https://lists.ubuntu.com/archives/launchpad- announce/2020-November/000107.html -- You received this bug notification because you are a

[Bug 1905212] Re: On 20.04 arm64 (raspberry) can't install cockpit from focal-backports

2020-11-24 Thread Martin Pitt
This is the wrong way to invoke apt, as the package/release syntax will install *only* that package from backports, but resolve all dependencies from main. Please try this: sudo apt install -t focal-backports cockpit ** Changed in: cockpit (Ubuntu) Status: New => Invalid -- You

[Bug 1892756] Re: System libvirt-dbus broken after changing libvirtd.socket SocketMode to 0660

2020-08-25 Thread Martin Pitt
ISTM that adding the libvirt-dbus user into the libvirt group is the right fix here. According to /usr/share/dbus-1/system.d/org.libvirt.conf only root and libvirt group users can call its interface. So that useradd seems correct to me, and it should be put into the Debian package. Unfortunately

[Bug 1885188] Re: fatrace autopkgtest failure due to rename test

2020-08-22 Thread Martin Pitt
https://github.com/martinpitt/fatrace/releases/tag/0.16 I uploaded this to Debian as well, from where it should get auto- imported into groovy. ** Changed in: fatrace Status: Fix Committed => Fix Released ** Changed in: fatrace (Ubuntu) Status: In Progress => Fix Committed --

[Bug 1861053] Re: no fatrace output in focal

2020-08-22 Thread Martin Pitt
FTR, I just ran fatrace a lot in a current Ubuntu 20.04 VM to debug #1885188, and it seems fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861053 Title: no fatrace output in focal To manage

[Bug 1885188] Re: fatrace autopkgtest failure due to rename test

2020-08-22 Thread Martin Pitt
anged in: fatrace (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885188 Title: fatrace autopkgtest failure due to rename test To manag

[Bug 1885188] Re: fatrace autopkgtest failure due to rename test

2020-08-22 Thread Martin Pitt
** Changed in: fatrace Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885188 Title: fatrace autopkgtest failure due to rename test To man

[Bug 1885188] Re: fatrace autopkgtest failure due to rename test

2020-08-22 Thread Martin Pitt
Thanks Christian for your initial investigations! I'm back from vacation, looking into this now. Observations: * The 0.13 tests still work fine , so this is indeed a problem with the "new" FAN_REPORT_FID mode. * I finally moved

[Bug 1890786] [NEW] ipa-client-install fails on restarting non-existing chronyd.service

2020-08-07 Thread Martin Pitt
Public bug reported: DistroRelease: Ubuntu 20.10 Package: freeipa-client 4.8.6-1ubuntu2 Client install fails: * LANG=C /usr/sbin/ipa-client-install --domain cockpit.lan --realm COCKPIT.LAN --mkhomedir --enable-dns-updates --unattended --force-join --principal admin -W --force-ntpd Option

[Bug 1799095] Re: Firewalld nftables backend breaks networking of libvirt

2020-08-07 Thread Martin Pitt
This somehow does not affect Ubuntu 20.04 LTS, but it does affect the current "groovy" release again: # virsh net-start default error: Failed to start network default error: internal error: firewalld is set to use the nftables backend, but the required firewalld 'libvirt' zone is missing. Either

[Bug 1831467] Re: test-umockdev tests flaky on armhf (and sometimes other archs)

2020-07-29 Thread Martin Pitt
https://salsa.debian.org/debian/umockdev/-/commit/87b476aee2 should hopefully help. I uploaded 0.14.2 to Debian unstable now, it should auto-sync into Groovy soon. Thanks Dan for tackling this! ** Changed in: umockdev (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received

[Bug 1875028] Re: Package cockpit-docker cannot be found

2020-04-25 Thread Martin Pitt
Right, this is intended, we stopped supporting cockpit-docker upstream: https://cockpit-project.org/blog/cockpit-215.html The older package still works for the time being, if you install it manually. ** Changed in: cockpit (Ubuntu) Status: New => Won't Fix -- You received this bug

[Bug 1802005] Re: socket is inaccessible for libvirt-dbus

2020-02-24 Thread Martin Pitt
@Christian: Wontfix WFM, I'm glad that the default works in focal (the next LTS). For the non-LTS ones it can be worked around (write a systemd unit drop-in or so), but apparently it's not such a big issue. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1802005] Re: socket is inaccessible for libvirt-dbus

2020-02-24 Thread Martin Pitt
Nice, thanks Christian! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802005 Title: socket is inaccessible for libvirt-dbus To manage notifications about this bug go to:

[Bug 1802005] Re: D-Bus socket is inaccessible

2020-02-18 Thread Martin Pitt
The socket is actually owned by libvirt ** Package changed: libvirt-dbus (Ubuntu) => libvirt (Ubuntu) ** Summary changed: - D-Bus socket is inaccessible + socket is inaccessible for libvirt-dbus -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1802005] Re: D-Bus socket is inaccessible

2019-12-29 Thread Martin Pitt
Here as well: https://www.reddit.com/r/linuxquestions/comments/c7hcfe/whack_issues_with_cockpit_and_ubuntu_server_1904/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802005 Title: D-Bus socket is

[Bug 1802005] Re: D-Bus socket is inaccessible

2019-12-29 Thread Martin Pitt
Other users run into this as well: https://github.com/cockpit- project/cockpit/issues/13339 ** Bug watch added: github.com/cockpit-project/cockpit/issues #13339 https://github.com/cockpit-project/cockpit/issues/13339 ** Changed in: libvirt-dbus (Ubuntu) Status: New => Confirmed --

[Bug 1850281] Re: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1

2019-11-07 Thread Martin Pitt
We see this in our Cockpit test image creation as well. ** Bug watch added: Red Hat Bugzilla #1721223 https://bugzilla.redhat.com/show_bug.cgi?id=1721223 ** Also affects: pcp (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1721223 Importance: Unknown Status: Unknown **

[Bug 1802005] Re: D-Bus socket is inaccessible

2019-10-28 Thread Martin Pitt
** Tags added: disco eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802005 Title: D-Bus socket is inaccessible To manage notifications about this bug go to:

[Bug 1848923] [NEW] pollinate.service fails to start: ERROR: should execute as the [pollinate] user

2019-10-20 Thread Martin Pitt
Public bug reported: In a standard Ubuntu 19.10 cloud image install, pollinate fails to start: ● pollinate.service - Pollinate to seed the pseudo random number generator    Loaded: loaded (/lib/systemd/system/pollinate.service; enabled; vendor preset: enabled)    Active: failed (Result:

[Bug 1845157] Re: runner/autopkgtest fails to setup env with binary packages moved to another packge, and different source/binary versions

2019-10-02 Thread Martin Pitt
Fix landed in autopkgtest master. Thanks Dan! ** Changed in: autopkgtest (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845157 Title:

[Bug 1826187] Re: firewalld fails to start: FATAL ERROR: No IPv4 and IPv6 firewall: looks for binaries in wrong paths

2019-09-10 Thread Martin Pitt
This magically went away on the most recent daily cloud images. @wvengen, does it work for you again as well? If so, we can close this. Thanks! ** Changed in: firewalld (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1837233] Re: [bionic] Manual IPv6 routes are not set

2019-07-19 Thread Martin Pitt
Nevermind then, this is working well enough for a stable release. ** Changed in: network-manager (Ubuntu Bionic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837233

[Bug 1837233] Re: [bionic] Manual IPv6 routes are not set

2019-07-19 Thread Martin Pitt
I confirm that using a valid IP works better: In the config: route1=fe80:2::/60,fe80::99,42 # ip -6 route show dev eth2 fe80::/64 proto kernel metric 101 pref medium fe80::/64 proto kernel metric 256 pref medium fe80:2::/60 via fe80::99 proto static metric 42 pref medium It's still missing the

[Bug 1837233] Re: [bionic] Manual IPv6 routes are not set

2019-07-19 Thread Martin Pitt
The journal says why: NetworkManager[1295]: [1563552648.1667] platform: route-sync: failure to add IPv6 route: 1:2::/60 via 1:2::3 dev 6 metric 42 mss 0 rt-src user: No route to host (113) NetworkManager[1295]: [1563552648.1672] device (eth2): failed to apply manual IPv6 configuration

[Bug 1837233] [NEW] [bionic] Manual IPv6 routes are not set

2019-07-19 Thread Martin Pitt
Public bug reported: I have a system connection like this: -- /etc/NetworkManager/system-connections/eth2 --- [connection] id=eth2 uuid=c73fb4d2-8383-4d03-a87c-04c8251961bd type=ethernet gateway-ping-timeout=12 interface-name=eth2 permissions= timestamp=1563551266 [ethernet]

[Bug 1831296] Re: __main__.SeccompTest is failing on Ubuntu CI

2019-06-25 Thread Martin Pitt
Thanks Dan! I landed your PR, so it should apply to the next upstream CI run. ** Changed in: systemd (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

2019-05-21 Thread Martin Pitt
Indeed the downstream tests fail like this as well: http://autopkgtest.ubuntu.com/packages/systemd/eoan/amd64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829829 Title: Ubuntu CI has been flaky

[Bug 1805642] Re: Package cockpit showing the debian favicon.ico

2019-05-17 Thread Martin Pitt
This version is in eoan and the bionic/cosmic/disco backports. ** Changed in: cockpit (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805642

[Bug 1826187] Re: firewalld fails to start: FATAL ERROR: No IPv4 and IPv6 firewall: looks for binaries in wrong paths

2019-04-26 Thread Martin Pitt
Doing this fixes it: ln -s /sbin/iptables /usr/sbin/ ln -s /sbin/iptables-restore /usr/sbin/ ln -s /sbin/ip6tables /usr/sbin/ ln -s /sbin/ip6tables-restore /usr/sbin/ Apparently firewalld looks for these binaries in the wrong path, doesn't use $PATH, and assumes a merged /usr system. ** Summary

[Bug 1826187] Re: firewalld fails to start: FATAL ERROR: No IPv4 and IPv6 firewall.

2019-04-24 Thread Martin Pitt
With the nftables backend, it's not just --state that's broken, it also at least affects --reload: # firewall-cmd --reload Error: 'inet firewalld filter_IN_public jump filter_IN_public_allow' # echo $? 254 -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1826187] Re: firewalld fails to start: FATAL ERROR: No IPv4 and IPv6 firewall.

2019-04-24 Thread Martin Pitt
The nftables backend actually does work reasonably well, only firewall- cmd --state seems to be broken. ** Tags added: amd64 disco regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1826187] [NEW] firewalld fails to start: FATAL ERROR: No IPv4 and IPv6 firewall.

2019-04-24 Thread Martin Pitt
Public bug reported: In a clean Ubuntu 19.04 (disco) VM installation, firewalld fails to start: * firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2019-04-24

[Bug 1805642] Re: Package cockpit showing the debian favicon.ico

2019-04-01 Thread Martin Pitt
** Changed in: cockpit (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805642 Title: Package cockpit showing the debian favicon.

[Bug 1822331] Re: autopkgtest-buildvm-ubuntu-cloud no longer works with precise or trusty

2019-03-29 Thread Martin Pitt
precise has been EOL for 2 years; trusty's support will end in about a month, so I don't think we need to bother about this now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822331 Title:

[Bug 1805642] Re: Package cockpit showing the debian favicon.ico

2019-03-14 Thread Martin Pitt
Fixed upstream in https://github.com/cockpit-project/cockpit/pull/11357 , will be in release 190. Thanks! ** Changed in: cockpit (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1819589] Re: Ubuntu CI is broken

2019-03-12 Thread Martin Pitt
That worked. ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819589 Title: Ubuntu CI is broken To manage notifications

[Bug 1819589] Re: Ubuntu CI is broken

2019-03-12 Thread Martin Pitt
Should be fixed with https://salsa.debian.org/systemd- team/systemd/commit/bd89a706b18796074d50bcf2a0cbd29de56ac542 . I'll close this once the retried PRs go green. ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Changed in: systemd (Ubuntu) Sta

[Bug 1817344] Re: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results

2019-02-24 Thread Martin Pitt
Thanks Iain! I'll keep an eye on this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817344 Title: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results To

[Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

2019-02-24 Thread Martin Pitt
This happens in about half of the xenial semaphoreci.com instances as well: $ uname -a Linux semaphore-light-1809b 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1817344] Re: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results

2019-02-24 Thread Martin Pitt
Another example: https://github.com/systemd/systemd/pull/11802 refers to the correct amd64 log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic-upstream-systemd-ci-systemd-ci/bionic/amd64/s /systemd-upstream/20190222_161608_7fe1f@/log.gz

[Bug 1817344] Re: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results

2019-02-24 Thread Martin Pitt
It seems to me that the logs are internally consistent, i. e. the mentioned UPSTREAM_PULL_REQUEST in the log does match the test results. But they get sent to the wrong PR, i. e. to the wrong statuses API. E. g.

[Bug 1787396] Re: ss crashes when using --no-header

2018-11-30 Thread Martin Pitt
I confirm this on Ubuntu 18.04 (bionic) with 4.15.0-2ubuntu1. It is fixed in 18.10 (cosmic) with 4.18.0-1ubuntu2. ** Also affects: iproute2 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: iproute2 (Ubuntu Bionic) Status: New => Confirmed ** Changed in:

[Bug 1805348] Re: Recent security update broke server-side keyboard-interactive authentication

2018-11-29 Thread Martin Pitt
Wow, thanks Marc, this was super-fast! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805348 Title: Recent security update broke server-side keyboard-interactive authentication To manage

[Bug 1805348] [NEW] Recent security update broke server-side keyboard-interactive authentication

2018-11-27 Thread Martin Pitt
Public bug reported: 0.8.4 and the backported fixes for CVE-2018-10933 cause server-side keyboard-interactive authentication to completely break. See https://bugs.libssh.org/T117 for details and a reproducer. This was fixed upstream as part of the 0.8.5 release, so disco is fine. For

[Bug 1640482] Re: Running "realm join" causes apparmor=DENIED messages

2018-11-13 Thread Martin Pitt
This seems fixed in 18.04. ** Changed in: realmd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640482 Title: Running "realm join" causes

[Bug 1799665] Re: [cosmic regression] fails to parse known_hosts, resulting in SSH_SERVER_FOUND_OTHER error for hostkey verification

2018-11-08 Thread Martin Pitt
I installed libssh-4 0.8.1-1ubuntu0.2 from cosmic-proposed, and confirm that the manual ssh connection with "cockpit-ssh" as well as all the integration tests that involve talking to remote machines through ssh now work. ** Tags removed: verification-needed verification-needed-cosmic ** Tags

[Bug 1802005] [NEW] D-Bus socket is inaccessible

2018-11-06 Thread Martin Pitt
Public bug reported: Package: libvirt-dbus Version: 1.2.0-1 DistroRelease: Ubuntu 18.10 libvirt-dbus seems to be completely broken for the system connection: root:~# busctl call org.libvirt /org/libvirt/QEMU org.libvirt.Connect ListDomains u 0 Failed to connect socket to

[Bug 1799665] Re: [cosmic regression] fails to parse known_hosts, resulting in SSH_SERVER_FOUND_OTHER error for hostkey verification

2018-10-24 Thread Martin Pitt
Added SRU information and uploaded SRU to unapproved queue. ** Description changed: Ubuntu 18.10's libssh 0.8.1 regresses parsing of known_hosts. This happens (sometimes) if there are multiple known_host key types (e. g. ssh-rsa and ssh-ed25519), then it can happen that

[Bug 1799665] [NEW] [cosmic regression] fails to parse known_hosts, resulting in SSH_SERVER_FOUND_OTHER error for hostkey verification

2018-10-24 Thread Martin Pitt
e for an SRU, especially as the impact is quite high. [1] http://api.libssh.org/master/group__libssh__session.html#gac%20bc5d04fe66beee863a0c61a93fdf765 [2] https://github.com/cockpit-project/cockpit/pull/10357 [3] https://fedorapeople.org/groups/cockpit/logs/pull-10357-20181022-204242-8672df31-verify-ub

[Bug 1799665] Re: [cosmic regression] fails to parse known_hosts, resulting in SSH_SERVER_FOUND_OTHER error for hostkey verification

2018-10-24 Thread Martin Pitt
t included: https://git.libssh.org/projects/libssh.git/commit/?id=35a64554899f142a2b8b68c79007ad9c3ce00cb1 https://git.libssh.org/projects/libssh.git/commit/?id=c1a8c41c5daf79e37aa5fde67dd94c8596e81102 https://git.libssh.org/projects/libssh.git/commit/?id=893b69d82b4435973ec4d15aae

[Bug 1796407] Re: pg_wrapper doesn't work when -p is used

2018-10-18 Thread Martin Pitt
@Robie: It's been a while since I dabbled with this, but to me this is not really "wishlist", it's an actual bug. Surely pg_wrapper doesn't document that it looks at the explicitly specified port, but it certainly ought to. This case was just plain forgotten. So the patch certainly needs some

[Bug 1788040] Re: Replace LXD deb by snap in Ubuntu 18.10

2018-08-22 Thread Martin Pitt
Ah, it used to be useful for running the containers on a remote servers. I. e. what we used to do for armhf testing, they were running on remote arm64 OpenStack instances. I adjusted the Suggests: https://salsa.debian.org/ci- team/autopkgtest/commit/4d4a7d9b16f Thanks! ** Changed in:

[Bug 1788040] Re: Replace LXD deb by snap in Ubuntu 18.10

2018-08-22 Thread Martin Pitt
autopkgtest *only* uses the `lxc` CLI and documents the `lxd` setup CLI from $PATH. The package has a "Suggests: lxd-client". You mention that the "lxd" deb will remain around, does that apply to "lxd-client" as well? ** Changed in: autopkgtest (Ubuntu) Status: New => Incomplete -- You

[Bug 1778641] [NEW] nsupdate crashes in dns_name_clone()

2018-06-26 Thread Martin Pitt
Public bug reported: During our Cockpit integration tests on Ubuntu 16.04, nsupdate crashes awfully often when joining a FreeIPA domain, like this: Jun 25 13:17:26 x0.cockpit.lan systemd-coredump[8503]: Process 8498 (nsupdate) of user 0 dumped core.

[Bug 1774000] Re: Fails to boot cirros QEMU image with tuned running

2018-05-29 Thread Martin Pitt
I tested this on Fedora 28, which also has tuned 2.9.0, but a slightly newer QEMU (2.11.1, as opposed to 2.11 on Ubuntu 18.04), and a newer kernel (4.16.10 instead of 4.15.0 in Ubuntu 18.04). The invocation in the unit (/usr/bin/python -Es /usr/sbin/tuned -l -P) is exactly the same, so is the

[Bug 1774000] Re: Fails to boot cirros QEMU image with tuned running

2018-05-29 Thread Martin Pitt
Found it. This happens as soon as you install tuned, which auto-starts tuned.service. After "systemctl stop tuned", QEMU works again. Retitled accordingly, so this is not a regression. ** Summary changed: - Regression: Fails to boot cirros image + Fails to boot cirros QEMU image with tuned

[Bug 1774000] [NEW] Regression: Fails to boot cirros image

2018-05-29 Thread Martin Pitt
Public bug reported: A recent security update broke booting of some images, particularly CirrOS [3]: $ wget https://download.cirros-cloud.net/0.3.5/cirros-0.3.5-i386-disk.img $ qemu-system-x86_64 -enable-kvm -nographic cirros-0.3.5-i386-disk.img -snapshot qemu-system-x86_64: warning: host

[Bug 1696471] Re: AppArmor denies access to /etc/gss/mech.d/

2018-03-02 Thread Martin Pitt
Sorry for the delay, I finally found some time to get back to this. This is still reproducible on current Ubuntu 17.10: virsh define m.xml qemu-img create -f qcow2 /var/lib/libvirt/images/subVmTest1-2.img 128M virsh start subVmTest1 dmesg shows: [ 319.220193] audit: type=1400

[Bug 1696471] Re: AppArmor denies access to /etc/gss/mech.d/

2018-03-02 Thread Martin Pitt
Forgot to mention: I didn't change any libvirt config files, in particular not the ones you mentioned: # dpkg -s libvirt-daemon-system | grep libvirt.conf /etc/sasl2/libvirt.conf 09c4fa846e8e27bfa3ab3325900d63ea # md5sum /etc/sasl2/libvirt.conf 09c4fa846e8e27bfa3ab3325900d63ea

[Bug 1749736] Re: autopkgtest-build-lxd fails to build artful/bionic containers

2018-02-25 Thread Martin Pitt
Updated patch: https://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=563eac74595cd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749736 Title: autopkgtest-build-lxd fails to build

[Bug 1749736] Re: autopkgtest-build-lxd fails to build artful/bionic containers

2018-02-20 Thread Martin Pitt
** Changed in: autopkgtest (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749736 Title: autopkgtest-build-lxd fails to build artful/bionic containers To

[Bug 1749736] Re: autopkgtest-build-lxd fails to build artful/bionic containers

2018-02-20 Thread Martin Pitt
signed) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749736 Title: autopkgtest-build-lxd fails to build artful/bionic containers To manage notifications about this bug go

[Bug 1750654] [NEW] "lxc-create -B best" fails on non-btrfs/zfs system

2018-02-20 Thread Martin Pitt
Public bug reported: As per documentation, the `-B best` option should automatically select the best backingstore, falling back all the way to dir. But apparently it doesn't, at least not in artful's 2.1.0-0ubuntu1: $ sudo lxc-create -B best --name=autopkgtest-xenial -t ubuntu -- -r xenial

[Bug 1707898] Re: systemd translations are not synced with upstream

2018-02-19 Thread Martin Pitt
Thanks Gunnar, nice work! I cherry-picked the patches in https://salsa.debian.org/systemd-team/systemd/commit/87f54958bc24 . The debian/ changes were already in Debian master. ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification

[Bug 1749736] Re: autopkgtest-build-lxd fails to build artful/bionic containers

2018-02-15 Thread Martin Pitt
I propose to add a check for the default network route to the "is the container up?" polling loop: https://lists.ubuntu.com/archives/ubuntu-devel/2018-February/040158.html ** Changed in: autopkgtest (Ubuntu) Status: New => Triaged ** Changed in: autopkgtest (Ubuntu) Importance:

[Bug 1707898] Re: systemd translations are not synced with upstream

2018-02-15 Thread Martin Pitt
I confirmed that the current "ninja -C build-deb/ systemd-pot" command also builds a complete .pot file with policykit-1 installed (unsurprisingly, as this also just calls gettext). So that part is fine. What is really bad however, is to build-depend against policykit-1: The following NEW

[Bug 1707898] Re: systemd translations are not synced with upstream

2018-02-15 Thread Martin Pitt
Thanks Gunnar for tracking this down! Adding a policykit-1 build dependency requires some thought, as that also build-depends on systemd [1], thus this is circular. Also, there was a lot of effort with making systemd bootstrappable without excessive dependencies. But I think it's fine to add this

[Bug 1707898] Re: systemd translations are not synced with upstream

2018-02-14 Thread Martin Pitt
@Gunnar: This patch does not actually work: ❱❱❱ xgettext -f "po/POTFILES.in" -o "build-deb/po/systemd.pot" --join-existing xgettext: warning: file 'src/core/org.freedesktop.systemd1.policy.in.in' extension 'policy' is unknown; will try C xgettext: warning: file

[Bug 1707898] Re: systemd translations are not synced with upstream

2018-02-12 Thread Martin Pitt
I committed the first hunk to Debian, this makes sense: https://salsa.debian.org/systemd-team/systemd/commit/18d8c2df133b8af The second is too hackish for a permanent downstream delta, IMHO: This should rather be fixed upstream, as upstream polkit (as well as Debian's and Ubuntu's older versions)

[Bug 1741227] Re: apparmor denial to several paths to binaries

2018-01-04 Thread Martin Pitt
The most plausible explanation for enumerating /usr/local/bin/ is that ntpd has some hooks.d/ mechanism which gets called after syncing the time, and that runs a shell in between. So IMHO this should be allowed. -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

2018-01-04 Thread Martin Pitt
The most plausible explanation for enumerating /usr/local/bin/ is that ntpd has some hooks.d/ mechanism which gets called after syncing the time, and that runs a shell in between. So IMHO this should be allowed. -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

2018-01-03 Thread Martin Pitt
I locally ran Cockpit tests on our current Ubuntu 17.10 image and re- confirm that I got the "disconnected path" error. I then upgraded the ntp package to artful-proposed, and *that* violation is now gone. As others already saw, I now get a test failure on apparmor="DENIED" operation="open"

[Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path

2017-12-15 Thread Martin Pitt
Thanks Christian! Indeed this is rather hard to reproduce locally, but that PR seems to address this. I'll let you know if it doesn't after it lands. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1680384] Re: libvirt-qemu apparmor profiles misses several important entries

2017-12-06 Thread Martin Pitt
Christian: This bug now hit debian-testing (see http://209.132.184.41/logs/pull-8219-20171206-214646-d2e9e141-verify- debian-testing/log.html#2). Is there an upstream bug/patch mail for reference, or are these Debian/Ubuntu downstream rules? ** Bug watch added: Debian Bug tracker #878203

[Bug 1153671] Re: Port to python3-launchpadlib

2017-11-30 Thread Martin Pitt
Once you do this, these fallbacks should be cleaned up: http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/apport/crashdb_impl/launchpad.py#L30 http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/apport/crashdb_impl/launchpad.py#L137 -- You received this bug

[Bug 1725348] Re: Systemd - Bypassing MemoryDenyWriteExecution policy

2017-11-14 Thread Martin Pitt
Patches backported into Debian packaging git: https://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?id=9bba5469f2b95ea9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725348 Title:

[Bug 1696471] Re: AppArmor denies access to /etc/gss/mech.d/

2017-11-05 Thread Martin Pitt
This still happens all the time, also in 17.10, reopening. I need to find some time to create a reproducer that doesn't involve the Cockpit tests. ** Changed in: libvirt (Ubuntu) Status: Expired => Incomplete ** Changed in: libvirt (Ubuntu Xenial) Status: Expired => Confirmed --

[Bug 1729626] Re: AppArmor denies access to /sys/block/*/queue/max_segments

2017-11-03 Thread Martin Pitt
Nice work, thanks Christian! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729626 Title: AppArmor denies access to /sys/block/*/queue/max_segments To manage notifications about this bug go to:

[Bug 1729626] [NEW] AppArmor denies access to /sys/block/*/queue/max_segments

2017-11-02 Thread Martin Pitt
Public bug reported: Since Cockpit's "ubuntu stable" VM image got updated from Ubuntu 17.04 to 17.10, the libvirt tests now cause several instances of this AppArmor denial: Nov 02 10:19:28 unassigned-hostname audit[1347]: AVC apparmor="DENIED" operation="open"

[Bug 1726804] Re: rules for images on attach-device not containing lock permission

2017-10-26 Thread Martin Pitt
This also gets detected by the cockpit integration tests in https://github.com/cockpit-project/cockpit/pull/7939, so I spent an hour to create a minimal reproducer (attached), only to find that this is already fixed in -proposed. I confirm that with the -proposed package this works again. Thanks!

[Bug 1727202] [NEW] [17.10 regression] AppArmor denial: Failed name lookup - disconnected path

2017-10-25 Thread Martin Pitt
Public bug reported: Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd"

[Bug 1717771] Re: confusing btrfs storage pool creation

2017-09-25 Thread Martin Pitt
Indeed, sorry about that - I've become so used to backports having the latest version, I was testing with 2.17. I now upgraded to artful, and 2.18 now does the right thing: ❱❱❱ sudo lxd init Do you want to configure a new storage pool (yes/no) [default=yes]? Name of the new storage pool

[Bug 1659541] Re: name resolution fails in vmdebootstrap with setup-testbed customize script

2017-09-24 Thread Martin Pitt
https://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=085b1798fa ** Changed in: autopkgtest (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1339106] Re: Provide ssh setup script for ubuntu-emulator

2017-09-24 Thread Martin Pitt
With the demise of the Ubuntu phone (rest in peace, *tear*) this is obsolete now. ** Changed in: autopkgtest (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1646544] Re: "changelog format debian is unknown" with read-only testbeds on < xenial

2017-09-24 Thread Martin Pitt
This was fixed in xenial, and there's no point in trying to fix this in earlier releases any more. ** Changed in: autopkgtest (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1574706] Re: Disabling the welcome wizard doesn’t dismiss it

2017-09-24 Thread Martin Pitt
With the demise of the Ubuntu phone (rest in peace, *tear*) this is obsolete now. ** Changed in: autopkgtest (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1383459] Re: Bring back adb factory reset

2017-09-24 Thread Martin Pitt
With the demise of the Ubuntu phone (rest in peace, *tear*) this is obsolete now. ** Changed in: autopkgtest (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1659541] Re: name resolution fails in vmdebootstrap with setup-testbed customize script

2017-09-24 Thread Martin Pitt
** Bug watch added: Debian Bug tracker #845925 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845925 ** Also affects: autopkgtest (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845925 Importance: Unknown Status: Unknown -- You received this bug notification

[Bug 1673370] Re: autopkgtest-buildvm-ubuntu-cloud fails to find a zesty image on xenial hosts

2017-09-24 Thread Martin Pitt
This is fixed in current autopkgtest versions, including the one in xenial-backports. You can't use the xenial proper version to run tests for later releases, the cloud images, lxc/lxd etc. change too quickly for that. ** Changed in: autopkgtest (Ubuntu) Status: New => Fix Released --

[Bug 1384706] Re: qemu: tar: Unexpected EOF in archive in copyup()

2017-09-24 Thread Martin Pitt
** Changed in: autopkgtest (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384706 Title: qemu: tar: Unexpected EOF in archive in copyup() To manage

[Bug 1384706] Re: qemu: tar: Unexpected EOF in archive in copyup()

2017-09-24 Thread Martin Pitt
** Summary changed: - tar: Unexpected EOF in archive in copyup() + qemu: tar: Unexpected EOF in archive in copyup() ** Bug watch added: Debian Bug tracker #829753 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829753 ** Also affects: autopkgtest (Debian) via

[Bug 1717771] Re: confusing btrfs storage pool creation

2017-09-24 Thread Martin Pitt
Thanks! That already makes a lot more sense, although it's still quite a bit more complicated than necessary, and for sure a lot more complicated than earlier versions that "just worked": ❱❱❱ sudo lxd init Do you want to configure a new storage pool (yes/no) [default=yes]? → ok, I suppose yes

[Bug 1717771] Re: confusing btrfs storage pool creation

2017-09-18 Thread Martin Pitt
Thanks for that, Stéphane! Indeed saying "no" at question 4 wasn't obvious. Question 5 makes sense, I just didn't get that far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717771 Title:

[Bug 1717771] [NEW] confusing btrfs storage pool creation

2017-09-17 Thread Martin Pitt
Public bug reported: In the past, lxd "just worked" on btrfs, as it would automatically put containers/images into subvolumes for snapshotting. Now it's apparently necessary to explicitly create a "storage pool" for it. I wouldn't see why one would ever want to use a plain "dir" or even a zfs

[Bug 1717771] Re: confusing btrfs storage pool creation

2017-09-17 Thread Martin Pitt
Also, while I know that /dev/sda is my hard disk, so I typed that in, it's not very friendly to expect that every user will be able to do that. The script could detect available block devices and give you a choice? -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1693154] Re: ipa-client-install fails: kinit: Included profile directory could not be read while initializing Kerberos 5 library

2017-09-14 Thread Martin Pitt
Using the reproduction steps in the description, I re-confirmed that with the current zesty version joining the domain fails because of that missing directory. After installing freeipa-{client,common} from -proposed, joining the domain now succeeds. ** Tags removed: verification-needed-zesty **

[Bug 1716034] Re: Network manager stops managing Ethernet links after upgrade

2017-09-11 Thread Martin Pitt
FTR, I don't want to blame the NetworkManager 1.2.6 SRU to xenial - that new upstream version now evades the version test in the postinst, but of course it's still that version test which is at fault. I don't see how we can use a simple version test to determine the situation that we want

[Bug 1716034] Re: Network manager stops managing Ethernet links after upgrade

2017-09-11 Thread Martin Pitt
I'm sorry, I mean bug 1676547. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716034 Title: Network manager stops managing Ethernet links after upgrade To manage notifications about this bug go

[Bug 1716034] Re: Network manager stops managing Ethernet links after upgrade

2017-09-11 Thread Martin Pitt
Is that any better with the fix in bug 1690992? That sounds very much like a duplicate? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716034 Title: Network manager stops managing Ethernet links

  1   2   3   4   5   6   7   8   9   10   >