Subscribing field medium to represent the issue this now causes with
landscape per-AZ upgrades
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859649
Title:
networking disruption on upgrade from
Public bug reported:
I've filed with ubuntu-bug so additional logging should be available.
Starting with 19.10 there has been a regression in my CalDigit
thunderbolt 3 dock. With Bionic and Disco the dock has been stable
across two laptops. After upgrading to Eaon and running 5.3.0-18-generic
** Changed in: charm-neutron-openvswitch
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Subscribing field-high which wasn't carried over from the other
duplicate bug https://bugs.launchpad.net/keystone/+bug/1832766
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782922
Title:
LDAP:
requested logging during the month of the error
** Attachment added: "unattended-upgrades.log.1"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+attachment/5261355/+files/unattended-upgrades.log.1
--
You received this bug notification because you are a member of Ubuntu
Bugs,
dpk logging from the same time period
** Attachment added: "unattended-upgrades-dpkg.log.1"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+attachment/5261356/+files/unattended-upgrades-dpkg.log.1
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@rbalint I've included the logs but I don't see any Traces as mentioned
in LP: #1824341
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826916
Title:
MAAS uninstalls itself on unattended upgrade
To
I've reinstalled with: sudo apt install maas -o
debug::pkgproblemresolver=true 2>&1 | tee install.log
As the attached log shows there were no errors, clean install.
After following the restore and restarting the services juju returned the
following error:
ERROR opening environment: unexpected:
That's all relevant logs I could think of, when I am able to do a
reinstall I'll include the above recommended debug option as well. If
there's something I didn't think of let me know and I'll provide that as
well.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
attached apt history.log
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+attachment/5260156/+files/history.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached dpkg.log
** Attachment added: "dpkg.log"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+attachment/5260154/+files/dpkg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
attached apt term.log
** Attachment added: "term.log"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+attachment/5260155/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Having recently found my MAAS unresponsive I was surprised to find out
it's because it uninstalled itself. First, how on earth does this
happen, and second how do I go about recovering this I have several
critical juju services deployed on a nodes that this MAAS runs and juju
Public bug reported:
The --H, --auto-hosts option does not currently include fqdn and in fact
removes the fqdn entries. This is blocking the use of sshuttle for
things like accessing a Graylog server which links back to itself via
fqdn.
This has been fixed with pull request #173 [0] in Oct of
I've subscribed Canonical Field Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749425
Title:
Neutron integrated with OpenVSwitch drops packets and fails to
plug/unplug interfaces from
The machine I was using has been redeployed without LVM. If I get a
chance to redeploy I'll grab the requested logs. It's fairly trivial to
trigger if you have a machine available to deploy with lvm boot as
described above.
--
You received this bug notification because you are a member of Ubuntu
** Package changed: maas (Ubuntu) => maas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573982
Title:
LVM boot problem - volumes not activated after upgrade to Xenial
To manage notifications
I've run across this today and it affects MAAS.
MAAS version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1)
Configuring an LVM based drive with a raid on top of it for the root
partition will trigger this. Deploying the default kernel / OS will fail
due to inactive volume groups.
The fix as expected:
** Also affects: linux-meta-hwe (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-meta-hwe (Ubuntu)
** No longer affects: linux-meta-hwe (Ubuntu Yakkety)
** No longer affects: linux-meta-hwe (Ubuntu Zesty)
--
You received this bug notification because you are a
Great, this should fix it for you then. I ran between 40 min and 3 hours
between crashes. I've been running daily (this is my daily use laptop
for work) and after the above fix it's completely stable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Javi, see comment 25 above I'm booting with a work around on the 9550 with
PM951.
However, also note that this bug shouldn't crash "on boot". I had a seperate
issue with the 9550 with tlp and external usb devices causing an on boot crash
which is not related to this. I recommend you run w/o any
Nils, from above use 'nvme-core.nvme_core.default_ps_max_latency_us=0'
to turn APST off.
That as my first step to confirm this is indeed related to APST and the
same bug. If that doesn't do it, I'm afraid you might have another
issue.
--
You received this bug notification because you are a
I can now confirm that I've had a stable machine for more than 7 hours
using 6k for latency. I think the longest I had with out the option was
~3 hours and generally it was ~45 minutes to crash.
Nils, I'm setting the parameter in /etc/default/grub by appending it to
the
I have an xps15 9550 same as above, same controller, same issue. I set
nvme_core.default_ps_max_latency_us=6000 this morning and have ~1 hour
right now with no crash. I'll continue to run it today and report back.
The only issue I have seen with the 6k setting which I didn't not see
with a
I've just noticed this has resolved for me. See below, the errors do not
repeat and I connect to the network. However, I have recently updated my
router firmware to my knowledge it's still configured like it was (40/80
Mhz channels). I'm running the same nvidia-375 that was causing errors
before.
This appears to be a conflict with the Nvidia driver (at least for me).
I've tried:
nvidia-378 (open source)
nvidia-370 (open source)
nvidia-375 (proprietary)
All three give the exact same results as above on both 2.4 and 5 Ghz.
Switching to the intel graphics driver completely clears this up.
XPS-15 (9550), Yakkety, 4.8.0-41-generic, 40Mhz channels also unable to
connect to Wifi any longer. Happy to provide testing or any additional
information.
dmesg | grep brcm
[5.481593] usbcore: registered new interface driver brcmfmac
[5.481639] brcmfmac :02:00.0: enabling device
27 matches
Mail list logo
