Fixed in 20210222 daily images. Marking fix released.
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Greater output of journalctl:
https://pastebin.canonical.com/p/XJzPMHrSbx/
** Description changed:
Summary
===
On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud
instance to loose network access.
Expected Result
===
Working network access
Actual
$ sudo journalctl --no-pager -u systemd-networkd-wait-online.service
-- Journal begins at Mon 2021-01-11 21:30:31 UTC, ends at Mon 2021-01-11
22:01:17 UTC. --
Jan 11 21:30:35 ubuntu systemd[1]: Starting Wait for Network to be Configured...
Jan 11 21:30:37 ubuntu systemd-networkd-wait-online[416]:
Public bug reported:
Summary
===
On Hirsute, upgrading or using to systemd 247.1-4ubuntu1 causes Google Cloud
instance to loose network access.
Expected Result
===
Working network access
Actual Result
===
After upgrade, network access is lost and serial console is filled with
messages about
** Changed in: cloud-images
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1880853
Title:
libc6-lse lets update-initramfs fail
# journalctl -u systemd-networkd
https://paste.ubuntu.com/p/9M3xwgwgMj/
# systemctl status systemd-networkd.service
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled;
vendor preset: enabled)
Active: failed (Result:
** Attachment added: "journal short-precise"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891716/+attachment/5401580/+files/journal.short
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Attachment added: "journal from lxd"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891716/+attachment/5401579/+files/journal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Here are my notes from using a Groovy LXD container:
Expected Results
---
$ resolvectl status | grep "DNS Server"
Current DNS Server: 192.168.100.1
DNS Servers: 192.168.100.1
Actual Results
---
$ resolvectl status
Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS
@smoser
a looks merged
b has not had any changes since 2018 and looks up-to-date in Focal. What
am I missing?
c I see a devel branch, is it assumed that it uses a packaging structure
similar to cloud-init or can someone just grab and upload master?
--
You received this bug notification
After providing more background, the Trusty package needs to be uploaded
to the security pockets to ensure our Ubuntu Pro users are able to get
this update. This is essential to Pro users getting updates from the new
esm-infra pockets.
** Changed in: unattended-upgrades (Ubuntu Trusty)
** Tags removed: verification-failed-eoan
** Tags added: verification-needed-eoan
** Tags removed: verification-dibe-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
We will not drop the Eoan task as the SRU needs to go back to all
supported versions of the package, whether or not the UA components are
available in that release.
The test for Eoan then is to verify that nothing regressed. Please re-
test that unattended-upgrades continues to function with no
** Description changed:
+ [Impact]
+
+ * Changes to the ESM repo naming and the introduction of the new esm-infra
and esm-apps suites require an update to unattended-upgrades to ensure the
security pockets are used.
+ * This change will ensure users are actually receiving updates, where as
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1850775
Title:
DNS info is not loaded
Will fix in a follow-up upload with a fix to:
https://git.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/tree
/apt-hook/hook.cc?h=ubuntu/trusty-proposed#n218
** Changed in: update-notifier (Ubuntu)
Status: Incomplete => Invalid
** Changed in: apt (Ubuntu)
Status: New =>
Hmm I was able to reproduce even having 1.0.1ubuntu2.24; adding apt as a
affects as well.
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
This is how I am reproducing:
multipass launch trusty --name t1
multipass exec t1 bash
echo "deb http://archive.ubuntu.com/ubuntu trusty-proposed main" | tee -a
/etc/apt/sources.list
sudo apt update -qq
sudo apt upgrade -y
sudo apt list --upgradable
--
You received this bug notification
** Changed in: cloud-init
Status: Confirmed => Fix Released
** Changed in: cloud-init (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
It should be removed from all types eventually, this was a distro wide
change no an ISO specific change.
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Ubuntu discontinued the use of /etc/network/interfaces a number of
releases ago and in 19.10 have removed ifupdown. Please see the
migrating to netplan document:
https://wiki.ubuntu.com/MigratingToNetplan
If you need to continue using /etc/network/interfaces then there are
ways to install
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1841654
Title:
Replace mawk with gawk in main
Status in mawk package in Ubuntu:
New
Bug
I am cleaning up zookeeper bugs and I believe that this will not be
fixed given the release it was reported on. Xenial and newer versions do
not appear to be affected by this bug. As such I am marking this
incomplete for zookeeper and allowing someone to provide reproduction
steps if it still is
Marking the Ubuntu Manpage Repository task invalid and adding the
systemd (Ubuntu) task.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-manpage-repository
Status: New => Invalid
--
You received this bug notification because you are a
Marking incomplete due to lack of response. If you did submit an
upstream bug please let us know and link to it here. Thanks!
** Changed in: ntp (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
@Anthony - should someone on the kernel team review your proposed
merge/change rather than the server team?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1786574
Title:
Hi! Thanks for taking the time to file a bug. I have re-assigned this to
network-manager as this isn't a bug with the vlan package, but with the
UI itself. It may need to be moved to yet another package, but this
should get the right people's attention.
Could you also let us know what version of
Per the comment above, please take a look at your sshd_cofig file and
verify it is valid. I am marking this incomplete until then.
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
This did not reproduce in xenial or bionic, so that narrows it down to a
change between 7.7p1-2 (cosmic) and 7.6p1-4 (bionic)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Confirmed this in a Cosmic container this morning. It appears the
version in cosmic has an issue with the underscore.
Steps to reproduce:
1. lxc launch ubuntu-daily:c c
2. lxc exec c bash
3. echo "PermitUserEnvironment yes" > /etc/ssh/sshd_config
4. ssh-import-id
5. add environment="FOO_BAR=1"
Hi, thanks for taking the time to file a bug.
The three ciphers you listed, aes128-cbc, 3des-cbc, and des-cbc, I
believe are not considered secure anymore. While your SSH client can use
them, it may not offer them without explicitly saying you wish to use
them as you have discovered.
It may be
Here are some change log entries confirming my suspicion:
openssh (1:7.4p1-1) unstable; urgency=medium
* New upstream release (http://www.openssh.com/txt/release-7.4):
- ssh(1): Remove 3des-cbc from the client's default proposal. 64-bit
block ciphers are not safe in 2016 and we
Hi, thanks for taking the time to file a bug. Based on that last message
from SSH it makes me wonder if the syntax you have is correct.
1) Can you confirm PermitUserEnvironment is set to yes in your
sshd_config?
2) Can you provide more details of the line in question in your
authorized keys
Thanks for following up! I'll mark this as invalid.
** Changed in: openssh (Ubuntu)
Status: New => Invalid
--
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/1764743
>From terminal log:
dpkg: error processing package libkrb5-26-heimdal:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Thank you for taking the time to file a bug report.
One of your packages is reporting that it is in an inconsistent state. This
needs to be solved before you continue further operations. To help you get
started please see this question and response:
Thanks for filing a bug.
>From your terminal log:
Feb 13 08:32:25 jb2-System-Product-Name sshd[3943]: /etc/ssh/sshd_config: lin...
Feb 13 08:32:25 jb2-System-Product-Name sshd[3943]: /etc/ssh/sshd_config: ter...
I'm willing to bet there is something wrong with your
/etc/ssh/sshd_config.
Try
>From your log:
Feb 11 14:57:02 de sshd[12337]: error: Bind to port X on 0.0.0.0
failed: Address already in
Feb 11 14:57:02 de sshd[12337]: error: Bind to port X on :: failed:
Address already in use.
The port you are trying to use already has something running on it.
Thanks for taking the time to file a bug!
It appears that the post-install failed to start the SSH server. The latest
version of SSH came only with 4 security fixes so it is not obvious what would
be causing this:
Thank you for taking the time to file a bug report.
It looks like the installer had issues trying to a file during the
post install. Does the /etc/ssh directory exist? what about sshd_config?
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I
>From terminal log:
/var/lib/dpkg/info/openssh-server.postinst: 171: /var/lib/dpkg/info
/openssh-server.postinst: cannot create /etc/ssh/sshd_config: Directory
nonexistent
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Since in the above I show you how to:
1) Why a random password gets set
2) Set the password non-interactively
3) Change the password
I am going to move this to incomplete and await your response as to if
further action needs to be taken. Frankly, I don't see this as a bug in
Ubuntu, other than
Thanks for taking the time to file a bug
> E.g. if the package was installed non-interactively through puppet or
> ansible, it is not obvious where the root password comes from or how
> to change it or how to re-setup.
Per Debian bug #134774, a change was made to generate a random one if a
** Changed in: debconf (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
I take this back, it is still an issue with the amd64 ISO:
https://paste.ubuntu.com/26178135/
--
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/1736770
Title:
It looks like the installer is getting further now, however, failing on
kernel package install:
https://paste.ubuntu.com/26166359/
Shall we close this bug and open a new one for that issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Here is syslog from booting using the commands in the bug description:
https://paste.ubuntu.com/26127285/
This is another boot with DEBCONF_DEBUG=developer enabled:
https://paste.ubuntu.com/26127333/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
@cyphermox, thanks for looking. I added Linux to get their look at it as
it does look like the kernel rev changed between the last successful ISO
and the current failing ISO:
Last Successful ISO had:
/pool/main/l/linux/linux-image-4.13.0-16-generic_4.13.0-16.19_amd64.deb
Currently failing ISO
Public bug reported:
During a test install of Bionic it appears that the debian-installer
/main-menu option changes priority from medium to critical part way
through the test:
Dec 6 04:18:55 debconf: --> INPUT medium debian-installer/main-menu
Dec 6 04:18:55 debconf: <-- 30 question skipped
Hey Thanks for taking the time to file a bug!
What release and version of iproute2 are you using. Here are the various
supported versions I show:
iproute2 | 3.12.0-2 | trusty | source, amd64, arm64,
armhf, i386, powerpc, ppc64el
iproute2 | 3.12.0-2ubuntu1|
Public bug reported:
Starting with the bionic ISOs setting the debconf priority level via
`debconf/priority=LEVEL` on the cmdline is not respected. Using
`priority=LEVEL` however is.
Steps to reproduce:
1. Download daily bionic ISO from
http://cdimage.ubuntu.com/ubuntu-server/daily/pending/
2.
>From terminal log:
insserv: Starting vpnagentd_init depends on plymouth and therefore on
system facility `$all' which can not be true!
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thank you for taking the time to file a bug report.
You have a locally-installed init script, /etc/init.d/vpnagentd_init,
which lacks an LSB header defining its dependencies. You can move
this init script aside to finish your install, and add an LSB header
to that script to make it compatible
Hi! Thanks for taking the time to file a bug.
Were there any additional log messages from ldap that specify additional
details to the cause of the failure that would help triage why ldap is
not happy about that option suddenly?
** Changed in: openldap (Ubuntu)
Status: New => Incomplete
>From log:
insserv: Starting panasoniclpd-init depends on plymouth and therefore on
system facility `$all' which can not be true!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
Thanks for taking the time to file a bug!
It looks like your panasoniclpd-init file in /etc/init.d/lacks an LSB
header defining its dependencies. You can move this init script aside or
add an LSB header to that script to make it compatible again.
** Changed in: ntp (Ubuntu)
Status: New =>
** Changed in: iproute2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1720126
Title:
[ip link] Message truncated error for
Hi! I am running Artful on my X1 Carbon Gen3.
I downloaded the Ubuntu Server Artful final beta and attempt to do an
install with the following qemu cli:
$ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d -hda
vdisk.img -cdrom artful-server-amd64.iso -monitor stdio
Trying to use the
*** This bug is a duplicate of bug 1646731 ***
https://bugs.launchpad.net/bugs/1646731
Thanks for taking the time to file a bug.
This looks like a duplicate of LP: #1646731. If you are still facing
this issue, it would be very very helpful if you could collect the
output of the following
Thank you for taking the time to file a bug report.
Per the log message above, you may have changed the default Python
version from 2 to 3. This leads to unexpected behavior like the errors
you are currently seeing. Can you confirm that /usr/bin/python is
version 2?
Since it seems likely to me
>From log:
Removing python-pip (8.1.1-2ubuntu0.4) ...
File "/usr/bin/pyclean", line 63
except (IOError, OSError), e:
^
SyntaxError: invalid syntax
Removing python-pkg-resources (20.7.0-1) ...
File "/usr/bin/pyclean", line 63
except (IOError, OSError), e:
Thank you for taking the time to file a bug report.
I am unable to read the rest of the terminal log, but it looks like during
the install something ran into issues with creating the above directory.
Make sure it exists and try your install again with
`sudo apt-get install -f`
Since there is not
Log (translated):
Dependency problems - leave unconfigured
/var/lib/dpkg/info/openssh-server.postinst: 164: /var/lib/dpkg/info
/openssh-server.postinst: cannot create /etc/ssh/sshd_config: Directory
nonexistent
--
You received this bug notification because you are a member of Ubuntu
Touch
Thank you for taking the time to file a bug report.
Are you able to find any logs from either the openssh-server or systemd
that show the failure?
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
>From logs (translated):
See system logs and 'systemctl status ssh.service' for details.
Invoke-rc.d: initscript ssh, action "restart" failed.
Failed to get properties: The waiting time for the connection has expired
[1mdpkg: [0m Error processing package openssh-server (--configure):
Subprocess
** Changed in: nss (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1707938
Title:
package libnss3-nssdb 2:3.28.4-0ubuntu0.14.04.2
Thank you for taking the time to file a bug report.
One of your packages is reporting that it is in an inconsistent state. This
needs to be solved before you continue further operations. To help you get
started please see this question and response:
>From logs:
dpkg: error processing package libnl-genl-3-200:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
>From log:
Processing triggers for update-notifier-common (3.168.4) ...
dpkg: error processing package libwind0-heimdal:amd64 (--configure):
package libwind0-heimdal:amd64 is not ready for configuration
cannot configure (current status 'half-installed')
--
You received this bug
Thank you for taking the time to file a bug report.
It looks like the install did not complete. Can you try running:
'sudo apt-get install -f' and see what it says?
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and
Thank you for taking the time to file a bug report.
Can you run file on the so with the invalid EFL header:
$ file /usr/lib/i386-linux-gnu/libopts.so.25
Also you may try reinstalling the package with that so:
$ sudo apt-get install --reinstall libopts25
Since there is not enough information in
>From log:
/usr/sbin/ntpd: error while loading shared libraries: /usr/lib/i386
-linux-gnu/libopts.so.25: invalid ELF header
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
Can you give the output of those commands so we can make sure the issue
has not changed and see what you are seeing? That will help us assist
you further.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnl3 in Ubuntu.
Take a look at the link in my previous message; it essentially boils
down to:
sudo apt-get install -f --reinstall libnl-genl-3-200
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnl3 in Ubuntu.
** Changed in: ntp (Ubuntu)
Importance: Undecided => High
--
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/1593907
Title:
ntpdate startup routine prevents ntp service from
>From terminal log (translated):
Dpkg: Error processing package libnl-genl-3-200: amd64 (--configure):
Package is in a very bad inconsistent condition - you should get it
Again before attempting the configuration.
--
You received this bug notification because you are a member of Ubuntu
Touch
Thank you for taking the time to file a bug report.
One of your packages is reporting that it is in an inconsistent state. This
needs to be solved before you continue further operations. To help you get
started please see this question and response:
** Changed in: libseccomp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1695808
Title:
tasks killed for nop (-1)
Status in
Thank you for taking the time to file a bug report.
Looks like SSH or some other service was already bound to port 22.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.
However, if you believe that this is
>From Journal Log:
Jun 05 18:41:17 hostname sshd[1237]: error: Bind to port 22 on 0.0.0.0 failed:
Address already in use.
Jun 05 18:41:17 hostname sshd[1237]: error: Bind to port 22 on :: failed:
Address already in use.
Jun 05 18:41:17 hostname sshd[1237]: fatal: Cannot bind any address.
--
>From terminal log (translated):
dpkg error processing package iproute2 (--configure):
Package is in a very bad inconsistent state; you should
reinstall it before attempting to configure.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thank you for taking the time to file a bug report.
One of your packages is reporting that it is in an inconsistent state. This
needs to be solved before you continue further operations. To help you get
started please see this question and response:
Thank you for taking the time to file a bug report.
It appears that something killed dpkg while it was doing an install. I
would suggest running 'sudo dpkg --configure -a' and
'sudo apt-get install -f' to determine what is left to configure.
Since there is not enough information in your report
>From terminal log:
Dpkg: error processing iproute2 (--configure) package:
The iproute2 package is not ready to be configured
Can not be configured (current state 'half-installed')
>From history log:
Error: Sub-process /usr/bin/dpkg exited unexpectedly
--
You received this bug notification
>From terminal log:
dpkg: error processing package iproute2 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Thank you for taking the time to file a bug report.
One of your packages is reporting that it is in an inconsistent state. This
needs to be solved before you continue further operations. To help you get
started please see this question and response:
We also need to confirm that this is fixed in Artful. Given it is fixed
in Debian stable it probably is, but confirming that it is fixed in the
latest development release will be required for the SRU.
** Changed in: libnl3 (Ubuntu Trusty)
Status: New => Triaged
--
You received this bug
@filofel, my bad yes you are right. This seems fixed in later versions
and as such this requires an SRU.
Next step would be to determine what changes would be required to fix.
Trusty-updates has version 3.2.21-1ubuntu4
Debian stable (jessie) has version 3.2.24-2
** Also affects: libnl3 (Ubuntu
I believe this is the upstream project:
https://github.com/tgraf/libnl
** Tags added: bitesize needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1690836
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 will 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
Hi,
This is an older bug, but came up during the daily server team bug
triage because of the recent comments. The last comment seems to
indicate that this is no longer an issue. I did attempt to do an scp
from trusty to another system using version 6.6p1-2ubuntu2.8 and found
no issues.
If this
>From log:
Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255:
/etc/ssh/sshd_config: line 2: Bad configuration option: AuthorizedKeyFile
/etc/ssh/sshd_config: terminating, 1 bad configuration options
--
You received this bug notification because you are a member of Ubuntu
Touch
Thank you for taking the time to file a bug report.
>From the log message above it appears you have a bad configuration
option in your sshd file. I believe the option you want is
'AuthorizedKeysFile'.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1683237
Title:
krb5-user: kinit fails for OTP user when using kdc discovery via DNS
Status in
Looks like they use a mailing list for bug reports:
dnsmasq-disc...@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
Hi! Thanks for reporting this and including your configuration file.
Given you are seeing this across distros I think this warrants an
upstream report. Would you be willing to file something upstream and
provide a link back in this bug report? Thanks!
** Tags added: needs-upstream-report
--
You
Hi! Thanks for looking into this and determining what was going on.
Based on the documentation I agree that it is not capturing enp* network
devices. However, as the man page says you can add a regex if you want
to capture other types of interfaces:
bridge_ports regex enp.*
If you desire to
If we want to fix this in zesty, then a release with only the bug fixes
would be desired. That could be SRU'ed assuming it is not too big of a
change such that it would limit the exposure to new issues or changes in
features/functionality.
For fixing this in the 17.10 release, then picking up the
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Thank you also for reporting this to Debian and finding the
upstream record.
If you need a fix for the bug in previous versions of Ubuntu, then the
relevant procedure is documented here:
** Changed in: krb5 (Ubuntu)
Status: New => Triaged
** Changed in: krb5 (Ubuntu)
Importance: Undecided => High
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
1 - 100 of 191 matches
Mail list logo
