Hi,
I recreated the issue using the Ubuntu upstream kernel builds at
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
After launching a 18.04 instance, and then installing those kernels
and rebooting (generic_4.20.0-999.201811252100) I saw the issue.
I noticed that cloud-init's
Hi Adrian,
In a system where this recreates, could you please run:
cloud-init collect-logs
and attach the output?
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/1803173
Title:
Hi.
I added a 'linux' package task here. It seems that in bug 1551419 patches were
added
to the ubuntu kernel to do the right thing. Possibly those patches were
inadvertantly
dropped? Either way, it seems like the [Ubuntu] kernel should promise this
consistently
so that multiple consumers do
** Description changed:
=== Begin SRU Template ===
[Impact]
A previous change to open-iscsi made under bug 1755858 caused a regression
- that is seen when a system has only a single iscsi mount that was made
+ that is seen when a system has only a iscsi mounts that were made
in the
** Description changed:
=== Begin SRU Template ===
- [Impact]
+ [Impact]
A previous change to open-iscsi made under bug 1755858 caused a regression
that is seen when a system has only a single iscsi mount that was made
in the initramfs. The most likely scenario would be iscsi root.
.
If no image was available for a release, a NameError exception would be
raised.
-- Scott Moser Wed, 14 Nov 2018 16:50:29 -0500
open-iscsi (2.0.874-5ubuntu10) disco; urgency=medium
* d/iscsi-disk.rules, d/tests: Add a udev rule so that iscsid.service
will be run when udev disks
** Changed in: livecd-rootfs (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803162
Title:
non-dpkg information and broken format in manifest
To manage
> No, that's not how it works.
I'm not sure I know what you were referring to.
Can you give a single justification for breaking existing consumers of a
deliverable?
I do not see justification anywhere. Not in the commit message [1], the
merge proposal [2] or any of the comments here. This is
It is a bug to change content in backwards incompatible ways. livecd-
rootfs produced an artifact that is indexed with known-content. A
change broke consumers of that content. Thats a regression.
Pretending otherwise is wasting both of our time.
I pointed at one known consumer (owned by the
@Steve,
"We have never represented the .manifest to be a public machine-parseable
interface."
Thats clearly not true. Machine-formatted content (the .manifest)
advertised in a machine-formatted index (streams) is quite reasonable to
be expected to be machine parseable.
One example of something
Public bug reported:
Ubuntu images have been accompanied by a 'manifest' file since at least 10.04.
This manifest file was a list of the dpkg installed packages and their versions.
The format was as output by dpkg-query --show.
That format was
package-nameversion
The offending change was added
in IRC, xnox suggested a SYSTEMD_WANTS as a udev rule.
I'm looking at that solution.
https://irclogs.ubuntu.com/2018/11/09/%23ubuntu-devel.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802354
@Steve,
That feels overly indirect.
If open-iscsi.service (or anything) knows that iscsid should be running,
then why be sly?
Thats essentially what we were trying to do, and in some cases it didn't
work. Starting a persistent daemon by requesting to list the current
sessions seems like an
The goal here should be simple.
If there are iscsi sessions, then iscsid should be started/running.
You can tell if there are iscsi sessions by either:
- 'iscsiadm --mode=session' exits 0
- /sys/class/iscsi_session is non-empty.
The current open-iscsi.service implementation will not result in
** Description changed:
It was reported that after the changes made in bug 1755858, the iscsid
service was not running when initramfs (via iscsi_* params or iBft)
set up an iscsi mount.
This seems to not be a problem until there is a restart of the iscsi
*host* service or some other
** Description changed:
[Impact]
* Service is running uselessly which is consuming a few cycles/memory as
well as raising general concerns e.g. on minimizing attack surface of
a system.
* This is also the only service in a default server install which pulls
in the
** Changed in: open-iscsi (Ubuntu)
Importance: Undecided => High
** Changed in: open-iscsi (Ubuntu)
Status: New => Confirmed
** Changed in: open-iscsi (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member
Public bug reported:
It was reported that after the changes made in bug 1755858, the iscsid
service was not running when initramfs (via iscsi_* params or iBft)
set up an iscsi mount.
This seems to not be a problem until there is a restart of the iscsi
*host* service or some other hiccup. Thus,
Marking this Invalid on cloud-initramfs-tools. It doesn't seem likely
that there is much we can do there.
** Changed in: cloud-initramfs-tools
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-initramfs-tools
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689642
Title:
cloud-initramfs-rooturl should manual_add_modules
I just now realized that this issue only occurs when the window is on my
"second" monitor.
If move the window to the primary display then the window menu has
Minimize, Maximize, Move, Resize, Always on Top, Always on Visible
Workspace, Move Workspace Down, Move to Monitor Right, Close
But on
** Summary changed:
- sru curtin 2018-10-02 - 18.1-55-g0a27f283
+ sru curtin 2018-10-02 - 18.1-59-g0f993084
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795712
Title:
sru curtin 2018-10-02 -
With regard to wiping all prep partitions...
We do have code that does this in helpers/pt_prep. Ie, the non-storage config
path does this.
However, this is kind of a grey line here. If maas wants a partition wiped,
then MAAS should send config that says it should be wiped.
If we bake in
** Merge proposal linked:
https://code.launchpad.net/~thedac/simplestreams/+git/simplestreams/+merge/354369
** Changed in: simplestreams
Status: New => Confirmed
** Changed in: simplestreams
Importance: Undecided => Medium
** Changed in: simplestreams
Assignee: (unassigned)
** Changed in: cloud-init
Status: Incomplete => Invalid
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799954
Title:
Hi Sandro,
It looks like the version of nova-lxd that is in 16.04 is currently
13.3.0-ubuntu1. That version has the fix for bug 1661797 included.
You did mention that you're running 13.1.3-0ubuntu1 so your environment
definitely will not have the fix.
So above, 'b' is already done, meaning
(in 'c' I typoed. The bug referenced should have been bug 1661797).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799954
Title:
cloud-init fails openstack detection from openstack lxd virtual
Hi,
I *do* want to fix cloud-init to accept your specific configuration
of openstack datasource. The plan is to fix that under bug 1788487.
I think you're suggesting that you are running nova-lxd as your
platform. Is that correct?
We have a couple options then to fix this:
a.) cloud-init fix
@xnox, @blackboxsw,
I've updated the summary.
We were still waiting on solutions QA response.
I've talked to John George and he hopes to get to that today.
** Description changed:
== Begin SRU Template ==
[Updates 10/17/2018]
SRU regression in behavior found on Xenial(Azure) which
marking this as 'fix-released' on xenial, it is not a problem there as
there is a 'zfs' (virtual) package
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status: New => Confirmed
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
** Description changed:
I was attempting to run growpart when booting off of a RAID device and
noticed that growpart never grows the root partition properly.
During boot, I get the message:
GROWROOT: FAILED: /dev/md126p: does not exist
I then modified the "growroot" wrapper
this is fixed in cloud-utils 0.30
** Changed in: cloud-utils
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604011
Title:
mount-image-callback getopt
fixed in 0.30
** Changed in: cloud-utils
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593451
Title:
ubuntu-cloudimg-query does not return xenial ami
this fix is present in cloud-utils 0.30
** Changed in: cloud-utils
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493188
Title:
"overlayfs" no longer
** Changed in: cloud-utils
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715994
Title:
mount-image-callback lxd: is broken with lxd 2.17
To manage
** Changed in: cloud-utils
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619285
Title:
cc_growpart fails on yakkety
To manage notifications about this
Public bug reported:
== Short summary ==
In lxd containers launched by juju,
/var/lib/cloud/seed/nocloud-net/network-config has:
has:
network:
config: disabled
That is invalid content. Cloud-init assumes content in 'network-config'
is already namespaced to 'network'. The correct content
@Pengpeng,
Looking at the logs, the core of the issue seems to be the error in journal.txt
and
cloud-init-output.log:
IsADirectoryError: [Errno 21] Is a directory: '/var/lib/cloud/instance'
I'm not really sure how that got that way.
I had seen a bug like this before but have never been able
** Description changed:
This is a new version of snapd.
The changelog is available here
https://github.com/snapcore/snapd/blob/2.35/packaging/ubuntu-16.04/changelog,
the raw git changelog is available here:
https://github.com/snapcore/snapd/commits/2.35 (note that the debian
This is reported fixed in snapd 2.35.5+18.10 which was uploaded under
SRU bug 1786438.
** Changed in: snapd (Ubuntu)
Status: Confirmed => Fix Committed
** Description changed:
# Summary
snap confinement fails on top of overlayroot
-
# Steps to reproduce:
These steps
Hi,
There is more information on a SRU of simplestreams in bug 1686437.
https://bugs.launchpad.net/simplestreams/+bug/1686437/comments/11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611987
Title:
lots of discussion in irc
https://irclogs.ubuntu.com/2018/10/12/%23snappy.html#t13:49
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797218
Title:
snap confine fails on top of overlayroot
To
Just as information to put here. A change to overlayroot like below
actually does make the /proc//mountinfo table in line with what
snapd is expecting. I've verified that such an initramfs does have
snaps seemingly working.
--- /usr/share/initramfs-tools/scripts/init-bottom/overlayroot.dist
** Summary changed:
- boot hangs in curtin vmtest
+ snap confine fails on top of overlayroot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797218
Title:
snap confine fails on top of overlayroot
'c' above can also be: 'sudo snap install'
There, the install wont complain or fail, but running 'hello' will.
$ sudo snap install hello
2018-10-11T17:54:21Z INFO Waiting for restart...
hello 2.10 from 'canonical' installed
$ echo $?
0
$ hello
cannot create lock directory /run/snapd/lock:
In another re-create scenario, you can see this fail on bionic.
a.) launch bionic image somewhere
b.) sudo sh -xc 'echo overlayroot=tmpfs > /etc/overlayroot.local.conf && reboot'
c.) $ sudo snap install lxd
2018-10-11T17:44:22Z INFO Waiting for restart...
error: cannot perform the following tasks:
After above recreate, you can login on console as 'root' with
'passw0rd'.
You'll then see the system is still 'starting' (per systemctl status)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797218
Heres an even easier re-create
$
url=http://cloud-images.ubuntu.com/cosmic/current/cosmic-server-cloudimg-amd64.img
$ img=${url##*/}
$ wget "${url}" -O "$img"
$ sudo mount-image-callback "$img" -- \
mchroot sh -xc 'echo overlayroot=tmpfs > $1 && echo root:$2 | chpasswd' \
setup-image
(installation via maas)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797218
Title:
boot hangs in curtin vmtest
To manage notifications about this bug go to:
I am attempting to verify if installation of 18.10 is similarly broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797218
Title:
boot hangs in curtin vmtest
To manage notifications about this
I noticed that the seeding of snaps in the cloud image also caused regression
of the open-iscsi test [1] as seen from [2].
If anyone wants to debug this the open-iscsi test case provides doc on
how to run it at [3] and I have a gist on it at [4].
Alternatively you can use uvt-kvm or multipass or
$ snap changes
ID Status Spawn Ready Summary
1Error today at 19:46 UTC today at 19:47 UTC Initialize system state
2Donetoday at 19:46 UTC today at 19:46 UTC Initialize device
3Error today at 19:52 UTC today at 19:52 UTC Initialize system
$ for service in $(cd /lib/systemd/system && ls snap*); do echo $service
=; systemctl status --no-pager --full $service; done 2>&1 | pastebinit
http://paste.ubuntu.com/p/57W9QnXwfQ/
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Changed in: snapd (Ubuntu)
$ systemctl status snapd --no-pager --full
● snapd.service - Snappy daemon
Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset:
enabled)
Active: active (running) since Wed 2018-10-10 19:47:19 UTC; 44s ago
Main PID: 1960 (snapd)
Tasks: 11 (limit: 1105)
Memory:
Jenkins jobs that run this are archived at
https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-amd64/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797218
Title:
boot hangs in curtin vmtest
Public bug reported:
$ cat /etc/cloud/build.info
build_name: server
serial: 20181010
$ dpkg-query --show | pastebinit
http://paste.ubuntu.com/p/KpwSzBdZkw/
The above system hangs on boot. This is seen in curtin's vmtest.
The last success was with image 20180926.
The console log ends up
Well, after an upgrade and reboot (including mutter 3.30.1-1), 'alt
space' now works to bring up the m enu.
However, there is no 'Always on visible workspace' option.
So I will close this bug as 'fix released' and I have opened bug
1797120.
** Changed in: mutter (Ubuntu)
Status: New =>
Public bug reported:
I filed bug 1795410 a few weeks ago complaining that the 'alt space'
didn't bring up the window menu. That is now fixed (seemingly likely
with mutter 3.3.0-6).
However, the window menu that does come up does not have an entry for
'Always on visible workspace' as it used to.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Public bug reported:
our vmtest proposed tests failed here
https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-amd64-proposed/16/console
those essentially get run like
+ ./tools/jenkins-runner -p4
CURTIN_VMTEST_ADD_REPOS=proposed
CURTIN_VMTEST_CURTIN_EXE_VERSION=18.1-56-g3aafe77d
Hi,
Can you please attach the .tar.gz file created by
cloud-init collect-logs
in success and failure cases.
Also, please include the open-vm-tools version in both.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
when you've provided that input, set the status back to 'New'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796875
Title:
cloud-init and cloud-init-local services boot sequence does not obey
@Adam,
> See the comment on the linked debian-cd MP from Marc Deslauriers. Note
> that the goal of removing the cloud-image seed is still entirely
> reasonable and doable, openssh-server should just move to livecd-rootfs
> as something always added to cloud images. Done and done. There's no
Your
Just as a point of reference, a single container booted on the same system I
showed the 38 second boot time before, seems to be down to 25 or so now.
Much better, but still not 10 seconds as it was.
Note that I don't call this a scientific test. I've made no real effort to
control the
Bah. my comment 8 above is wrong.
I meant to reference bug 1796165 (seeded snaps never cleaned up.)
That could affect boot time of subsequent boots, if snapd is re-reading those
preseed snaps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Stgraber,
I'm not sure why you wouldnt' have just done this yourself, so maybe I'm
missing your request.
$ lxc init ubuntu-daily:cosmic my-test
Creating my-test
$ lxc file pull my-test/etc/nsswitch.conf - | pastebinit
http://paste.ubuntu.com/p/7rpZ2N4grn/
$ lxc start my-test
$ lxc exec my-test
repeat boots could I guess be slow as a result of bug 1786165.
The snaps that are seeded are never removed. perhaps snapd doesn't realize (or
has to re-check) to verify that they are not new.
I'd suggest debugging and re-create in lxd itself.
Doing so allows you to jump into the container before
** Changed in: cloud-init
Assignee: (unassigned) => Scott Moser (smoser)
** Changed in: cloud-init
Status: Confirmed => In Progress
** Changed in: apt-setup (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: apt-setup (Ubuntu Bionic)
Importance: Undecided
This bug is fixed in cosmic.
This bug was fixed in the package cloud-init - 18.4-0ubuntu1
---
cloud-init (18.4-0ubuntu1) cosmic; urgency=medium
* New upstream release.
- release 18.4 (LP: #1795741)
- tests: allow skipping an entire cloud_test without running.
-
This is fixed in Ubuntu 18.10.
cloud-init (18.3-46-gbb60f61b-0ubuntu1) cosmic; urgency=medium
* New upstream snapshot.
- ds-identify: doc string cleanup.
- OpenStack: Support setting mac address on bond. [Fabian Wiesel]
-- Ryan Harper Fri, 14 Sep 2018 16:13:19
-0500
** Also
This bug was fixed in
This bug was fixed in the package cloud-init - 18.4-0ubuntu1
---
cloud-init (18.4-0ubuntu1) cosmic; urgency=medium
* New upstream release.
- release 18.4 (LP: #1795741)
- tests: allow skipping an entire cloud_test without running.
- tests:
This is fixed in Ubuntu 18.10.
This bug was fixed in the package cloud-init - 18.4-0ubuntu1
---
cloud-init (18.4-0ubuntu1) cosmic; urgency=medium
* New upstream release.
- release 18.4 (LP: #1795741)
- tests: allow skipping an entire cloud_test without running.
-
This bug is fixed in 18.10
This bug was fixed in the package cloud-init - 18.4-0ubuntu1
---
cloud-init (18.4-0ubuntu1) cosmic; urgency=medium
* New upstream release.
- release 18.4 (LP: #1795741)
- tests: allow skipping an entire cloud_test without running.
-
This bug was fixed in the package cloud-init - 18.4-0ubuntu1
---
cloud-init (18.4-0ubuntu1) cosmic; urgency=medium
* New upstream release.
- release 18.4 (LP: #1795741)
- tests: allow skipping an entire cloud_test without running.
- tests: disable lxd tests on
This bug was fixed in the package cloud-init - 18.4-0ubuntu1
---
cloud-init (18.4-0ubuntu1) cosmic; urgency=medium
* New upstream release.
- release 18.4 (LP: #1795741)
- tests: allow skipping an entire cloud_test without running.
- tests: disable lxd tests on
This bug is believed to be fixed in cloud-init in version 18.4. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.4. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.4. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.4. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.4. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.4. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.4. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
Public bug reported:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these improvements.
The notable ones are:
- Enable custom storage configuration for centos images
-
I've marked this verification-done-bionic based on the fix in
cloud-initramfs-tools.
I'm not sure what the right tag-status is to indicate that the livecd-rootfs
change has not actually been verified.
Anyone who feels motivated can fix that, just please justify.
--
You received this bug
verified cloud-initramfs-tools in bionic. see attached.
** Attachment added: "log of verification of cloud-initramfs-tools fix in
bionic"
https://bugs.launchpad.net/ubuntu/xenial/+source/cloud-initramfs-tools/+bug/1792905/+attachment/5195945/+files/1792905-copymods-bionic-verify.log
**
I've verified the cloud-initramfs-tools fix (cloud-initramfms-copymods)
is in place in xenial, see attached.
** Attachment added: "log of verification of cloud-initramfs-tools fix in
xenial."
Here is my verification of bionic proposed.
It should be considered in cooperation with open-iscsi dep8 tests
which do a iscsi root boot:
http://autopkgtest.ubuntu.com/packages/o/open-iscsi/bionic/amd64
Below is sufficient for the 'Test Case' section of the SRU Template,
it would be nice to see
For the cloud-initramfs-tools upload, I'm provding the following as a SRU
template.
Rather than updating the description above.
=== Begin SRU Tempate cloud-initramfs-tools ===
[Impact]
The designed purpose of cloud-initramfs-copymods is to copy modules
from the initramfs to /lib/modules/ if
** Summary changed:
- iptables --list --numeric fails on -virtual kernel
+ iptables --list --numeric fails on -virtual kernel / -virtual missing bpfilter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Chris,
For what its worth, there is a process to build maas images with -proposed
enabled at
https://gist.github.com/smoser/8a34b1713badb643dee3a25e5cf134b8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As a work around, I just configured some short cut (super w) to 'Toggle
window on all workspaces or one' in the gnome-control-center and that
seems to function.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I'm accustomed to hitting 'alt-space' to 'Activate the window menu'
where there are options like 'Always on Top' or 'Always on visible
workspace'.
After an upgrade today I can no longer bring up that menu.
Alt-space simply does nothing. Configuring the keyboard shortcut in
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
The module needed to magically make this work is 'bpfilter.ko'.
So at least one solution for this is to move bpfilter.ko from
the linux-modules-extra to linux-modules.
Currently linux-modules-extra-4.18.0-7-generic but we would want it
in linux-modules-4.18.0-7-generic.
bpfilter is described
Originally ran into this trying to use lxd on cosmic as described in
https://github.com/lxc/lxd/issues/5081
Simple test case was just:
a.) launch fresh cosmic instance
b.) sudo snap install lxd
c.) sudo lxd waitready
d.) sudo lxd init --auto --storage-backend=dir
In the failure case, that
Public bug reported:
On a fresh instance of cosmic, run:
$ sudo iptables --list --numeric; echo $?
iptables: No chain/target/match by that name.
1
Expected result is something like:
$ iptables --list --numeric
Chain INPUT (policy ACCEPT)
target prot opt source destination
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671951
This is still broken in bionic images 20180927.
I realize it is just 'fix committed', but we really need the fix.
customer MAAS deployments are delayed by ~90 seconds in the best case scenario
and will fail installation in other cases.
What all needs to happen to get an updated bionic image with
Hm...
Our tests show that this is not fixed in cosmic or bionic.
https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-amd64/533/console
shows curtin's vmtest failing. Partial output shows:
==
ERROR:
I uploaded to
* cosmic 0.43ubuntu1
* xenial 0.27ubuntu1.5
* bionic 0.40ubuntu1.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792905
Title:
[2.5] iSCSI systemd services fails and blocks for
201 - 300 of 11836 matches
Mail list logo
