You can also just:
sudo snap stop maas
Then init lxd
No need to remove the maas snap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1995194
Title:
lxd init fails with 'Address already in use'
To
*** This bug is a duplicate of bug 1944586 ***
https://bugs.launchpad.net/bugs/1944586
Dulicate of bug which is now fixed in stable
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944586/comments/8
** This bug has been marked a duplicate of bug 1944586
kernel bug found when disconn
Public bug reported:
On focal/ussuri latest deployment packages (deployed 2 days ago)
I'm seeing failure to delete stacks when I have debug flag on.
openstack stack delete f57323ae-ebd8-4296-8472-9ffbe159a876
Are you sure you want to delete this stack(s) [y/N]? y
ERROR: b'\n\n503 Service
Unavai
** Description changed:
[Impact]
It has been brought to my attention the following:
"
We have been experiencing node lockups and degradation when testing fiber
channel fail over for multi-path PURESTORAGE drives.
Testing usually consists of either failing over the fabric or the
Ok that looks like a client environment problem. Never mind.
Steven
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911228
Title:
enable-fips doesn't work on bionic
To manage notifications about th
Having some trouble adding this repository.
sudo add-apt-repository -m ppa:ua-client/staging
Cannot add PPA: 'ppa:~ua-client/ubuntu/staging'.
ERROR: '~ua-client' user or team does not exist.
---
We can curl the address so it does not seem like a proxy issue.
curl http://ppa.launchpad.net/ua-
Sorry for the resubmit but wanted to get this to the field-high users...
I'm escalating this to field high as this is impacting deployment on 4 customer
clouds.
We can do this manually but it is a much more involved process and with the
large number of nodes we need to deploy this will be prone
I'm escalating this to field high as this is impacting deployment on 4 customer
clouds.
We can do this manually but it is a much more involved process and with the
large number of nodes we need to deploy this will be prone to error and risk.
It is my understanding that FIPS for bionic is through
Work around
Load:
sudo modprobe nf_conntrack_ipv4
Confirm:
lsmod | grep nf_conntrack_ipv4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834213
Title:
After kernel upgrade, nf_conntrack_ipv4 modu
Kernel version
uname -r
4.4.0-150-generic
apt list --installed | fgrep image
cloud-image-utils/xenial-updates,now 0.27-0ubuntu25.1 all [installed,automatic]
genisoimage/xenial,now 9:1.1.11-3ubuntu1 amd64 [installed]
linux-image-4.4.0-137-generic/xenial-updates,xenial-security,now 4.4.0-137.163
Ok I see what is happening. If you do not specify a gateway the add or
apply button is not active. However if you do add a gateway it works.
The problem is that for the VPN connection specification that I was
given a gateway is not required/provided.
--
You received this bug notification because
If I add the address and range manually in NetworkManager it works fine.
And populates the fields in the Dialog once I reload it. So the bug is
that the gateway value needs to be optional not required.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
VPN dialog snapshot
** Attachment added: "Add button greyed out"
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1829926/+attachment/5265714/+files/screenshot.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Ubuntu 19.04
Gnome 3.32.1
VPN type is Cisco AnyConnect (I do not think this matters)
Yes this is reproducible:
Add new VPN connection with +
Enter name and gateway for new VPN (you do not need to press add)
Go to IPV4 and turn off automatic routes
Enter random IP and netmask.
Public bug reported:
In VPN settings dialog for ipv4 if you add static routes. Apply button
is greyed out and can not apply these changes.
If you add routes manually in /etc/NetworkManager/system-connections
file. These are populated properly in the dialog box for that VPN.
** Affects: network-m
15 matches
Mail list logo
