\o/ everything migrated fine in Cosmic now.
Time is ready for an SRU now into Bionic.
** Also affects: netcat-openbsd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: netcat-openbsd (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification
** Merge proposal unlinked:
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/345498
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
nss and corosync being the last on this are in Cosmic now.
** Changed in: corosync (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
I backported the changes which had a lot of extra noise that had to be dropped.
Now a build is ready in ppa [1]
I haven't actually read the patch too much yet but found the build to not solve
the issues for me on the example from the man page - so I started taking a
deeper look.
It really works
Found a much better backport much more suited for the SRU process.
New build in ppa, if it tests fine I'll propose that instead.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu.
** Merge proposal unlinked:
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/345498
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
** Description changed:
[Impact]
Concurrent SASL authentications could trigger a segfault. This was observed
by the bug reporter during replication from a master to a slave, and can be
reproduced with a test program.
The fix is applied upstream, see comment #13.
[Test Case]
*
*** This bug is a duplicate of bug 1767283 ***
https://bugs.launchpad.net/bugs/1767283
Hi,
you are right and this is a dup of bug 1767283 which I already fixed in Cosmic
and have a backport for Bionic ongoing right now.
Closing this as Dup.
** This bug has been marked a duplicate of bug
I set up a Xenial on arm64.
I created a working guest like:
b1
1f776433-dc84-43ac-9e60-b8e571ae22ff
https://launchpad.net/uvtool/libvirt/1;>ssh-rsa
We have a few changes, but none of these is "the" issue.
- Cpu features
- cpu model
- emulator without redirect
But I found that your nvram line is wrong:
/usr/share/AAVMF/AAVMF_VARS.fd
With that you want it to change the systems default template, you should
instead use
I'm wondering if taking it out of ubuntu-server but adding it to cloud-
image seed would fix it for most people without breaking major use
cases.
The mentioned mail is sent to ensure I'm not missing other use-cases.
--
You received this bug notification because you are a member of Ubuntu
Touch
This is currently spread across different seeds, we have:
ubuntu./server
* open-iscsi
# This is Needed by MAAS images to deploy via iscsi
ubuntu./server-ship
* open-iscsi
* open-iscsi-udeb
# This is for the installer on/through iscsi (server images)
ubuntu./ship
* open-iscsi
*
Thanks Stefan, updating the tags per former comment.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Changes reviewed and SRU Template ready, uploaded for the SRU Team to
accept it into Bionic.
** Description changed:
+ [Impact]
+
+ * This worked in former relases, so from a LTS->LTS upgraders POV it is
+an upgrade regression
+ * The impact is that local source (-s) can no more be used
Hi Newell - Hmm, interesting.
We have
owner @{PROC}/*/auxv r,
for qemu, but never had/needed so for
/etc/apparmor.d/usr.lib.libvirt.virt-aa-helper which your denies are against.
For "myself" IN only resolved arm VMs in Bionic and forward (since I made
uvtool fully work for me on arm), but
I thought I might have oversimplified PCIe setup for q35 too much when I
tried to compare to i440fx (where this works AFAICS).
But adding libvirts default devices for this case did not change anything.
For documentation purposes still here the difference how to add those as
attachment.
The
Since we ruled out netplan, mark it invalid.
Focus on systemd-networkd for now.
** Changed in: netplan.io (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I identified that systems I spawn as q35 right away work.
Only those where the initial cloud init runs as i440fx and then I change them
to q35 are affected.
I compared configurations and eventually had even my converted instance
running, to the point that it was hard to tell why.
I found that
** Also affects: spice (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1719038
Title:
X Server crashes during log in VM
Public bug reported:
Debian has picked many of our Apparmor changes whcih simplifies Delta.
Also the newer Upstream version is good to have.
I have marked a few bugs to retest with this new build, but need the
merge build first.
** Affects: ntp (Ubuntu)
Importance: Undecided
Nothing to do on NTP here, linked up the relayed Debian bug on openntpd
- thanks Simon!
** Also affects: openntpd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882556
Importance: Unknown
Status: Unknown
** Changed in: ntp (Ubuntu)
Status: Confirmed => Won't
We handled chrony and ntp was demoted, so set ntp to Won't Fix in regard
to this bug.
** Changed in: ntp (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
*** This bug is a duplicate of bug 1727202 ***
https://bugs.launchpad.net/bugs/1727202
Fixed in >=Bionic by 1727202, since it is not a fatal error and a config
file change can silence it I do not plan on an SRU.
** This bug has been marked a duplicate of bug 1727202
[17.10 regression]
*** This bug is a duplicate of bug 1741227 ***
https://bugs.launchpad.net/bugs/1741227
Fixed in bug 1741227
** This bug has been marked a duplicate of bug 1741227
apparmor denial to several paths to binaries
--
You received this bug notification because you are a member of Ubuntu
Touch
FYI - accepted by Debian in debian/1%4.2.8p11+dfsg-1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1741227
Title:
apparmor denial to several paths to binaries
Status in ntp
Since there are no intentions to SRU the fixes for chrony or touch ntp
/open-ntp on this lets mark the tasks accordingly to manage
expectations.
** Changed in: openntpd (Ubuntu)
Status: New => Won't Fix
** Changed in: ntp (Ubuntu)
Status: New => Won't Fix
** Changed in: chrony
Per former comment expected to be good and since we demoted NTP(d)
setting to Won't Fix for NTP task.
** Changed in: ntp (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in
Drops due to my contribs being accepted in Debian:
pick 1dc3bef2 DROP: d/ntp-systemd-wrapper protect service startup from
ntpdate (LP: #1706818)
pick 3018fe81 DROP: add attach_disconnected to let ntp report log messages
(LP: #1727202)
pick 316d86fa DROP: * debian/apparmor-profile: avoid
On those live CDs there should be no NTP daemon running anyway.
And even if so we switched which defaults to non-utc for the following reason:
rtconutc
chronyd assumes by default that the RTC keeps local time (including
any daylight saving changes). This is convenient on PCs
Hi,
the root cause lies in this of your log:
insserv: Starting smfpd depends on grub-common and therefore on system
smfpd is not part of the archive, you might check /etc/init.d/smfpd where it is
from and what is in its headers.
This breaks the update/upgrade of other packages by causing
And I beg your pardon to come by so late, I was looking at ntp bugs in
general today and found this. If I'd have known I could have explained
earlier :-/
** Changed in: ntp (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
Seed changes accepted and merged in VCS.
Related ubuntu-meta update uploaded as
https://launchpad.net/ubuntu/+source/ubuntu-meta/1.421
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
Prepared ppa at https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3273
I checked a few more bugs I wanted to check with the new version and updated
the bugs.
Also I cleared quite a bunch of ntp bugs this morning by retriaging them before
the merge.
--
You received this bug
** Merge proposal unlinked:
https://code.launchpad.net/~paelzer/ubuntu/+source/ntp/+git/ntp/+merge/347033
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1717983
Title:
Upgrade/Install from the ppa seemed good.
Tests from the ppa show no new regressions good (including the qa regression
tests).
Opening up the MP for this merge at:
https://code.launchpad.net/~paelzer/ubuntu/+source/ntp/+git/ntp/+merge/347033
** Merge proposal linked:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I appreciate the quality of this bug report and I'm sure
it'll be helpful to others experiencing the same issue.
This sounds like an upstream bug to me. The best route to getting it
fixed in Ubuntu in this case
I checked with latest upstream and this is still true.
** Changed in: ntp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1773007
The snippet I initially found is for a "trigger" which is independent
(other things need to reatsrt ntp. Sorry for the noise.
I found that the new postinst leaves ntp around but reloads the profile (ok
with the process running)
Eventually (after the reload) there is a invoke-rc.d ntp start ||
** Changed in: ntp (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1773921
Title:
merge ntp 1:4.2.8p11+dfsg-1 for cosmic
Status in
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Hi,
from your logs
update-alternatives: error: cannot stat file '/usr/bin/nodejs': Too many
levels of symbolic links
This is nothing that netcat-openbsd would touch in particular. If anything it
might be part of the generic debian maintainer script snippets.
I tried the same upgrade last week
Public bug reported:
Hi,
I miss some hidden trigger of "netplan apply" to understand the following case.
I have kvm guests, you can spawn your own one to reproduce via:
$ uvt-simplestreams-libvirt --verbose sync --source
http://cloud-images.ubuntu.com/daily arch=amd64 release=bionic
Since it might be networkd as well I added a bug task for it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1775566
Title:
networkd not applying config written by
Even "netplan apply" with NO yaml file fixes it.
So running in the static networkd config (with the files I copied formerly
created by netplan as outlied above).
Then with debug enabled it does:
$ networkctl list
IDX LINK TYPE OPERATIONAL SETUP
1 lo
Other than the mistake to not update to my name on the upload this is
resolved.
>From now on you can remove it:
# apt remvoe open-iscsi
E: Invalid operation remvoe
root@c:~# apt remove open-iscsi
Reading package lists... Done
Building dependency tree
Reading state information... Done
The
@Scott, I agree and I'm already on a much better fix by bug 1755858
After this there is not much reason left to remove it anywhere (there is but
not as much as now).
On top - going forward we can make is a recommends instead of a Depends
which help those that want to remove it later.
TL;DR:
-
So for this bug we need:
1. make it a recommends
2. ubuntu-meta update for cosmic
For #1 I opened [1] and #2 can only follow after that is merged.
And this can be done independent to bug 1755858 - so no matter if we
succeed/fail there one can at least later remove open-iscsid if he wants
without
Setting incomplete missing further info, also there were no similar bug
reports since then.
** Changed in: irqbalance (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1641272
Title:
Debug symbols package doesnt exist
Status in dnsmasq package in Ubuntu:
Hi,
first of all I beg your pardon - while I'm just the one cleaning old bugs - it
is bad that you had to wait so long.
Now lets get to your case...
This is a mix of systemd and ifup based network ocnfiguration, and in
Artful a lot of this was still in flight.
In Bionic there is a simplified
** Changed in: debconf (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1748063
Title:
package clamav-base
16.04.4 iso
/media/iso/pool/main/n/numactl/libnuma1_2.0.11-1ubuntu1.1_amd64.deb
/media/iso/pool/main/n/numactl/numactl_2.0.11-1ubuntu1.1_amd64.deb
I guess with that you are good now.
** Changed in: ubuntu-meta (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-meta
This is resolved I'd think.
@Dannf did you check older ISOs like the last 16.04 respin in regard to your
case?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1700826
Can be avoided not using -z
AFAIK it is an issue with compression on very huge files.
Theree are similar discussions on e.g.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741628
** Bug watch added: Debian Bug tracker #741628
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741628
**
Will be in 7.7p2 per (next stable release)
https://github.com/openssh/openssh-portable/commit/484fc023af92ee30bc99eb9798235a00e8f929cc
Upstream Bug:
https://bugzilla.mindrot.org/show_bug.cgi?id=2851
Seems to be broken in 7.7 only so no need to SRU.
** Bug watch added: OpenSSH Portable
That would imply it was resolved in slang2 (libslang2) 2.3.0-4 which is
in everything later than Xenial.
The change to consider for backporting would be
https://git.launchpad.net/ubuntu/+source/slang2/tree/debian/patches
/init-crash.patch?id=e633289c99ede705274a1b337a0deff5f8e08779
We should try
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
>From your log files:
/etc/ssh/sshd_config: line 91: Bad configuration option: Host
/etc/ssh/sshd_config: line 92: Bad configuration option: ForwardX11
/etc/ssh/sshd_config: terminating, 2 bad configuration options
SourcePackage: openssh
That has to be resolved for the install/upgrade of the
Hi,
from your log:
aug 23 09:45:31 hostname sshd[1051]: error: Bind to port 22 on 192.168.2.4
failed: Cannot assign requested address.
aug 23 09:45:31 hostname sshd[1051]: fatal: Cannot bind any address.
aug 23 09:45:31 hostname systemd[1]: Failed to start OpenBSD Secure Shell
server.
It seems
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
Fixed by Colin in 1:6.7p1-5+deb8u4 1:7.4p1-10+deb9u2 1:7.5p1-6 by hat
only Xenial still is affected.
But by now Xenial configs should work already since thre is already the
next LTS released.
** Also affects: openssh (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
This is essentially a config change breaking the service (re)start. and due to
that upgrades.
While the init could be more resilient it is not really a bug but a
misconfiguration as identified by Ryan already.
Also the error message (these days) is not misleading at all (tried on cosmic):
Hi,
I'm clearing old dormant bugs atm.
Here are no good next step to take action.
Also the referred upstream discussion seems to have fallen to slumber.
Did you have luck trying newer versions of this or any other update that
helps to get this bug moving again?
Also we are waiting for answers
Xenial seems affected
# valgrind --leak-check=full ./main
==1859== Memcheck, a memory error detector
==1859== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==1859== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==1859== Command: ./main
==1859==
start test
Artful
# valgrind --leak-check=full ./main
==1839== Memcheck, a memory error detector
==1839== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==1839== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==1839== Command: ./main
==1839==
start test
error: can't
X: 3.2.27-1ubuntu0.16.04.1
A: 3.2.29-0ubuntu3
https://github.com/thom311/libnl looks more up to date than the repo
suggested before.
Checking the log in between it is not ovbious what it is, also the leak
seemed to have changed between trusty and xenial (maybe old fixed and
new added).
--
You
Needs debugging what the actual change is that could be considered for
backporting.
** Changed in: libnl3 (Ubuntu Trusty)
Status: Triaged => Confirmed
** Changed in: libnl3 (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of
For the usual SRU policy [1] it is unlikely and would require a lot of
exceptions and checks to take the full 3.1.2.
You'd really have to show that it is not working at all.
Otherwise usually only individual fixes are backported.
The other issue you mentioned is already tracked on it's own so I
I confirm that every second
$ systemctl restart dnsmasq
hangs
Also I confirm that removing squid resolved the situation.
I found that it does this:
1. /bin/sh /etc/init.d/dnsmasq systemd-stop-resolvconf
2. /bin/sh /etc/init.d/dnsmasq systemd-start-resolvconf
Both will call hooks like:
0
Per former comments marking as fixed and adding Xenial task.
It is still an issue in Xenial, but since no one here was participating I
wonder about the severity.
Also we would certainly not backport the fix that was taken.
I filtered it a bit and it looks like
The other bug had mentioned being resolved in latter versions.
Can you cross-try the same on e.g. 18.04 to be sure on the scope of this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
Sounds related / similar to bug 1761096
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1778073
Title:
dnsmasq and resolvconf hangs on start
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1771011
Title:
Doesn't accept environment variable with underscore in its name in
SSH to finally learn how to pick up addresses later is a long time demand for
ssh to do that.
But it is a demand for an upstream feature IMHO.
I know it can thse day's re-pickup adresses that it lost:
- I have a KVM guest with one interface and I have set up ssh listen to only
interface
So what do we know:
- Working in KDE + Breeze theme
- Broken in Gnome + Ambiance theme
I tried Gnome + Adwaita theme and it works fine then.
For the Desktop team steps to reproduce:
1. qemu-img create -f qcow2 /var/lib/libvirt/images/test.img 10M
2. apt install virt-manager libvirt-daemon-system
one test needed trigger with new openmpi, done now
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1771011
Title:
Doesn't accept environment variable with underscore in
This one is fine, if you look at the top I added a task for it.
This is a thing Launchpad does really well - avoid the proliferation and
confusion of bugs affecting or being discussed in multiple packages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
For the strongswan change I filed a bug with Debian, I don't see an immediate
need to add Delta for this.
@xnox: If there are serious deadlines involved you can obviously push the
change, otherwise I'd wait for the next merge.
** Bug watch added: Debian Bug tracker #905082
Released with 1:7.7p1-3 since a while - handing in cosmic-proposed.
None of the issues seem related to me, for now I retriggered the tests to run
with the new versions and hopefully resolve by itself.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
** Tags added: libvirt-18.10
--
You received this bug notification because you are a member of Ubuntu
Tou
Upstream version 2.79 has this in the changelog:
+ Tidy up Crypto code, removing workarounds for ancient
+ versions of libnettle. We now require libnettle 3.
Not sure this is backportable to Trusty's nettle on 2.7.1-1ubuntu0.2
without taking back the upstream changes.
To get you
Since it "only" affects backports to very old releases as we have
Xenial: 3.2-1ubuntu0.16.04.1
Debian-Stable: 3.3-1
I'll mark importance low for now.
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This bug is present in Debian too, and Ubuntu currently doesn't make any
changes over the Debian package. So this bug would be best fixed
directly in Debian, and then Ubuntu will pick up the fix automatically.
*** This bug is a duplicate of bug 1758841 ***
https://bugs.launchpad.net/bugs/1758841
I knew I had talked about it before, but couldn't find the bug last week
- thanks Daniel for having a better bug navigation system!
--
You received this bug notification because you are a member of Ubuntu
** Tags added: triage
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1758841
Title:
virt-manager: Light grey menu items on light grey background are
barely
FYI - the libvirt change is in git, just needs a few other things and
tests to be complete for an upload.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1784023
Title:
I agree strongswan/openconnect (and maybe more) are affected by the
symptom, while the bug lies in bind9-host/avahi packages at least
according to current debugging.
>From my experience I guess what would be great to get more traction on this is
>to get a shorter reproducer than setting up some
FYI bug 1786261 could be another symptoms of this, reporters there will
take a look and might add another affected package to this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
Hi,
I just realized with you tracking it down so far - could it be "another
symptom" of bug 1752411 ?
If so we should add strongswan there as affected and make this bug a
Dup, so that ALL effects of this one issue are in one place.
I'd be glad if one of you could make the detail check if you
Hi fermulator,
I was wondering vice versa if 5 seconds would be too short actually.
Yes the good cases will return in sub-second, but it is the bad cases we want
to fix here.
Having a bit more time to recover if it can doesn't seem too bad to me.
On the question of host -W for waiting.
While it
Thanks Trent for the extra verification.
Tests also look good so far, but currently since a lot got uploaded due to
feature freeze some tests take a while.
We should have that in cosmic soon and then can pick the same for Bionic.
Thanks also for your thoughts on a better long term solution.
--
** Changed in: avahi (Ubuntu Cosmic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1752411
Title:
bind9-host,
Clearing old bug, this is fixed since:
141 isc-dhcp (4.3.3-5ubuntu6) xenial; urgency=medium
142
143 * isc-dhcp-server: Suggest policycoreutils instead of recommending it.
Fixed since 1.15-1, which is quite a while ago.
Clearing this old bug by updating the status.
** Changed in: krb5 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in
I've had some minor cleanups on the changelog, but other than that I
think the most recent submission is good.
Also I found no issues in testing.
The code path it takes when the timeout triggers is that of a failing host
command (bad RC) which I think is just right. It will set things in a way
I was pushing this through autopkgtesting on LP-Infra where we see issues with
that sometimes.
Unfortunately when you need an issue it does not show up, I only have 4 good
cases:
bind9-host is deprecated anyway isn't it?
Could the avahi shell script easily be modified to try dig at the same place?
Also as requested since you isolated it towards resolveconf I'm adding a
bug task for that as well.
** Also affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
While it might seem unimportant "only" hitting some open-iscsi tests we
can't be sure how many cases and how many people are hit by this every
now and then.
So I think this really is more important than it might seem at first.
--
You received this bug notification because you are a member of
1 - 100 of 1233 matches
Mail list logo
