** Changed in: multipath-tools (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/1944005
Title:
System Lockup during failover
To manage notifications about
Subscribed field-critical as this issue is blocking the environment to
go live.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944005
Title:
System Lockup during failover
To manage notifications
Hi Lucas,
FYI, this is affecting a customer deployment and I am working with
Jarred on this issue. We have tried a few variations of the multipath
configuration. The current config is the following:
defaults {
user_friendly_names yes
find_multipaths yes
polling_interval 10
}
devices {
** Tags added: cpe-onsite
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944005
Title:
System Lockup during failover
To manage notifications about this bug go to:
That situation occurs as well when installing nvidia-utils-* (in my case
nvidia-utils-450-server), which installs nvidia-settings. See
https://archlinux.org/packages/extra/x86_64/nvidia-settings/. This
requirement is optional and should be omitted on servers, as the same
issue will occur
To confirm this is the bug in /var/log/ovn/ovn-controller.log on the
hypervisors look for:.
2021-03-02T10:33:35.517Z|35359|ovsdb_idl|WARN|transaction error:
{"details":"RBAC rules for client
\"juju-eab186-zaza-d26c8c079cc7-11.project.serverstack\" role
\"ovn-controller\" prohibit modification
The maas version is the snap 2.8/stable (2.8.4-8597-g.05313b458) and the
image stream is the default one that comes with maas.io for 20.04 and
18.04. I'm not sure how to determine which image stream or bootloader
revision comes with that from this website
screenshot added
** Attachment added: "pxe-boot-2.png"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1917665/+attachment/5472227/+files/pxe-boot-2.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On Dell Poweredge R740, commissioning from MAAS fails because the PXE
booting process does not start properly. It exits into the grub command-
line quickly after attempting to PXE booting over IPV4.
The only workaround working so far is to connect to the remote console
Subscribed field-high
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917665
Title:
PXE booting exits into grub command-line
To manage notifications about this bug go to:
I was finally able to use the workaround on a Dell R740 remote console.
On the Install Ubuntu screen, click e for options, add "fsck.mode=skip"
before "quiet" on the 2nd line, then do ctrl+x to save the changes. It
skipped the integrity check successfully.
--
You received this bug notification
subscribed ~field-medium. This bug impacts deployments ands add very
long delays for the installation of the infra nodes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892369
Title:
Impossible to
https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/27
** Bug watch added: gitlab.gnome.org/GNOME/at-spi2-core/-/issues #27
https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/27
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, thank you for the info, I'll move the bug over there
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775392
Title:
at-spi-bus-launcher makes Xorg crash when resuming from suspend
To manage
upstream bug can be found here
https://bugzilla.gnome.org/show_bug.cgi?id=796512
** Bug watch added: bugzilla.gnome.org/ #796512
https://bugzilla.gnome.org/show_bug.cgi?id=796512
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1775392 ***
https://bugs.launchpad.net/bugs/1775392
Re-Actually , we kept getting the failure to login and the gnome crash
even by restarting sssd regularly.
I finally isolated my problem to be a duplicate of this bug
Same bug seen on Ubuntu Bionic 18.04.5 LTS with Lenovo P53.
In my case, the bug seen when attempting a domain login in ubuntu. About
75% of the time, the login hangs for several minutes, then the screen
turns black, and returns to the greater. Once in a while, the user is
able to login.
The
The problem was more with sssd than gnome.
Not sure of the exact source of the problem with SSSD, but applying the
following worked as a workaround :
- Run `sudo systemctl edit sssd.service` and add the following:
[Service]
RuntimeMaxSec=1800
Restart=on-failure
- Restart SSSD:
$ sudo
The vpn client is not causing the timeout. However, I found a lot of
kerberos errors in the auth.log and syslog upon subsequent attempts at
solving this issue.
(Tue Oct 27 10:54:53 2020) [[sssd[ldap_child[9515 [ldap_child_get_tgt_sync]
(0x0010): Failed to init credentials: Preauthentication
** Attachment added: "auth.log"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1901552/+attachment/5427390/+files/auth.log%20-%20bug-report
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
A Lenovo P53 is installed with ubuntu 18.04.5 LTS.
Graphics Intel UHD Graphics 630 (main display), nvidia quadro RTX 5000 also
installed but not used for main display.
Laptop is domain joined. When logging to the local ubuntu user, there is
no problem detected. Then, if
Could we change the name of the bug? It is not a kernel bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881821
Title:
Kernel does not report interface speed correctly for Cisco UCS B200 M5
Testing with MAAS 2.6 and the network interfaces were detected
correctly. This points to MAAS 2.7 having a bug in the way it tests the
link speeds. Also, the smartctl-validate tests were successful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Is this fixed in the latest release of the ubuntu 19.04 image? I seem to
be having a very similar issue when booting a ubuntu 19.04 image in
hyper-v. I am not getting a full install, it freezes before completion,
so I am unsure how I could go run the snap refresh if I cannot get into
the server.
Hi, I see that the backport fix is released and/or committed to MAAS
2.2, 2.6 and 2.7. Can we get it backported to 2.4 as well? It is
currently affecting a customer in production. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Similar behaviour documented in this bug for ceph-mon and ceph-osd with
disco series. https://bugs.launchpad.net/charm-ceph-mon/+bug/1842498.
Might be a duplicate if the underlying cause is the same
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
26 matches
Mail list logo
