** Merge proposal linked:
https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/+merge/379177
** Changed in: cloud-utils
Status: New => Fix Committed
** Also affects: cloud-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-utils (Ubuntu)
** Changed in: cloud-images
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/1770395
Title:
lxd missing dependency on iproute2
To manage notifications about this bug go
** Also affects: flash-kernel (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/1863145
Title:
arm64 cloud image contains flash-kernel which leads
Also verified here.
Thanks for doing this Dannf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858458
Title:
remove assumption of lp chroot extension
To manage notifications about this bug go to:
This bug is fixed in the 5.8 release.
** Changed in: ssh-import-id
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/1770305
Title:
ssh-import-id
This bug is fixed in the 5.8 release.
** Changed in: ssh-import-id
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/1770302
Title:
ssh-import-id
> If someone manually installs Ubuntu Desktop / Server using an installer,
> one should not be installing or using cloud-init as clearly, it will never
> complete without a correct metadata source present. And when it fails to
> complete, it re-attempts to reprovision the machine on every boot.
For what its worth, see bug 1669875.
Specifically see comment 7
https://bugs.launchpad.net/cloud-init/+bug/1669875/comments/7 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855458
Title:
Hi.
Please attach the output of 'cloud-init collect-logs'. Ideally from the 18.04
instance, but the 16.04 instance would be fine if you're not able to get it
from 18.04.
Then, set the status of this bug back to New.
thanks.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
> > So that means we have this sequence of events:
> > a.) growpart change partition table
> > b.) growpart call partx
> > c.) udev created and events being processed
> That is not true. whilst sfdisk is deleting, creating, finishing
> partition table (a) and partx is called (b), udev events
I really think you are all *way* over thinking this.
a. growpart made a change to the partition table (using sfdisk)
b. growpart called partx --update --nr 3 /dev/sda
c. growpart exited
With a and b growpart created udev events. If you create udev events,
you really need to wait for those
Public bug reported:
The open-iscsi tests have been failing for focal.
https://autopkgtest.ubuntu.com/packages/open-iscsi/focal/amd64 .
Since 2019-10-29, the failure cases have had the following error path:
scsi host3: iSCSI Initiator over TCP/IP
session1: session recovery timed out after
** Changed in: cloud-utils
Status: Triaged => 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/1850257
Title:
cloud-utils-euca depends on euca2ools which is python2-only and
** Also affects: cloud-utils
Importance: Undecided
Status: New
** Changed in: cloud-utils
Status: New => Triaged
** Changed in: cloud-utils
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The intent of the template files is that they *can* be user editable.
For example:
# head /etc/cloud/templates/sources.list.ubuntu.tmpl
## template:jinja
## Note, this file is written by cloud-init on first boot of an instance
## modifications made here will not survive a re-bundle.
## if you
best. fix. ever.
working after a reboot.
$ snap list lxd
Name Version RevTracking Publisher Notes
lxd 3.18 12211 stablecanonical✓ -
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't love the idea of two passes on adding users/groups.
https://stackoverflow.com/questions/57605982/how-to-make-a-custom-gid-in-groupadd-cloud-init
has an idea for another solution. sort of.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Rafael's comment matches my memory, and also my comment in the merge
proposal at
https://code.launchpad.net/~smoser/ubuntu/+source/simplestreams/+git/simplestreams/+merge/341214
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-utils
Status: Confirmed => Fix Committed
** Changed in: cloud-utils (Ubuntu)
Status: New => In Progress
** Changed in: cloud-utils (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is actually *only* in disco-proposed.
No where else.
** Changed in: cloud-utils
Status: New => Confirmed
** Changed in: cloud-utils
Importance: Undecided => High
** Also affects: cloud-utils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
The excuses page linked in comment 15 lists a test failure that is a
regression of the change for this bug.
I've filed bug 1842682 and put up a pull request to fix that logic
error.
** Description changed:
[Impact]
- * DEP8 race condition for ppc64el (LP: #1836593): intermittent
+ *
Corey, simplestreams-dev
My thoughts here have a primary goal to educate the audience on the use cases
and users as I know them for simplestreams. That would then allow the teams
involved make an educated decision on how to handle python 2 support.
I do not personally have any need for python2.
If there is a race, or a need to wait, it almost certainly is in cloud-
utils (growpart). If you use growpart to grow a partition, the result
should be that that is done, and it is ready. The caller should not
expect that they have to know additional information (to call 'udevadm
settle') or
** Also affects: cloud-utils
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/1834875
Title:
cloud-init growpart race with udev
To manage notifications
Seems related or at least "close to" bug 1762748.
If nothing else, that bug has nice local recreate information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840686
Title:
Xenial images won't
This is just a comment from a mostly uninterested third party, so take
it for what you will.
It sure seems to me that it makes more sense to make 'ubuntu-drivers'
take a '--accept-license' flag than to make cloud-init know some
seemingly arbitrary wizardry about writing "latelink=true" to a file
It'd be nice if cloud-init doc could somehow host the "full example".
Perhaps it would be possible to add the files that are in
smoser.brickies.net to cloud-init doc and then update the doc to
reference their https://git.launchpad/ urls.
On Sun, Jul 28, 2019 at 11:25 PM Tim McNamara
cloud-init does not write to syslog by default because it wants to
allow the user to configure rsyslog. second difference/tidyness thing
is that /var/log/cloud-init.log contains DEBUG output. I does not
feel proper to me to have debug output written to syslog (or journal)
by default.
cloud-init
Public bug reported:
MTU values get lost in translation when input is netplan (v2 yaml).
I'm attaching a recreate script, but basically the mtu setting gets lost
when writing ENI or sysconfig if the input is v2 yaml.
input of:
version: 2
vlans:
bond0.1000:
addresses:
output of recreate:
$ sh /tmp/recreate.sh
Read input format 'yaml' from 'bond-mtu-v1.yaml'.
Wrote output format 'sysconfig' to 'centos/sysconfig/from-v1/'
Read input format 'yaml' from 'bond-mtu-v2.yaml'.
Wrote output format 'sysconfig' to 'centos/sysconfig/from-v2/'
--- centos/sysconfig
** Changed in: cloud-utils
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836593
Title:
race condition in dep8 test
To manage notifications about this bug go to:
** 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/1836593
Title:
race condition in dep8 test
To manage notifications about this bug
** Attachment added: "full failed log from official run."
https://bugs.launchpad.net/cloud-utils/+bug/1836593/+attachment/5277177/+files/cloud-utils-ppc64el-0.31-0ubuntu1.log.gz
** Also affects: cloud-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-utils
0.31-3-gfadd07fe-0ubuntu1 is in eoan-proposed.
https://launchpad.net/ubuntu/+source/cloud-utils/0.31-3-gfadd07fe-0ubuntu1
** Changed in: cloud-utils (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: cloud-utils (Ubuntu Eoan)
Assignee: (unassigned) => Scott Moser (
those tags.
** Changed in: cloud-utils (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835124
Title:
growpart mishandles image filena
** Changed in: cloud-utils
Status: Confirmed => Fix Committed
** Changed in: cloud-utils (Ubuntu)
Assignee: Scott Moser (smoser) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
I agree that this is a bug (fix proposed), but fwiw, your naming of a
*disk* image with an extension 'ext4' is a bit confusing to anyone that
might see that file. Probably better '.disk' or '.img'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Filed issue with lxcfs at
https://github.com/lxc/lxcfs/issues/285
** Bug watch added: LXCFS bug tracker #285
https://github.com/lxc/lxcfs/issues/285
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
$ lxc launch ubuntu-daily:eoan devel1
$ sleep 10 # wait for boot
$ lxc exec devel1 /bin/bash
root@devel1:~# cat /proc/uptime
183.00 173.00
root@devel1:~# cat /etc/cloud/build.info
build_name: server
serial: 20190531
root@devel1:~# lsb_release -sc
eoan
root@devel1:~#
Quite a pleasent surprise I found today.
$ lxc launch ubuntu-daily:devel devel1
$ sleep 20
$ lxc exec devel1 systemctl status | grep State
State: running
$ lxc exec devel1 -- sh -c 'cat /etc/cloud/build.info; lsb_release -sc'
build_name: server
serial: 20190531
eoan
$ lxc exec devel1 --
I just added a bunch of other bugs that really are dups of this.
The goal of doing so is just to inform whoever might be looking at making a
change to more context on the unfortunate complexity of doing so.
Related bugs:
* bug 1016695: add console=tty1 to cloud-image kernel boot parameters
*
ack. a quick test gets that to actual python3 problems. ie, the build
change is correct, but upstream needs some changes. thanks.
On Tue, Feb 12, 2019 at 11:50 AM Robie Basak <1815...@bugs.launchpad.net> wrote:
>
> This probably needs:
>
> - dh $@ --with python2
> + dh $@ --with
Public bug reported:
After fresh install of 18.04, I went to install uvt-kvm.
A big slew of dependencies came... many from python2 stack.
it may well be not much more than this:
http://paste.ubuntu.com/p/VWVJhwpYm7/
to move to python3. but a quick sniff failed to build due to:
02/12/2019
There are 2 issues at play here:
a. bug 1666853: grub2 does not work correctly in 16.04 with ext4 filesystems
larger than 2TB. This appears to be fixed in 18.04, but the bug is not
currently marked as fixed there.
b. bug 1762748 was SRU'd to 16.04 which exposed bug 1666853. Before
that fix,
seems likely related to bug 1762748, and maybe that change overlapping
with bug 1666853 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812411
Title:
cloud-init corrupting grub
To manage
For my reference later.
The 'dconf read' with ':list' syntax has changed, so the comments above don't
work in 18.04.
Updated, this worked for me:
$ dconf list /org/gnome/terminal/legacy/profiles:/
:b1dcc9dd-5262-4d8d-a863-c897e6d979b9/
$ dconf write
Daniel,
Thanks for the bug report.
I've committed the fix to trunk.
** Changed in: cloud-utils (Ubuntu)
Importance: Undecided => Low
** Changed in: cloud-utils (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Also affects: simplestreams (Ubuntu)
Importance: Undecided
Status: New
** Changed in: simplestreams (Ubuntu)
Status: New => Confirmed
** Changed in: simplestreams (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of
I'm marking this fix-released. Per the debian bug, this should be in
any open-icsi >= 2.0.873+git0.3b4b4500-13
** Changed in: open-iscsi (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
moved on to systemd. feel free to re-file if necessary/relevant.
** Changed in: open-iscsi (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561041
Title:
** Changed in: open-iscsi (Ubuntu)
Status: Confirmed => Invalid
** Changed in: open-iscsi (Ubuntu Xenial)
Status: Confirmed => Invalid
** Changed in: open-iscsi (Ubuntu Bionic)
Status: Confirmed => Invalid
** Changed in: open-iscsi (Ubuntu Cosmic)
Status: Confirmed
http://autopkgtest.ubuntu.com/packages/o/open-iscsi
shows currently happy for xenial bionic and disco.
** Changed in: open-iscsi (Ubuntu)
Status: New => Fix Released
** Changed in: open-iscsi (Ubuntu Xenial)
Status: New => Fix Released
--
You received this bug notification
** Summary changed:
- vmtest: iscsi/LVM tests failing on cosmic/disco
+ vmtest: open-iscsi iscsi/LVM tests failing on cosmic/disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807978
Title:
Public bug reported:
Looking at source code for linuxDeployment.c [1] and also looking at
some logs, I'm pretty sure that the imc-customization path is using /tmp
to create files. That is not safe during systemd boot as the tmpfiles
cleaner may remove your files at any point.
[1]
With respect to the resource-agents autopkgtest failure in bionic,
I had commented on that in a previous SRU:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1802354/comments/18
copied here for eaiser view:
It seems this test fails transiently. It was quite reliable from
2017-11-27
** 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 iscsi mounts that were made
in the initramfs. The most likely scenario would be iscsi root.
The problem seen
The easiest thing to do would be to just ship a keyring that had the
obsolete public signing keys. Then the consumer could hard code
that 'precise' was signed with keys A, B, C. and work stuff out like
that.
Alternatively possibly we might want to deliver some distro-info like
data.
** Attachment added: "vmtest output/ from test verification for bionic"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1807978/+attachment/5222400/+files/bionic-output.tar.gz
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done
** Attachment added: "console log of test verification for bionic"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1807978/+attachment/5222399/+files/bionic-console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "vmtest output/ from test verification for cosmic"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1807978/+attachment/5222388/+files/cosmic-output.tar.gz
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug
** Attachment added: "console log of test verification for cosmic"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1807978/+attachment/5222387/+files/cosmic-console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1786244 ***
https://bugs.launchpad.net/bugs/1786244
** This bug has been marked a duplicate of bug 1786244
package linux-image-4.15.0-24-generic (not installed) failed to
install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with
'read <&2' seems like its probably a bug.
unless something else
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786244
Title:
package linux-image-4.15.0-24-generic (not installed) failed to
*** This bug is a duplicate of bug 1786244 ***
https://bugs.launchpad.net/bugs/1786244
** This bug has been marked a duplicate of bug 1786244
package linux-image-4.15.0-24-generic (not installed) failed to
install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with
** Changed in: ssh-import-id (Ubuntu)
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/1679404
Title:
Missing dep8 tests
To manage notifications about this bug go to:
** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+ This bug results in lvm devices on top of iscsi block devices not being
+ available to the system. The journal will show messages like:
+ [ 17.55] systemd[1]:
i (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: open-iscsi (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: open-iscsi (Ubuntu Cosmic)
Importance: Undecided => High
** Changed in: open-iscsi (Ubuntu)
Assignee: (unassigned) => Scott Moser
** Summary changed:
- vmtest: iscsi tests failing on cosmic/disco
+ vmtest: iscsi/LVM tests failing on cosmic/disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807978
Title:
vmtest: iscsi/LVM
The change here seems to have regressed at least some non-root iscsi
volume use cases. The curtin 'vmtest' test harness is showing failure
of its LVM on iscsi tests.
See bug 1802354 for more information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Here is a full journal of a failing system with a bunch of systemd debug added.
http://paste.ubuntu.com/p/8DMShKJgZR/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807978
Title:
vmtest: iscsi
I've verified that the bug can be fixed by removing the file
/lib/udev/rules.d/70-iscsi-disk.rules
from the image.
For reference, that file looks like:
SUBSYSTEM=="block", ACTION=="add", ENV{ID_PATH}=="*-iscsi-*",
ENV{SYSTEMD_WANTS}="iscsid.service"
iscsid.service looks like:
** Changed in: open-iscsi (Ubuntu)
Status: New => Confirmed
** Changed in: open-iscsi (Ubuntu)
Importance: Undecided => High
** Changed in: curtin (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Also affects: open-iscsi (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/1807978
Title:
vmtest: iscsi tests failing on cosmic/disco
To manage
This bug is believed to be fixed in cloud-utils in version 0.31. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-utils
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-utils in version 0.31. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-utils
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-utils in version 0.31. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Also affects: cloud-utils
Importance: Undecided
Status: New
** Changed in: cloud-utils
Status: New => Fix
This bug is believed to be fixed in cloud-utils in version 0.31. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-utils
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-utils in version 0.31. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Also affects: cloud-utils
Importance: Undecided
Status: New
** Changed in: cloud-utils
Status: New => Fix
This bug is believed to be fixed in cloud-utils in version 0.31. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-utils
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
@Oliver,
I have 2 questions about adding 'After=vgauth.service' to open-vm-tools.service
and adding 'DefaultDependencies=no' to vgauth.service.
a.) if open-vm-tools.service requires vgauth.service, then shouldn't we also
add a 'Requires=vgauth.service' ?
b.) Your MP adds RequiresMountsFor=/tmp
Public bug reported:
$ dpkg-query --show open-vmware-tools
dpkg-query: no packages found matching open-vmware-tools
$ dpkg-query --show open-vm-tools
open-vm-tools 2:10.3.0-0ubuntu1~18.04.3
$ dpkg -S /usr/bin/vmware-user
open-vm-tools: /usr/bin/vmware-user
$ ls -l /usr/bin/vmware-user
Well, I think I found out what was happening.
In gnome-tweaks I had somehow gotten 'Workspaces' -> 'Display Handling'
set to 'Workspaces on primary display only'.
So what happened was that there was only a single workspace on the
"second" head and thus no need for "always on visible workspace".
** Changed in: curtin (Ubuntu)
Status: New => Confirmed
** Changed in: curtin (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807216
Title:
As a comment (from the header in the reproduce script)
# The problem is that the user will be prompted with a dialog:
#What do you want to do about modified configuration file grub?
# even when there is no upstream change to the config file if they
# have made *both*:
# a. changes to
marked invalid. re-open if necessary.
** Changed in: compiz-plugins-main (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/1798540
Title:
Question on
This is currently held up from getting into 18.04 due to a failing
autopkgest for resource-agents on armhf.
https://autopkgtest.ubuntu.com/packages/resource-agents/bionic/armhf
It seems this test fails transiently. It was quite reliable from
2017-11-27 to 2018-08-09
with only a single
this was fix-released to xenial and artful under bug 1743618.
** Changed in: curtin (Ubuntu Xenial)
Status: Confirmed => Fix Released
** Changed in: curtin (Ubuntu Artful)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
As currently implemented, cloud-init will read either OVF CDrom *or* the
vmware IMC data.
That means if user-data is provided in the OVF environment file then it
will not be consumed at all by cloud-init.
It seems we need to either:
a.) support reading and merging these
Is this change expected to appear in Stable Releases? Does it conform
to Stable Release Updates policy?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805497
Title:
Snaps not included in image
** Attachment added: "recreate.sh: recreate the bug easilily."
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/564853/+attachment/5217387/+files/recreate.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/564853
Title:
Spurious conffile prompts for /etc/default/grub
To manage notifications about this bug go to:
** Changed in: grub2 (Ubuntu)
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/564853
Title:
Spurious conffile prompts for /etc/default/grub
To manage notifications
** Attachment added: "cosmic autopkgtest console log"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1802354/+attachment/5216836/+files/cosmic-autopkgtest.log
** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done verification-done-cosmic
I've attachd cosmic logs of a (second) run of the autopkg test.
this was successful and the following shows iscsi was running
$ grep open-iscsi manifest.txt
open-iscsi 2.0.874-5ubuntu9.1
$ cat ./iscsid-status.txt
active
● iscsid.service - iSCSI initiator daemon (iscsid)
Loaded: loaded
** Attachment added: "cosmic autopkgtest artifacts"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1802354/+attachment/5216835/+files/cosmic-autopkgtest-artifacts.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "bionic autopkg console log"
https://bugs.launchpad.net/ubuntu/cosmic/+source/open-iscsi/+bug/1802354/+attachment/5216832/+files/bionic-autopkgtest.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "bionic autopkg test artifacts"
https://bugs.launchpad.net/ubuntu/cosmic/+source/open-iscsi/+bug/1802354/+attachment/5216833/+files/bionic-autopkgtest-artifacts.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm marking bionic as verified.
In order to test this I did the following:
a.) have attached the log and artifacts from the open-iscsi dep8 run
for open-iscsi/2.0.874-5ubuntu2.4 on 2018-11-20 18:42:40 UTC
as 'bionic-autopkgtest.log' and 'bionic-autopkgtest-artifacts.tar.gz'
b.) tested on
I'm marking this fix-released for bionic and xenial.
The fix is available in bionic-updates and xenial-updates
and was SRU'd under bug 1795953.
If you are experiencing this problem still, re-open the bug.
Thank you.
** Changed in: cloud-init (Ubuntu Xenial)
Status: Confirmed => Fix
101 - 200 of 11836 matches
Mail list logo
