Public bug reported:
Hello,
Managing a HA floating IP with netplan and keepalived brings trouble.
Im managing a two node keepalived cluster with a floating IP.
Everything works out except if i run on a the master node (which holds floating
ip) "netplan apply".
Prob netplan resets the whole
*** This bug is a duplicate of bug 1815101 ***
https://bugs.launchpad.net/bugs/1815101
Heres a possible workaround until its solved (did not test it, but seems
valid): https://chr4.org/blog/2019/01/21/make-keepalived-play-nicely-
with-netplan-slash-systemd-network/
Personally i can live with
yes please also need it :((
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743200
Title:
No support for interface labels
To manage notifications about this bug go to:
Hello,
Sorry for the late response and please reopen it.
The issue happens in a DMZ.
We have two servers in 95.216.96.128/26 with ip 95.216.96.149 and
95.216.96.150, normally we are able to reach those servers directly
(cause they are in the same subnet).
Sadly our hosting provider forbids
heres btw the netplan config im using:
network:
version: 2
renderer: networkd
ethernets:
enp0s31f6:
addresses: [ 95.216.96.148/26 ]
gateway4: 95.216.96.129
nameservers:
addresses:
- "8.8.8.8"
- "1.1.1.1"
routes:
-
** Changed in: netplan
Status: Invalid => New
** Changed in: systemd (Ubuntu)
Status: Incomplete => Opinion
** Changed in: systemd (Ubuntu)
Status: Opinion => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
heres also the netplan file for it:
root@search-3 /run/systemd/network # netplan --debug apply
** (generate:22984): DEBUG: 21:03:47.073: Processing input file
/etc/netplan/01-netcfg.yaml..
** (generate:22984): DEBUG: 21:03:47.073: starting new processing pass
** (generate:22984): DEBUG:
Public bug reported:
root@search-3 /run/systemd/network # for i in *; do echo $i; echo; cat $i; done
; sudo service systemd-networkd stop; SYSTEMD_LOG_LEVEL=debug
/lib/systemd/systemd-networkd
10-netplan-enp0s31f6.network
[Match]
Name=enp0s31f6
[Network]
LinkLocalAddressing=ipv6
This crap here drives me crazy.
Im having this on an apt-installation of "redis-server".
Ubuntu 18.04
systemctl / networkctl all clean.
kernel is not booted with console parameters (also with console parameters
doesnt work)
I tried like everything, even replacing this stupid ..
Thanks @bryce for the detailed updates.
For us personally its the second time we run into a docker daemon
restart on production (including all container restarts).
The only reason why this time it got much more attention is that a bug
prevented a clean restart of the daemon, leaving containers
Public bug reported:
Hello,
Today plenty of our systems running ubuntu 20.04 were restarting the
docker daemon, even if i blacklisted the docker package. Since docker
has an dependency on containerd thats the reason why it was restarted.
IMO the blacklist should also check the full tree of
Sorry but im not really on your side here and it also doesnt really
solve the problem.
I added docker.io to the blacklist because i want to take care manually
about the upgrades, it should leave in any case this package alone.
Adding here dependencies (containerd) for the packages will never
Thanks for beeing fully ignored..
Well see us on the next production outtake..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906364
Title:
[SRU] unattended-upgrade still restarts blacklisted
Its a bug in 1.3.* as you can read here:
https://github.com/fwupd/fwupd/issues/391#issuecomment-756941356
Also they dont want to bring an update for ubuntu 20.04 LTS as you can
read here:
https://github.com/fwupd/fwupd/issues/2708#issuecomment-758850957
Further information can also be found
Public bug reported:
Hello,
devscripts package seem to break apt installs.
using following Dockerfile:
FROM ubuntu:impish
ENV DEBIAN_FRONTEND noninteractive
RUN apt-get update -qq && apt-get install -y nano
RUN apt-get update -qq && apt-get install -y devscripts
RUN apt-get update -qq &&
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943125
Title:
devscripts breaks apt
To manage notifications about this bug
Public bug reported:
Hello,
Was running now multiple times into the issue that the minimum memory
requirements for the installer was not met. Processes got random killed
by kernel with OOM, leading to a very weird behavior of the installer.
My experience says that (in case of loading the
Public bug reported:
Hello,
Running inside an KVM, impish with latest ceph version.
Can at least reproduce it in 3 reinstalled fresh ceph clusters.
Heres the crash info for my mgr's:
ceph crash info
2021-09-12T21:09:22.866793Z_2419107c-082c-457a-b5e6-a376d779b32f
{
"archived":
Public bug reported:
Hello,
Having issues with AMD and RBD Driver. Running on latest impish, using
libvirt7.6ubuntu1.
Having following setup (not sure if matters):
Dedicated-Host (AMD) -> Level1-KVM (cpu-pass-through, rbd) -> "Customer-
VM"=CVM
ubuntu20.04 -> impish -> custom
What happens?
Thanks for this hint.
But im already using this Parameter in combination with ipxe.
Lowering to less then 3 GB brings it sometimes to fail. Doing about
50-100 installs per week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Heres are the last lines when the MGR is running, but kicked out of the
cluster:
2021-09-14T00:00:42.062+ 7f05361b8640 -1 received signal: Hangup from
pkill -1 -x
ceph-mon|ceph-mgr|ceph-mds|ceph-osd|ceph-fuse|radosgw|rbd-mirror|cephfs-mirror
(PID: 1137578) UID: 0
latest impish stable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943238
Title:
memory requirements
To manage notifications about this bug go to:
sadly it didnt solve the issue.. heres more infos about:
https://tracker.ceph.com/issues/23460
sadly i didnt found a solution until now..
** Bug watch added: tracker.ceph.com/issues #23460
http://tracker.ceph.com/issues/23460
--
You received this bug notification because you are a member
added following cron on top of ntpd, to see if this solves the issue:
0 * * * * /usr/sbin/hwclock -w --verbose --update-drift >>
/tmp/hwclock.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943423
Public bug reported:
Hello,
I'm running into issues with subiquity on a cloud provider. The cloud
provider is using an on-link L3 gateway.
His DHCP response looks like this:
OPTION: 53 ( 1) DHCP message type 5 (DHCPACK)
OPTION: 54 ( 4) Server identifier 172.31.1.1
# ceph telemetry status
Error EINVAL: SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#'
formats
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964322
Title:
Module 'devicehealth' has
Module 'balancer' has failed: PY_SSIZE_T_CLEAN macro must be defined for
'#' formats
is affected as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964322
Title:
Module 'devicehealth' has
Public bug reported:
#ceph -s
...
health: HEALTH_ERR
Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be
defined for '#' formats
..
# dpkg -l | grep ceph
ii ceph-base 17.1.0-0ubuntu1
amd64common ceph daemon
thanks @james-page, any ETA for the fix beeing on the apt mirros?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964322
Title:
Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be
hey @chris.macnaughton,
Yes i restarted all daemons, rebooted even the whole machine. As you can
see in my console logs above. Having a cluster of +10 nodes, tried it on
multiple hosts.
It was working at some point, but now it seems fully broken again. Which
is.. weird.
The mgr-daemons are
even after reboot / restart.. under random circumstances this bug comes
back.
~ # dpkg -l | grep ceph
ii ceph-base 17.1.0-0ubuntu3
amd64common ceph daemon libraries and management tools
ii ceph-common
A lot of trouble, traced it down.
So basicly the fix is working.
The reason was an 'old' not restarted daemon on another host.
Very confusing is that even an old daemon can break itself (which is
expected) AND the CLI tools on another host. Which was not expected by
me and confused me hardly.
~ # dpkg -l | grep ceph
ii ceph-base 17.1.0-0ubuntu3
amd64common ceph daemon libraries and management tools
ii ceph-common 17.1.0-0ubuntu3
amd64common utilities to mount and interact
Uhm, interesting.. its maybe still fixed.
But it needs a reconnect of ssh/reboot after installing the new
packages..
** Changed in: ceph (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Hello,
It happened now twice for me that after a "unattended update" the linux
kernel is missing routes which were announced via BGP. From my point of
view, the problem is that networkd is restarted(?). Which leads to a
deletion of the routes in linux kernel.
# cat
happened on jammy
** Changed in: frr (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968550
Title:
unattended updates, missing routes
To manage
Funny thing is that the rfc 3442 is from 2002.
Thats what makes me wonder of the missing support till today...
My workarround till today is to unzip the iso -> kernel+initrd, patch
the initrd, and use the patched initrd.
I would not recommend anyone to do it like that, only if theres no other
37 matches
Mail list logo
