[Bug 1944005] Re: System Lockup during failover
** 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1944005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944005] Re: System Lockup during failover
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1944005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944005] Re: System Lockup during failover
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 {
device {
vendor "PURE"
product "FlashArray"
path_selector "queue-length 0"
path_grouping_policy "group_by_prio"
rr_min_io 1
path_checker tur
fast_io_fail_tmo 1
dev_loss_tmo infinity
no_path_retry 5
failback immediate
prio alua
hardware_handler "1 alua"
max_sectors_kb 4096
}
}
multipaths {
multipath {
wwid ""
alias data1
}
}
This configuration is used successfully in other systems (Ubuntu 18.04,
Debian, Centos) in the customer environment and is the recommended
configuration from their storage team.
For context, the ubuntu nodes that are affected are part of an Openstack
deployment. The multipath configuration is in place to set a
FibreChannel connection for the device used as Ceph-OSD. The failover
was tested in 2 different ways, which both led to nodes being
unresponsive. First, we turned off one of the F5 switch to simulate a
power failure. The other way we've tested it is by resetting the I/O
module in UCS manager for the chassis where the nodes are located.
As you can see, there's very little information in the logs about what
is actually causing the node to go wild. Do you have guidance on how to
gather more detailed logs? Jarred and myself can provide live access to
the environment if needed.
--
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:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1944005/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944005] Re: System Lockup during failover
** 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: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1944005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929868] Re: Should nvidia-driver-XXX-server stop recommending nvidia-settings?
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 (hibernation, unreachable node, very difficult to recover) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929868 Title: Should nvidia-driver-XXX-server stop recommending nvidia-settings? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1929868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917475] Re: RBAC Permissions too strict for Port_Binding table
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 of table
\"Port_Binding\".","error":"permission error"}
2021-03-02T10:33:35.518Z|35360|main|INFO|OVNSB commit failed, force recompute
next time.
To disabel rbac, on an ovn-central unit:
# sudo ovn-sbctl find connection
_uuid : a3b68994-4376-4506-81eb-e23d15641305
external_ids: {}
inactivity_probe: 6
is_connected: false
max_backoff : []
other_config: {}
read_only : false
role: ""
status : {}
target : "pssl:16642"
_uuid : ee53c2b6-ed8b-4b21-9825-a4ecaf2bdc95
external_ids: {}
inactivity_probe: 6
is_connected: false
max_backoff : []
other_config: {}
read_only : false
role: ovn-controller
status : {}
target : "pssl:6642"
Look for the 6642 listeners uuid. In this case 'ee53c2b6-ed8b-
4b21-9825-a4ecaf2bdc95'
Remove the role to disable rbac:
# sudo ovn-sbctl set connection ee53c2b6-ed8b-4b21-9825-a4ecaf2bdc95
role=''
Restart the ovn-controller service on the hypervisors.
To reenable rbac:
# sudo ovn-sbctl set connection e0cef788-df18-4b1b-a238-e8b79ea51c7c
role='ovn-controller'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917475
Title:
RBAC Permissions too strict for Port_Binding table
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1917475/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917665] Re: PXE booting exits into grub command-line
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 http://images.maas.io/ephemeral-v3/stable/. If there's a cli command I can run to find out, let me know. This is with UEFI. -- 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: https://bugs.launchpad.net/maas/+bug/1917665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917665] Re: PXE booting exits into grub command-line
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. https://bugs.launchpad.net/bugs/1917665 Title: PXE booting exits into grub command-line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1917665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917665] [NEW] PXE booting exits into grub command-line
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 during the commissioning phase, wait for the grub command-line, then type "exit", enter, and then the PXE booting resume correctly. This forces a manual interaction for every server commissioned through MAAS, which slows down considerably a deployment. MAAS version: 2.8/stable: 2.8.4-8597-g.05313b458 Commissioning images affected: 18.04, 20.04.2, with default kernel and hwe-edge kernel Integrated NIC : Intel(R) Ethernet 10G 4P X520/I350 rNDC (PXE over port 3) version 19.5.12 Dell BIOS version: 2.10.0 Thanks for the help ** Affects: grub2 (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/1917665 Title: PXE booting exits into grub command-line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1917665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917665] Re: PXE booting exits into grub command-line
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: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1917665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892369] Re: Impossible to skip integrity test for ubuntu-server 20.04.1 iso
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892369 Title: Impossible to skip integrity test for ubuntu-server 20.04.1 iso To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892369] Re: Impossible to skip integrity test for ubuntu-server 20.04.1 iso
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 skip integrity test for ubuntu-server 20.04.1 iso To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend
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. https://bugs.launchpad.net/bugs/1775392 Title: at-spi-bus-launcher makes Xorg crash when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend
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. https://bugs.launchpad.net/bugs/1775392 Title: at-spi-bus-launcher makes Xorg crash when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901552] Re: Unrecoverable failure in required component org.gnome.Shell.desktop
*** 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 https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392 ** Tags removed: cpe-onsite ** This bug has been marked a duplicate of bug 1775392 at-spi-bus-launcher makes Xorg crash when resuming from suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901552 Title: Unrecoverable failure in required component org.gnome.Shell.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1901552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend
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 workaround of removing the at-spi2-core package effectively stops the crashes -- but this removes also other functionalities. For example, nautilus is removed. Is there a patch available, or did anyone report the bug upstream yet ? Logs of the error : Nov 20 15:44:47 HOSTNAME gnome-session[5658]: gnome-session-binary[5658]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Nov 20 15:44:47 HOSTNAME gnome-session[5658]: gnome-session-binary[5658]: CRITICAL: We failed, but the fail whale is dead. Sorry Nov 20 15:44:47 HOSTNAME gnome-session-binary[5658]: Unrecoverable failure in required component org.gnome.Shell.desktop Nov 20 15:44:47 HOSTNAME gnome-session-binary[5658]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Nov 20 15:44:47 HOSTNAME gnome-session-binary[5658]: CRITICAL: We failed, but the fail whale is dead. Sorry Nov 20 15:44:47 HOSTNAME at-spi-bus-launcher[5774]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1" Nov 20 15:44:47 HOSTNAME at-spi-bus-launcher[5774]: after 21 requests (21 known processed) with 0 events remaining. ** 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/1775392 Title: at-spi-bus-launcher makes Xorg crash when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901552] Re: Unrecoverable failure in required component org.gnome.Shell.desktop
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 systemctl restart sssd.service This will restart sssd.service every 30 minutes unless you manually stop it, in which case it'll stay stopped until you manually start it again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901552 Title: Unrecoverable failure in required component org.gnome.Shell.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1901552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901552] Re: Unrecoverable failure in required component org.gnome.Shell.desktop
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 failed (Tue Oct 27 10:54:53 2020) [[sssd[ldap_child[9516 [ldap_child_get_tgt_sync] (0x0010): Failed to init credentials: Client 'wllnxrxxx...@domain.com' not found in Kerberos database I'm trying to figure out the correct configuration for sssd + realmd + kerberos to be able to join my computer to the AD domain. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901552 Title: Unrecoverable failure in required component org.gnome.Shell.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1901552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901552] Re: Unrecoverable failure in required component org.gnome.Shell.desktop
** 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. https://bugs.launchpad.net/bugs/1901552 Title: Unrecoverable failure in required component org.gnome.Shell.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1901552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901552] [NEW] Unrecoverable failure in required component org.gnome.Shell.desktop
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 we log out and try to login with a domain user, gnome crashes. >From what I can see in the logs, the user is authenticated correctly, but then in the instantiation of the session, gnome.shell.desktop faces an unrecoverable failure. >From auth.log ``` pam_sss(gdm-password:auth): authentication success; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=u...@na.cie.com Oct 23 16:27:28 WLLNXPFX gdm-password]: pam_unix(gdm-password:session): session opened for user u...@na.cie.com by (uid=0) Oct 23 16:27:28 WLLNXPFX systemd-logind[1200]: New session 17 of user u...@na.cie.com. ``` >From syslog ``` Oct 23 10:17:42 WLLNXPFX gnome-session[1914]: gnome-session-binary[1914]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 23 10:17:42 WLLNXPFX gnome-session[1914]: gnome-session-binary[1914]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 23 10:17:42 WLLNXPFX at-spi-bus-launcher[2026]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Oct 23 10:17:42 WLLNXPFX at-spi-bus-launcher[2026]: after 21 requests (21 known processed) with 0 events remaining. ``` I will include the full syslog and auth.log to this bug. Please let me know if any other log could be useful to troubleshoot. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: cpe-onsite ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1901552/+attachment/5427389/+files/syslog%20-%20bug%20report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901552 Title: Unrecoverable failure in required component org.gnome.Shell.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1901552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
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 blade To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
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 to Ubuntu. https://bugs.launchpad.net/bugs/1881821 Title: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831453] Re: [Hyper-V] Install issue for Ubuntu 19.04
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831453 Title: [Hyper-V] Install issue for Ubuntu 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/probert/+bug/1831453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken
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 Ubuntu. https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842751] Re: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842751 Title: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder/+bug/1842751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
