On 18/01/2021 12:46, Launchpad Bug Tracker wrote:
> This bug was fixed in the package adduser - 3.118ubuntu5
>
> ** Changed in: adduser (Ubuntu Hirsute)
>Status: Fix Committed => Fix Released
\o/
Well done and thank you to everyone who worked to make this happen.
I wonder if there
On 28/08/2020 22:19, vexorian wrote:
> Maybe Gnome developers and Canonical can live in a pretend world where a
> Hamburger menu is a remotely-acceptable UX in A DESKTOP OS, but for
> those of us who use Ubuntu professionally this design is just not
> practical.
You are of course entirely
Just to say thank you for progressing this :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870087
Title:
Old broker lockfile blocks landscape-client starts
To manage notifications about this bug
Removing broker.sock and broker.sock.lock allowed the client to start up
cleanly.
We definitely have not addressed this issue correctly or completely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi folks, I am still seeing this issue intermittently in Ubuntu 20.04.
$ sudo apt-cache policy landscape-client
landscape-client:
Installed: 19.12-0ubuntu4.1
Candidate: 19.12-0ubuntu4.1
Version table:
*** 19.12-0ubuntu4.1 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main
Is there an updated target release for the ability to describe
configuration for an interface (such as name) but leave the interface
down at boot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664844
OK, will circle back to this bug in due course. From what you say it
might even be specific to that Nuc.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872964
Title:
Reliable crash in
Hi Seth
I have been deploying charmed-kubernetes on a LXD cluster. I didn't
think the kernel crash was workload-specific, but of course it might be.
It looked more likely to be ZFS + lowlatency + snaps triggering the issue.
For now I have had to move to -generic on the machine which was causing
Hi folks, I think you need to reopen this bug. I just saw the issue
again on several Focal machines. It's definitely not 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/1870087
Title:
Just to confirm and still seeing this with today's -24 package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872964
Title:
Reliable crash in lowlatency kernel with LXD
To manage notifications
The update to landscape-client 19.12-0ubuntu4 failed on several of my
servers. I apply updates via Landscape, so it might be a divide-by-zero
issue with landscape failing to update itself cleanly. I did a
widespread push of updates and saw several servers fail. When I ssh to
the actual servers and
Thanks all, I will keep an eye on my systems to see if the issue goes
away. It was triggered regularly on Focal machines so should be quite
easy to spot if it comes back :).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just wanted to say thank you Vincent, Christian, and it's really great
to see you working together this way!
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872183
Title:
package chrony
Public bug reported:
Hello, I am able to crash 5.4.0-21-lowlatency running LXD. This machine
in an Intel NUC, part of a three-member LXD cluster. The other machines
do not show this crash and they are not running the lowlatency kernel,
but that might be incidental. I will swap out the generic
gpsmon is the primary tool I use from the clients package, just to see
that gpsd it tracking things properly and to see the PPS is active.
Agree that gpsctl makes more sense in the gpsd package itself, if you
think the same applies to the non-Python bits then the dependencies of
gpsd might stay
Public bug reported:
gpsd-clients depends on gir1.2-gtk-3.0 which brings in a bunch of X
dependencies, I think for xgps and xgpsspeed. If those were split into a
separate package, perhaps gps-xclients or gps-clients-graphical, then
headless systems could avoid the X dependencies.
** Affects:
** Also affects: gpsd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: chrony (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872178
Title:
GPSD unable to use
Upgrade from bionic to focal broke for this system which has chrony
installed.
After do-release-upgrade exited (warning that the system was in an
indeterminate state) I was unable to fix the system initially. It seemed
that systemd-timesyncd was somehow interacting badly with chrony:
$ sudo apt
Public bug reported:
Failed during bionic->focal upgrade
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: chrony 3.2-4ubuntu4.2
ProcVersionSignature: Ubuntu 4.15.0-97.98-lowlatency 4.15.18
Uname: Linux 4.15.0-97-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
Public bug reported:
I am working with gpsd and a pulse-per-second (PPS) signal on a serial
port.
GPSD is able to detect the PPS signal but it is not able to use Kernel
PPS for lower jitter. Here are the relevant log lines when PPS is being
detected and enabled:
gpsd:INFO: KPPS:/dev/ttyS0
Public bug reported:
GPSd fails to access the socket used to communicate PPS signals with
Chrony.
>From the startup log:
gpsd:PROG: PPS:/dev/ttyS0 connect chrony socket failed:
/var/run/chrony.ttyS0.sock, error: -2, errno: 13/Permission denied
The socket in question has these permissions:
$
Public bug reported:
Looks like a file has moved between packages which caused the dpkg
error. The issue was resolved with "apt --fix-broken install" but
nevertheless we should make sure nobody sees this on upgrade. Thanks!
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package:
Pawel, this is great debugging, thank you. Agree it's an edge case.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868706
Title:
Snapd postinst script hangs
To manage notifications about
OK, so *now* the situation has cleared on that machine. And there are no
snaps installed :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868706
Title:
Snapd postinst script hangs
To manage
@kai-mast I think grub is the only way, since both sudo and login are
stuck under these circumstances.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867431
Title:
ERROR got an error from dpkg for
@jbouter you are a lifesaver. Or at least, a weekend-saver, thank you :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867431
Title:
ERROR got an error from dpkg for pkg: 'libc6'
To manage
Added another term.log, hope that's useful
** Attachment added: "term.log"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1867431/+attachment/5336953/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ah, thank you Andreas, that is a good catch.
I believe the ISC maintains some .debs themselves, and it would be worth
reaching out to see if they want to collaborate to avoid this sort of
gotcha. They do have some additional commercial packages they would care
about, and we should offer to
Public bug reported:
I tested do-release-upgrade -d on a few servers with simple setups. In
both cases, openssh-server was removed. Given that the upgrader warned
me about doing the upgrade over SSH, this was surprising :) I think we
should whitelist openssh-server to ensure it stays installed
Along with the move, please update the default configuration for
/etc/kea/kea-ctrl-agent.conf to refer to the appropriate location
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863100
Title:
Move
Here is apt's term.log:
Log started: 2020-02-15 11:52:34
(Reading database ... 138590 files and directories currently installed.)
Purging configuration files for isc-kea-common (1.6.1-isc0042520191119145256)
...
userdel: user _kea is currently used by process 1435
/usr/sbin/deluser:
Public bug reported:
I upgraded to kea 1.6 in Focal, and saw an old isc-kea-common package
with configuration files. Removing that threw up a number of
uncomfortable looking error messages about _kea user and group removal
failing. I don't think our transition approach is yet clean.
** Affects:
Ran into this today, confirming.
** Changed in: isc-kea (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809262
Title:
Missing hooks library
To manage
** Changed in: isc-kea (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858347
Title:
Wrong PID-File-Directory in /usr/sbin/keactrl in Ubuntu 20.04 LTS
To
Public bug reported:
After a fresh 18.04.2 desktop install, I have a curious item at the top
of the launcher called 'Install RELEASE' which doesn't correspond to
anything I was expecting or want on the system. Screenshot attached.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
OK, interesting. I really don't like the reloading strategy but am not
sure that BIND gives us many better options. Let us know what you find.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 6/26/19 5:12 PM, Sam Lee wrote:
> When I compare our v2.5.3 install from our v2.4.2 install, the amount of
> rndc reloads is vastly more on v2.5.3.
Hi Sam, I don't see these issues any more, on 18.04 and 2.6. I see
reloads every few minutes on a stable MAAS (i.e. without a lot of
activity).
Sorry for the regression, and thanks for the detailed bug report. I'm
sure a fix will be relatively quick and straightforward, but as an aside
I would suggest that you run some machines on -proposed because that's
where we cook changes to the deep plumbing, and this one was there for a
reasonable
Confirmed that 3ubuntu10.15 fixes the core-dump in systemd-networkd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818340
Title:
systemd-networkd core dumps in bionic-proposed
To manage
Just to let you know, I still see 237-3ubuntu10.14 in -proposed and I
think that's the one that has the issue.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818340
Title:
systemd-networkd
Apport info from an affected system is in #1818487
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818340
Title:
systemd-networkd core dumps in bionic-proposed
To manage notifications about this
*** This bug is a duplicate of bug 1818340 ***
https://bugs.launchpad.net/bugs/1818340
Public bug reported:
This is apport info for systemd related to #1818340
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.14 [modified:
Timestamping seems to be working. However there may be other networking
issues in -proposed that could be kernel related (captured in bug
#1818340) that might warrant a hold on promotion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I found that the bond seems not to have come up properly:
$ sudo cat /proc/net/bonding/bond-lan
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2+3 (2)
MII Status: down
MII Polling Interval (ms): 100
Up
Taking the bond down and then bringing it back up again seemed to sort
out the aggregation. I was able to assign an IP address to the bond and
ping it. However, even with the bond sorted, restarting systemd-networkd
dumps core.
--
You received this bug notification because you are a member of
Further digging in journalctl shows:
-- Unit systemd-networkd.service has begun starting up.
Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-lan: netdev ready
Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]: bond-net: netdev ready
Mar 02 20:37:00 4-ridge-fw1 systemd-networkd[6851]:
Needless to say I suggest not promoting systemd from -proposed until
this is figured out :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818340
Title:
systemd-networkd core dumps in
Public bug reported:
I run a number of servers with -proposed enabled and have seen a bunch
of this today:
Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with
result 'core-dump'.
Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service.
These machines
Hold on, I think this bug is still problematic for MAAS and Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710278
Title:
[2.3a1] named stuck on reload, DNS broken
To manage notifications
This does seem like a significant shortcoming in the current 18.04
install experience. Let's fix it in 19.04 and it will be available for
18.04 existing install media with a straightforward snap refresh.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
&& works better :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810578
Title:
Set correct terminal size to improve login over serial port experience
To manage notifications about this bug go to:
Hmm... that .profile causes this on SSH logins, so needs tweaking:
Last login: Sat Jan 5 10:49:02 2019 from 192.168.4.70
[1]+ Exit 1 [[ $(tty) == /dev/ttyS* ]]
john@xx:~$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
For people who use ipmiconsole or other serial port access to servers a
great deal it would be helpful to set LINES and COLUMNS correctly on
login. There are a number of ways to do this. I found a small (10k) C
application at:
Hi folks
Thanks for working on this. However, I think it unwise to change the
units of the unqualified number in an SRU. That would mean that people
who adjusted to "1" (second) as I did would suddenly find themselves at
1ms.
Rather, I suggest:
* keep the unqualified number as seconds
*
Fine-grained network security for snaps is going to be fantastic, but
it's also a rich area, and when networking policy stuff is done
simplistically it becomes awkward more than useful.
I'd suggest that we start now working up detailed design on the topic,
so that when we are ready to start
Seems like the point release would be a reasonable SRU.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791958
Title:
iptables-restore is missing -w option
To manage notifications about this
Hi Seth, 18.04 LTS is plenty for my purposes and for users wanting to
kick the tires on the functionality. No need for a backport on the
change at this stage.
Thank you!
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Colin, thanks for the analysis.
No rush on the change.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785816
Title:
Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING
To manage notifications
Thanks folks, looking forward to the results. I would have thought it
would noop where the feature was not in use; as far as I know it
requires explicit activation.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hi folks, is there a reason we do not enable
CONFIG_NETWORK_PHY_TIMESTAMPING ? I'm not sure of the tradeoffs but I
think this config option is required for PTP time syncronization which
would be useful in telco and financial (and OCD :)) environments.
** Affects: linux
\o/ thanks all, glad that one got in for the point release.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761997
Title:
/var/run needs mode 777 in bionic
To manage notifications about this
On 05/17/2018 06:52 AM, Christian Ehrhardt wrote:
> GPSD calls systemd helpers for the service which will end up in *inst
> maintainer scripts.
> in d/rules are:
> dh_systemd_enable -pgpsd
>
> dh_installinit
** Changed in: gpsd (Ubuntu)
Status: Incomplete => Invalid
** Changed in: chrony (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771080
Title:
I have an odd behaviour in that gpsd starts on one machine but not on
the other. I think this is just me being new to systemd, please let's
close this bug as invalid until I have a deeper root cause. Thanks for
the help!
status invalid
--
You received this bug notification because you are a
I think the existing gpsd.service has a bug in that it states
After=chronyd.service when the correct service is chrony.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771080
Title:
gpsd
Thanks Christian. The SOCK method is a much more accurate (apparently)
way for chrony and gpsd to communicate. I do think we need to lock gpsd
down as well but that's a separate issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When using GPSD to provide a time signal over a socket to chrony, it is
necessary to start gpsd after chrony (I think this is so that gpsd finds
the /var/run/chrony.ttySX.sock file when it launches). gpsd tends to
want to drop privileges quickly which makes it hard for it to
Public bug reported:
When using chrony with gpsd for very accurate time, chrony wants to
create a file called /var/run chrony.ttyXX.sock which gpsd will use when
it starts. The current apparmor rules for chrony prevent that file from
being created. I was able to fix this by manually adding this:
Yes, thanks Michael, all three for consistency.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764413
Title:
may be clearer than
To manage notifications about this bug go to:
Ah, elegant approach, BUT we'll need to maintain that patch carefully if
it doesn't get upstreamed, a lazy future merge will just cause the
problem to resurface.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In the did-you-mean case (a command that is not found and which is not
an exact match for an existing command but is close enough to warrant
suggestions) it might be clearer to suggest 'snap info '
rather than 'snap info '. The use of a tight snapname suggest
a single-word
Yes, the issue is on upgrade, where if you don't add the 'Systemd on'
config, it fails.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761994
Title:
Shift of conntrackd to systemd notification
Public bug reported:
I saw some odd behaviour of screen during the upgrade from Xenial to
Bionic using do-release-upgrade. I was trying to use screen to reattach
to an upgrade process that had gone sideways during a router daemon
upgrade (duh). But I was told that the permissions on /run/screen
Public bug reported:
In Bionic, conntrackd configuration needs to be updated to use systemd
notification otherwise we get problems during the upgrade process.
Ultimately, it requires putting up with broken debconf scripts in the
upgrade process, editing the file to reflect the new location,
Public bug reported:
The new language for CNF with snaps is much better thank you, but there
is a mistake in that it recommends that you use 'snap info' with the
*command* when it should in fact be 'snap info '. As an
example:
mark@mark:~$ aws
Command 'aws' not found, but can be installed as:
Thanks for the attention on this bug, but the upgrade process isn't
reliable:
Unpacking libwsman-client4:amd64 (2.6.5-0ubuntu2~18.04.2) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-a3GKdH/7-libwsman-client4_2.6.5-0ubuntu2~18.04.2_amd64.deb
(--unpack):
trying to overwrite
Thanks, this will resolve a bunch of update issues in bionic. Also
interested to know if the newer wsman helps or hinders AMT devices.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754012
Title:
Public bug reported:
The browser used in the captive portal system is reported as 'Desktop Safari
Linux 64'. Could we change this to 'Ubuntu Desktop', please?
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
On 02/21/2018 01:36 PM, Michael Vogt wrote:
> We are working on improving this currently. Right now c-n-f has no
> version concept for the apt backend (easy for snaps). But we have a plan
> how to fix that (some work though).
For the apt version, I thought we would just display the current
Perhaps this would be a better format:
$ aws
The command 'aws' can be installed as:
snap aws-cli (1.14.38)
deb awscli (1.14.36-1)
See 'snap info aws-cli' for additional versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Perhaps we are talking at cross purposes. My expectation is that update
would list the packages to be removed because they are no longer
dependencies of packages that were consciously installed. On that basis,
there should be no surprise to users. The messaging could point users to
a handy
Public bug reported:
Would it be possible to change 'found' to 'installed', and show
potential versions? For example:
$ aws
The program 'aws' can be installed as:
* snap 'aws-cli' (1.14.38)
* deb 'awscli' (1.14.36-1)
** Affects: command-not-found (Ubuntu)
Importance: Undecided
Public bug reported:
I see this on upgrade on one machine, which is unexpected. If this file
is generated by each machine, why would we ship a default?
Configuration file '/etc/ssh/moduli'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated
Can we bump up the priority of this, please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731868
Title:
vmware reported as 'EC2', 'None'
To manage notifications about this bug go to:
Thanks all, and Dimitri allow me to sponsor that Starbucks coffee :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
Title:
systemd-resolved is not finding a domain
To manage notifications
The main reason to do this is kernel cruft. We have had kernels being
flagged for removal for years now, and it's completely reliable. We
really should garden that automatically.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In bionic, apt upgrade should also autoremove by default. I have a few
bionic systems (upgrades from xenial mostly) which are not yet showing
that behaviour, it may be we haven't implemented that yet so this is
just a placeholder bug in that case :)
** Affects: apt (Ubuntu)
Confirmed, I am seeing this everywhere that local fonts are being used.
I think it's a fontconfig or related regression.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512111
Title:
"Ubuntu
Yes, this is a captive portal situation on up-to-date 17.10. The captive
portal popup fails with a DNS error looking for
securelogin.arubanetworks.com and then hilarity ensues. Manually editing
/etc/resolv.conf to use one of these DNS servers makes it all work. So
the problem is systemd-resolved
Public bug reported:
I have an odd network situation that I have so far managed to narrow
down to the inability to resolve a domain via systemd-resolved which is
resolvable with nslookup. If I use nslookup against the two nameservers
on this network I get answers for the domain, but ping says it
I think Andres has access to the GMAAS, would appreciate if he could
verify the fix there. If not, let me know and I can try it.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
I think it maybe that 15.3 had the issue, and 15.4 is OK. When I
rebooted I was able to complete the 15.4 update, and another machine
managed to do the 15.4 update without trouble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
There is an SRU for 1.108ubuntu15.4 in xenial-proposed that hangs for me
on upgrade, causing updates to get stuck across the system. Haven't
tracked it down further than that but wanted to report a bug quickly to
prevent further promotion of the package.
** Affects:
Might this also be why the boot is so slow on the server live-install image?
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619258
Title:
netplan should allow NICs to be disconnected and not
OK, restarting via 'sudo service bind9 restart' does work in the end, it
just takes a long time. The downside is that MAAS is not going to have
an effective DNS for a few minutes, which is unacceptable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
OK, will do, thanks :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710278
Title:
[2.3a1] named stuck on reload, DNS broken
To manage notifications about this bug go to:
To avoid reloads in parallel, I think we should:
* verify the reload happened (perhaps checking zone serial?)
* make sure we defer and subsequent reload at least 10 seconds
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 12/08/17 01:11, Mike Pontillo wrote:
> Finally, I think your last bullet requires more discussion before we can
> work on it. MAAS currently uses sudoers rules specific to the init
> system to start and stop services like bind9; we do not currently have
> permission to 'kill -9' arbitrary
In MAAS, we should:
* throttle reloads (at least make sure a reload is complete before we
trigger the next one)
* monitor the actual service from the perspective of rackd's (perhaps
have rackd's do a dig @region-controller for a name we send them
whenever they talk to the region controller)
*
Yes, we need a mirror network, including China.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612882
Title:
Snap store very slow
To manage notifications about this bug go to:
1 - 100 of 1806 matches
Mail list logo
