I tested the resource-agents package from focal-proposed and it fixed it
for me. Marking verification-complete. Logs:
http://paste.ubuntu.com/p/F5yDkV2wKS/
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this
Public bug reported:
On a deploy of kubernetes, we're seeing a machine have issues with its
tg3 driven nics.
We see:
Dec 14 07:44:08 juju-fcf29c-0-lxd-1 kernel: [ 1496.772960] tg3
:02:00.1 eth1: transmit timed out, resetting
Around that time, we have issues with services losing network
conn
We reproduced it again... looking to try the testing now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759445
Title:
kernel panic when trying to reboot in bionic
To manage notifications about thi
So far we've only been able to produce this by doing bionic deploys.
One thing that stands out in the rsyslog for bionic deploys is this
failure:
http://paste.ubuntu.com/p/y8xXc7PYjp/
Apr 2 17:48:35 leafeon blkdeactivate[1782]: /sbin/blkdeactivate: line
345: /bin/sort: No such file or directory
After updating firmware on the servers, we can't reproduce it at all
anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759445
Title:
kernel panic when trying to reboot in bionic
To manage not
Marked as Fix Released on Bionic/Xenial because the SRU for bug 1777912
is done. I can't make Artful "Won't Fix", but it should be.
** Changed in: cloud-init (Ubuntu Xenial)
Status: Confirmed => Fix Released
** Changed in: cloud-init (Ubuntu Bionic)
Status: Confirmed => Fix Released
Public bug reported:
On some deployments of bionic, using maas and juju, my system ends up
not being able to resolve hostnames. This happens inconsistently, it
seems like a race.
systemd-resolve is showing no nameservers
https://pastebin.canonical.com/p/tyFw8TfSxk
rharper had a look at one repro
I've configured our test runs to turn debug logging on for networkd and
resolvd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802355
Title:
systemd-resolve is missing nameservers until interface i
** Tags added: cdo-qa cdo-release-blocker foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812935
Title:
oslo cache mempool issues with python3
To manage notifications about this b
** Description changed:
nova conductor running on a rhel8 host inside f28 based containers hits the
following error:
2019-01-17 13:59:37.049 46 DEBUG oslo_concurrency.lockutils
[req-284f3071-8eee-4dcb-903c-838f2e024b48 40ca1490773f49f791d3a834af3702c8
8671bdf05abf48f58a9bdcdb0ef4b740 - defa
In the previous package removal, we are seeing:
[10.244.40.30] out: Purging configuration files for avahi-daemon
(0.7-3.1ubuntu1.1) ...
[10.244.40.30] out: rmdir: failed to remove '/var/run/avahi-daemon': Directory
not empty
--
You received this bug notification because you are a member of Ubu
Subscribed to field-high as this is causing a lot of failures lately.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792978
Title:
initscript avahi-daemon, action "start" failed
To manage notificat
20:37 < rharper> powersj: jhobbs: re: curtin SRU; I had planned to SRU
in Nov, but the fix that landed at the time was not complete; I was
still able to recreate the failure. We have a more omplete fix that's
passing all of the vmtest scenarios with bcache; that's landed, so
likely SRU will start
I tested with 19.3-787-gb022ed4-0ubuntu1+228~trunk~ubuntu18.04.1 and it
can repeatedly install just fine - no issues with the setup described
above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/184454
This started to affect our solutions-qa test runs yesterday/last night
at some point - we can no longer deploy bionic on uefi systems:
We're not using dkms packages at all; here is the failed install log
from maas:
http://paste.ubuntu.com/p/NVdV4tZvJW/
** Changed in: shim-signed (Ubuntu)
Public bug reported:
Here's the lshw xml output for my node:
https://pastebin.com/pL0A1Y3T
Some disks, for example, /dev/sdd, don't have a serial number listed.
However, the serial number for the disk is available via udevadm:
http://paste.ubuntu.com/24990967/
So, it seems like lshw should be a
** Description changed:
Here's the lshw xml output for my node:
https://pastebin.com/pL0A1Y3T
Some disks, for example, /dev/sdd, don't have a serial number listed.
However, the serial number for the disk is available via udevadm:
http://paste.ubuntu.com/24990967/
- So, it seems
I just tested this also and can verify it fixed it in the
environment/test where it was originally reported as broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737640
Title:
/usr/sbin/fanctl:
Testing on arm64, the workaround of adding xenial-proposed via maas
doesn't work - the newer ubuntu-fan package isn't being installed
http://paste.ubuntu.com/26178859/
I don't know how that can be, since the repo is being added (or should
be added) before juju installs ubuntu-fan.
--
You receiv
I'm running qemu-system-arm 2.10+dfsg-0ubuntu3.1~cloud0 and still seeing
this issue.
** Changed in: libvirt (Ubuntu)
Status: Incomplete => New
** Tags added: cdoqa-blocker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
No - with the hwe-kernel (4.10.0-42-generic from 4.10.0-42.46~16.04.1),
this doesn't happen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706630
Title:
aarch64: MSI is not supported by interrupt c
I got this to work: http://paste.ubuntu.com/p/K8VncJv4vp/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579652
Title:
snap ignores the proxy environment variables
To manage notifications about thi
** Description changed:
After deploying openstack on arm64 using bionic and queens, no
hypervisors show upon. On my compute nodes, I have an error like:
2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError:
Node device not found: no node device with matching name
'ne
The deploy works fine with juju 2.4 beta 2 and xenial/queens.
package versions: http://paste.ubuntu.com/p/PF7Jb7gxnX/
we do see this in nova-compute.log, but it's not fatal:
http://paste.ubuntu.com/p/Dh4ZGVTtH8/
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
given it works with the same libvirt and kernel on 16.04 but not 18.04,
I'm suspicious of netplan here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771662
Title:
libvirtError: Node device not fou
This looks like it is specific to this hardware and the way it does VFs
and PFs, so I'm removing 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/1771662
Title:
libvirtError: Node device no
steve captured what I meant in #8 better than I did: 17:46 < slangasek>
one could as accurately say "I'm suspicious this is related to us
replacing the whole networking stack in Ubuntu" ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
@rharper still working on getting the other stuff you've asked for, but here is
the uname -a output from xenial vs bionic:
http://paste.ubuntu.com/p/rJDpK5SyW9/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
@rharper here are the logs you asked for from the bionic deploy
** Attachment added: "bionic-logs.tgz"
https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+attachment/5140998/+files/bionic-logs.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
all of /var/log and /etc from the bionic deploy.
** Attachment added: "bionic-var-log-and-etc.tgz"
https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+attachment/5141000/+files/bionic-var-log-and-etc.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Christian, thanks for digging in. Yes, I really just setup base
openstack and hit this condition. I'm not doing anything to setup
devices as passthrough or anything along those lines, and I'm not trying
to start instances.
--
You received this bug notification because you are a member of Ubuntu
B
This bug is a kernel panic when rebooting at the end of a MAAS
deployment of bionic; there is no way to run apport-collect.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- Bionic due to kernel panic
+ kernel panic when trying to reboot in bionic
--
Yo
** Tags added: foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759445
Title:
kernel panic when trying to reboot in bionic
To manage notifications about this bug go to:
https://bug
We can no longer reproduce this.
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759445
Title:
kernel panic when trying to r
We're still seeing a bcache timeout failure during curtin install
2019-08-22T10:16:40+00:00 spinda
cloud-init[1604]: finish:
cmd-install/stage-partitioning/builtin/cmd-block-meta/clear-holders: FAIL:
removing previous storage devices
2019-08-22T10:16:40+00:00 spinda cloud-init[1604]:
** Attachment added: "spinda.maas-curtin_config.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5284072/+files/spinda.maas-curtin_config.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784665
Title:
bcache: bch_allocator_thread(): hung task timeout
To manage not
@ Ryan we do not test Xenial or Disco
On Thu, Aug 22, 2019 at 7:41 PM Ryan Harper <1784...@bugs.launchpad.net>
wrote:
> Finally, I did verify xenial proposed with our original test. I had
> over 100 installs with no issue.
>
> @Jason
>
> Have you had any runs on Xenial or Disco? (or do you not
I successfully verified the bionic fix on MAAS. Here's what I did:
1. deployed a machine with a bridge via maas
2. machine went to deployed mode, couldn't ssh in
3. switched to rescue mode, ssh'd in
4. mounted /, captured cloud-init-output.log with error:
http://paste.ubuntu.com/p/Gg53xf9wtZ/
5.
Sub'd ~field-high.
** Also affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- rt #112309: keyserver.ubuntu.com increased failure rates over past few days
+ key retrieval timeouts cause failures
** Description changed:
- keyserver failures mo
** 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/1777512
Title:
key retrieval timeouts cause failures
To manage notifications about this bug go to:
https://bugs.launchpad.net
** Tags added: cdo-qa foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796292
Title:
Tight timeout for bcache removal causes spurious failures
To manage notifications about this bu
** No longer affects: cdoqa-system-tests
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777512
Title:
key retrieval timeouts cause failures
To manage notifications about this bug go to:
https://bug
sub'd to field high; this blocks FCE from working on focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899187
Title:
in python 3.8, ActionAPI.__call__ breaks with "RuntimeError:
dictionary ke
Public bug reported:
See https://github.com/maas/python-libmaas/issues/246
This is fixed upstream and needs to be fixed in Ubuntu too.
** Affects: python-libmaas (Ubuntu)
Importance: Undecided
Assignee: Adam Collard (adam-collard)
Status: New
** Tags: cdo-qa foundations-engi
sub'd to field high; this blocks cleaning in our CI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899822
Title:
hang during purging postgresql-common
To manage notifications about this bug go to:
Public bug reported:
purging postgresql-common on 20.04 results in a hang:
root 269255 0.0 0.0 11004 4672 ?Ss 16:44 0:00 | \_
sudo bash --login -c apt-get -q autoremove --purge postgresql-common -y
root 269256 0.4 0.0 69708 58152 ?S16:44 0:00 |
we were missing DEBIAN_FRONTEND=noninteractive
** Changed in: postgresql-common (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899822
Title:
hang during purgi
Public bug reported:
There is a bug in the resource agent's node_exist function. It looks at
crm_mon output, which has changed between bionic and focal.
The result is that the 'pgsql-status' and 'pgsql-data-status' attributes
are missing from crm status --as-xml output on focal.
Here is the foca
sub'd to field high; this breaks our ability to validate postgres HA on
focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900016
Title:
pgsql resource agent uses regexes for old crm_mon format,
Here they are with regex that accepts either version:
is_node_online() {
print_crm_mon | tr '[A-Z]' '[a-z]' | grep -e "^\( \* \)\?node $1 " -e "^\(
\* \)\?node $1:" | grep -q -v "offline"
}
node_exist() {
print_crm_mon | tr '[A-Z]' '[a-z]' | grep -q "^\( \* \)\?node $1"
}
--
You rec
Bumped to field crit as we don't have a good workaround for this. We
could hotpatch the resource agent, but that only lasts until the package
is updated again, and then crm status output for pgsql will be broken
again.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Dropped back to field-high since we can hotpatch as a workaround,
because there will be no additional package updates that don't contain
this fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900016
Here's crm configure show:
https://paste.ubuntu.com/p/Mqcn7HMzng/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900016
Title:
pgsql resource agent uses regexes for old crm_mon format, breaks
pgs
sub'd to field high, this is affecting sqa release testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890432
Title:
Create subnet is failing under high load with OVN
To manage notifications ab
I can use my configuration for the test case and do the validation, no
problem. Do you need anything from me right now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900016
Title:
pgsql resource ag
Here's my commands and output:
https://paste.ubuntu.com/p/R4f5xX6QPq/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900016
Title:
pgsql resource agent uses regexes for old crm_mon format, breaks
We're not having any issues with the VIP moving when it's supposed to. I
don't really understand what the command you suggested does, but it's not
really relevant to our problem. As you say, the problem is that the xml is
missing the node attributes right after the deployment.
Jason
On Wed, Oct 2
sub'd to field high as this is blocking field high bug 1818113
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880959
Title:
Rules from the policy directory files are not reapplied after changes
to
** Tags added: cdo-qa foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start lxd-bridge.service when MAAS is managing DNS
To manage notifications about this bu
Public bug reported:
A machine in our test lab kernel panic'd during PXE boot from MAAS.
It was running 4.15.0-46-generic #49-Ubuntu
I've attached a screenshot of the call trace.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: cdo-qa foundations-engine
**
I can't get logs from the system because it's kernel panic'd.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
This happens only sporadically. If it happens, is there some keyboard
sequence I can use to dump more information, or is the system totally
frozen at this point?
Jason
On Sat, Mar 16, 2019 at 11:35 AM Kai-Heng Feng
wrote:
> Would it be possible to get earlier trace?
>
> --
> You received this b
1) Testing
2) No, it's in baremetal
3) Attached.
4) The machine was deployed with maas - it's a bionic cloud image. We then
install/configure maas, run some tests, and remove maas via purge, and repeat.
This shows up sometimes on deployments after the initial one - avahi-daemon, or
at least its
Bumped to field-high as we ran into this again in testing.
We have a workaround, but it's to not use 2G VM's, which is really silly
and hard to remember when we go and add new deployments, especially
because the failure mode is not obvious at all.
--
You received this bug notification because yo
@Christian
- release: bionic
- seabios: 1.10.2-1ubuntu1
- qemu: 1:2.11+dfsg-1ubuntu7.10
- libvirt: 4.0.0-1ubuntu8.8
- ovmf - this is a uefi thing right? we're not using it.
- kernel 2019-03-18T12:17:11+00:00 elastic-2 kernel: [0.00]
Linux version 4.15.0-46-generic (buildd@lgw01-amd64-038)
MAAS is installing bind9 and configuring it for its own purposes - it
provides other config for bind, and it's perfectly reasonable to expect
maas to configure it to only listen on interfaces MAAS wants to provide
DNS services on.
** Changed in: maas
Status: Invalid => New
** Tags added: c
This occurrs on a target machine during maas install. Apport is not
collected in this case.
** 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.
https://bugs.launchpad.ne
With the package 1.30.1-0ubuntu1.1 from rocky-proposed in place, I ran
through the test case for this and did not hit any failures. I can
verify this fixes the issue for rocky.
** Tags removed: verification-rocky-needed
** Tags added: verification-rocky-done
--
You received this bug notification
This is difficult for us to test in our lab because we are using MAAS, and
we hit this during MAAS deployments of nodes, so we would need MAAS images
built with these kernels. Additionally, this doesn't reproduce every time,
it is maybe 1/4 test runs. It may be best to find a way to reproduce this
We're still hitting this in LXD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651497
Title:
install Job for iscsid.service failed because a configured resource
limit was exceeded
To manage noti
We're actually seeing iscsi errors show up as soon as the container
starts; I guess the iscsid service never starts properly and so when the
charm does an apt-get install of some unrelated packages, something is
trying to set up that iscsi service and it's failing again.
I've attached logs from a
** Summary changed:
- iscsid.service fails to start in container, results in failed apt-get install
later on
+ iscsid.service fails to start in container, results in failed dist-upgrade on
** Summary changed:
- iscsid.service fails to start in container, results in failed dist-upgrade on
+ iscs
@rharper, here are the logs you requested from the xenial deploy.
** Attachment added: "xenial-logs-1771662.tgz"
https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+attachment/5142976/+files/xenial-logs-1771662.tgz
** Changed in: charm-nova-compute
Status: Invalid => New
** Ch
marked new on nova-compute-charm due to rharper's comment #18, and new
on libvirt because I've posted all the requested logs now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771662
Title:
libvirt
0_" name="/bin/"
> pid=91949 comm="(y-helper)" flags="ro, remount, bind"
>
>
> xenial.log:May 22 15:15:10 aurorus kernel: [ 918.311740] audit:
> type=1400 audit(1527002110.131:109): apparmor="DENIED"
> operation="file_mmap"
Do you really want a tar? How about ls -alR? xenial:
http://paste.ubuntu.com/p/wyQ3kTsyBB/
On Tue, May 22, 2018 at 5:14 PM, Jason Hobbs wrote:
> ok; looks like that 4.15.0-22-generic just released and wasn't what I
> used in the first reproduction... I doubt that's it.
>
>
cd /sys/bus/pci/devices && grep -nr . *
xenial:
http://paste.ubuntu.com/p/F5qyvN2Qrr/
On Tue, May 22, 2018 at 5:27 PM, Jason Hobbs wrote:
> Do you really want a tar? How about ls -alR? xenial:
>
> http://paste.ubuntu.com/p/wyQ3kTsyBB/
>
> On Tue, May 22, 2018 at 5:14 PM
gt; Looks like the ls -aLR contains more data; we can compare bionic.
>
> On Tue, May 22, 2018 at 6:53 PM, Jason Hobbs
> wrote:
>> cd /sys/bus/pci/devices && grep -nr . *
>>
>> xenial:
>> http://paste.ubuntu.com/p/F5qyvN2Qrr/
>>
>> On Tue, May
*** This bug is a duplicate of bug 1768893 ***
https://bugs.launchpad.net/bugs/1768893
** This bug has been marked a duplicate of bug 1768893
installation on several nodes failed with errors relating to dmsetup remove
of ceph devices.
--
You received this bug notification because you are
** Tags added: cdo-qa foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607345
Title:
Collect all logs needed to debug curtin/cloud-init for each deployment
To manage notifications
After testing with the new version of the charm, we're not seeing this
anymore. Looks fixed to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772947
Title:
You have enabled the binary log, but y
We are seeing this in our test runs as well.
** Tags added: cdo-qa foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774666
Title:
Bond interfaces stuck at 1500 MTU on Bionic
To ma
Subscribed to Canonical Field High SLA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774666
Title:
Bond interfaces stuck at 1500 MTU on Bionic
To manage notifications about this bug go to:
https:
This is causing test failures for us, because containers deployed by
juju that are bound to a space that sits on top of the bond have the
corrent mtu (9000) but the bond's mtu is stuck at (1500), so packets are
being dropped.
curtin config for the machine:
http://paste.ubuntu.com/p/8tMR2YBGYm/
cl
Is there a workaround for this? I can just rm /etc/resolv.conf and
create it with the contents I want, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750884
Title:
[2.4, bionic] /etc/resolv.c
Ok, that's not much of a workaround then :).
On Thu, Mar 8, 2018 at 3:52 AM, Dan Watkins
wrote:
> On Wed, Mar 07, 2018 at 11:42:29PM -0000, Jason Hobbs wrote:
>> Is there a workaround for this? I can just rm /etc/resolv.conf and
>> create it with the contents I want, ri
We're also seeing this in OIL. The dashboard takes so long to load
sometimes that the browser times out.
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664764
Title:
ARM Opentac
We hit this doing an apt update in a lxd container:
http://paste.ubuntu.com/25233711/
** Tags added: cdo-qa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651497
Title:
install Job for iscsid.servi
** Tags added: foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699161
Title:
lshw crashes with SEGV in privileged containers
To manage notifications about this bug go to:
https://
** Tags added: cdo-qa foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701720
Title:
lshw output is missing serial numbers for disks
To manage notifications about this bug go to:
h
** Tags added: foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705064
Title:
lshw doesn't have logicalname, serial number, or size for nvme device
To manage notifications about t
** Description changed:
There is an nvme device on my system, at PCI::05:00.0.
Here is the lshw output:
https://pastebin.com/9t7Pj2pH
There is no 'logicalname', 'serial', or 'size' field given for the
device.
lsblk output includes all of that info:
https://pastebin.co
On Mon, Feb 5, 2018 at 11:58 AM, Andres Rodriguez
wrote:
> No new data was provided to mark this New in MAAS:
>
> 1. Changes to the storage seem to have improved things
Yes, it has. That doesn't change whether or not there is a bug in
MAAS. Can you please address the critical log errors that I
@Steve - I don't think it helps with the problem of MAAS taking a long
time to respond to the grub.cfg request. However, it may help with the
part of this bug where grub is hitting an error and asking for keyboard
input. https://imgur.com/a/as8Sx
Maybe that should be a separate bug? It seems li
The packetdump (comment #35) of MAAS not responding to grub's request
for the mac specific grub.cfg before grub times out, and then responding
immediately to the generic-amd64 grub cfg, clearly shows a race
condition in MAAS.
MAAS's design of dynamically generating the interface specific grub
conf
ieu...@gmail.com;
>> Launchpad-Bug-Tags: cdo-qa cdo-qa-blocker foundations-engine patch
>> Launchpad-Bug-Information-Type: Public
>> Launchpad-Bug-Private: no
>> Launchpad-Bug-Security-Vulnerability: no
>> Launchpad-Bug-Commenters: andreserl blake-rouse cgregan jason-h
On Mon, Feb 5, 2018 at 3:27 PM, Andres Rodriguez
wrote:
> @Jason,
>
>
> On Mon, Feb 5, 2018 at 3:38 PM, Jason Hobbs
> wrote:
>
>> On Mon, Feb 5, 2018 at 11:58 AM, Andres Rodriguez
>> wrote:
>> > No new data was provided to mark this New in MAAS:
>>
On Mon, Feb 5, 2018 at 3:45 PM, Andres Rodriguez
wrote:
> @Jason,
>
> On Mon, Feb 5, 2018 at 3:38 PM, Jason Hobbs
> wrote:
>
>> On Mon, Feb 5, 2018 at 11:58 AM, Andres Rodriguez
>> wrote:
>> > No new data was provided to mark this New in MAAS:
>> >
@Mike, you can see the stacked response behavior in
https://bugs.launchpad.net/maas/+bug/1743249/+attachment/5046952/+files/spearow-fall-back-to-default-amd64.pcap
You can tell packet 90573 is a response to the requests for
grub.cfg- because its destination port (25305) is the src port
the request
1 - 100 of 229 matches
Mail list logo
