fixed in 0.28
** Changed in: cloud-utils
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1087526
Title:
need support for g
fixed in 0.28
** Changed in: cloud-utils
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1302052
Title:
mount-image-callback : --dev
fixed in 0.28
** Changed in: cloud-utils
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1303786
Title:
ubuntu-ec2-run stack trace
fixed in 0.28
** Changed in: cloud-utils
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1259703
Title:
growpart on disk larger than
fixed in 0.28
** Changed in: cloud-utils
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1492386
Title:
mount-image-callback: must s
we no logner use that cron job.
** Changed in: cloud-utils (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-utils in Ubuntu.
https://bugs.launchpad.net/bugs/641651
Title:
uec-quer
** Changed in: cloud-utils (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1055211
Title:
cloud-run-instances crashed with SyntaxE
cloud-image-utils was split out, now it depends on qemu-utils and
genisoimage.
** Changed in: cloud-utils
Status: Triaged => Fix Released
** Changed in: cloud-utils (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Se
marking this wont-fix. this tool has kind of been deprecated. i would
take a well done patch though.
** Changed in: cloud-utils (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-utils
I'm pretty sure this is fixed.
I've just tried partitioning a disk with gpt and 11 partitions on xenial and
then run
$ sudo growpart /dev/vdb 11
sudo: unable to resolve host xenial-20160510-175548
CHANGED: partition=11 start=206848 old: size=204800 end=411648 new:
size=83679199,end=83886047
ple
fix released in 0.28. Also, the suggestion is to have distro-info (it
is Recommends).
** Changed in: cloud-utils (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-utils (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubu
** Description changed:
+ == Begin SRU Template ==
+ [Impact]
+ This update to curtin is required to support features of MAAS 1.9 that is
being SRU'd to trusty and wily under bug 1509147. There are also numerous bug
fixes that affect the code path used with older maas as well. See the
change
I've just uploaded 0.1.0~bzr387-0ubuntu1~YY.MM.1 to each xenial wily and trusty.
yakkety does not yet have 387 due to LP: #1560134.
** Description changed:
- In order to support MAAS sru of 1.9 into trusty, we need a newer version
- of curtin.
+ In order to support MAAS sru of 1.9 into trusty, we
## This uses qemu and a maas image to easily test bcache of a root disk
## on a vm. Originally put together for bug 1515780
## It does:
## * downloads a maas image, kernel and initramfs
## * and makes a disk with 1M in front for the bcache header (root.img)
## * creates a disk for cache image (c
** Attachment added: "suggested /lib/systemd/system-sleep/bcache.sh"
https://bugs.launchpad.net/debian/+source/bcache-tools/+bug/1515780/+attachment/4659445/+files/bcache.sh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bcache-too
** Bug watch added: Debian Bug tracker #823860
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823860
** Also affects: bcache-tools (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823860
Importance: Unknown
Status: Unknown
--
You received this bug notification beca
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1577844
Title:
Drop unnecessary blocking of all net udev rule
** Description changed:
We're interested in supporting network configuration of lxc containers
via maas/cloud-init yaml format.
The end goal is to do:
$ lxc init xenial x1
# enter into container and modify
/var/lib/cloud/seed/nocloud-net/network-config
# to have something like:
** Summary changed:
- [SRU] xenial curtin to trusty
+ [SRU] yakkety curtin to trusty and xenial
** Also affects: curtin (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: curtin (Ubuntu Xenial)
Impo
Public bug reported:
currently the glance mirror requires hypervisor_mapping config in the api.
Better to not required that as a library consumer would not necessarily provide
it.
** Affects: simplestreams
Importance: Medium
Status: Fix Committed
** Affects: simplestreams (Ubuntu)
Public bug reported:
In order for web service to aggregate custom logs, simplestreams client
should identify itself via user-agent.
** Affects: simplestreams
Importance: Medium
Status: Fix Committed
** Affects: simplestreams (Ubuntu)
Importance: Medium
Status: Confirm
some futher thought one reason for the blocking of udev was to have the .link
files that cloud-init wrote apply.
It turns out that systemd.link will only rename devices once (based on a
property in the devices /sys that says it has been renamed).
So, for cloud-init to have these apply we will pr
Public bug reported:
In order to support MAAS sru of 1.9 into trusty, we need a newer version
of curtin.
* debian/new-upstream-snapshot, debian/README.source: add
new-upstream-snapshot and mention it in README.source
* debian/control: adjust build dependency as python3-pyflakes in xenial
** Description changed:
We would like to request a SRU for MAAS 1.9. This follow the approval by
the Ubuntu Technical Board for backporting new MAAS upstream releases.
[Impact]
This is a new version of MAAS that provides new features as well as various
bug fixes against various issues.
** Changed in: bcache-tools (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bcache-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1515780
Title:
bcache does not work with suspend
To mana
** Changed in: curtin (Ubuntu)
Status: New => Fix Released
** Also affects: curtin (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: curtin (Ubuntu Trusty)
Importance: Undecided => Medium
--
I consider 'system-upgrade' as the fix for this.
Either add config that does:
system_updgrade: enabled: True
or run
curtin system-upgrade
as a late_command
** Also affects: curtin
Importance: Undecided
Status: New
** Changed in: curtin
Status: New => Fix Committed
** Changed
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1449099
T
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status: Confirmed => In Progress
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification b
Public bug reported:
in cloud-init users can install packages via cloud-config:
#cloud-config
packages: [apache2]
Due to some intricacies of systemd and service installation that doesn't work
all that well.
We fixed the issue for simple services that do not have any dependencies on
other servic
** Description changed:
Using the following cloud config, apache2 will fail to start on
installation on Xenial:
#cloud-config
packages:
- apache2
See for example:
$ gcloud compute instances create xenial-$(date +%y%m%d-%H%M) --image
ubuntu-1604-xenial-v20160420c --image-pro
> This behaviour of installing packages or configuring your system while the
> system isn't booted yet might also bite you in other cases (it certainly bit
> me a number of cases). Maybe we should discuss how to move that after the
> boot? I do that in
> https://git.launchpad.net/~ubuntu-release/+g
Pitti, in reponse to comment 5 above:
> > d.) output of runlevel is stored in RL and then it goes looking for an
> > SLINK or SSLINK (/etc/rc$RL.d/S??apache2 or /etc/rcS.d/S??apache2). Neither
> > of these exist so it exits without starting the service.
> To be sure we are talking about the same t
tus: New => Fix Committed
** Changed in: cloud-init
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/15750
I spoke with cyphermox, and it seems that probably the right way for
this to happen is for cloud-init to prompt at install time at the proper
priority and then the installer will ask. Alternatively, we could seed
the question in the installer preseed so there is no prompt and it is
disabled.
** A
Public bug reported:
pollinate runs too early on some of the instances i launch. Basically
nothing guarantees that it will have network access when it attempts to
run.
failure looks something like:
$ lxc launch xenial x1
$ sleep 4
$ lxc exec x1 systemctl status pollinate
● pollinate.service - S
Ok, here is what is happening:
a.) dpkg (or apt) install of apache2 (or just about any service) starts
services by calling to /usr/sbin/invoke-rc.d (like 'invoke-rc.d apache2 start').
b.) invoke-rc.d calls 'runlevel' to get the current runlevel and see if this
service should be started.
c.) ru
** Also affects: cloud-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1574963
Title:
juju2 lxd launch hostname reverse lookup i
this is fix-released from cloud-init perspective in xenial.
If you disagree, please state why and open the bug. cloud-init now renders
.rules files and configures ENI per the datasource's provided network config or
a fallback network config.
** No longer affects: cloud-init
** Changed in: clo
This is solvable in cloud-init, and it would not be terribly invasive
for the lxc datasource (nocloud) as that is "local". For other
datasources that use the network, its more complex at least for now as
getting the hostname would mean dhcp on the network interface and thus
advertising 'ubuntu'.
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => Medium
--
You
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status: Confirmed => Fix Released
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: c
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team,
marking fix-released in util-linux as we have 2.27 in xenial.
** Changed in: util-linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-utils in Ubuntu.
https://bugs.launchpad.net
pply networking less often, when possible only on first
instance boot (LP: #1571004).
- no longer delete /etc/network/interfaces.d/eth0.cfg on
ubuntu (LP: #1563487)
-- Scott Moser Fri, 15 Apr 2016 16:25:43 -0400
** Changed in: cloud-init
Status: Fix Committed => Fix Relea
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bug
So:
a.) zfs-import-cache.service is 'After systemd-udev-settle.service'
b.) cloud-init installs /lib/udev/rules.d/79-cloud-init-net-wait.rules which
uses IMPORT of /lib/udev/cloud-init-wait to block network device add events
until cloud-init-local has written networking configuration
I'm pretty
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1571761
Title:
zfs-import-cache.service slows boot
** Description changed:
- when i removed the symlink in the maas ephemeral image from
/etc/network/interfaces
- the iscsi root boot fails, and maas deployment would also fail.
+ when i removed the symlink in the maas ephemeral image from
/etc/network/interfaces the iscsi root boot fails, and ma
** No longer affects: cloud-init (Ubuntu)
** No longer affects: maas-images
** No longer affects: cloud-init
** Description changed:
newer ifupdown versions (those in xenial) now keep interface state in
/run/network/ifstate. rather than combined in
/run/network/ifstate .
We need to u
fixed in trunk at revno 210.
** Changed in: cloud-init
Status: Confirmed => Fix Committed
** Changed in: cloud-init
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clou
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Confirmed
** Changed in: livecd-rootfs (Ubuntu)
Importance: Undecided => Medium
** Changed in: livecd-rootfs (Ubuntu)
Status: Confirmed => Fix
** Summary changed:
- ifupdown wants to configure interfaces it shouldn't (lxdbr0)
+ ifupdown wants to configure interfaces it shouldn't (lxdbr0 or veth)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bug
ok. So under bug 1569974 i fixed cloud-init to not consider the bridge as
something it should pick as a fallback nic.
However, there is still a problem in that cloud-init may select the host side
of a veth device.
The result is that
$ cat /etc/network/interfaces.d/50-cloud-init.cfg
auto vethVH9
** This bug is no longer a duplicate of bug 1569974
networking fallback should ignore bridges
** Changed in: lxd (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bu
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1570119
Title:
xenial ppc64le cloud image crashes on nested vi
At this point, I think the second patch there is doing the right thing.
The reason I asked slangasek to NAC my upload was that poweroff wasnt' working
correctly.
The reason poweroff wasn't working correctly was that cloud-init is writing
'auto eth0' where cloud-initramfs-dyn-netconf is writing 'm
*** This bug is a duplicate of bug 1569974 ***
https://bugs.launchpad.net/bugs/1569974
** This bug has been marked a duplicate of bug 1569974
networking fallback should ignore bridges
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1543459
Title:
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Serv
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Importance: Undecided => High
** Changed in: cloud-init
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is su
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Public bug reported:
Serge pointed me at an an issue with cloud-init's fallback networking.
It will consider bridges as possible devices to dhcp on.
Since these bridges are configured only by things like lxd (not
/etc/network/interfaces) they're not going to be good devices to 'dhcp' on and
get
I've seen this reproduce more and more in curtin tests lately in xenial:
https://server-team-jenkins.canonical.com/job/curtin-vmtest-venonat-devel/15/artifact/output/XenialBcacheBasic/logs/install-serial.log/*view*/
https://server-team-jenkins.canonical.com/job/curtin-vmtest-venonat-devel/15
Public bug reported:
if there is no product name in dmi data, cloud-init log will show
DataSourceCloudSigma.py[WARNING]: failed to get hypervisor product name via dmi
data
util.py[WARNING]: Getting data from failed
util.py[DEBUG]: Getting data from failed#
Traceback (most recent call last):#
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/b
Marking as 'fix-released' in maas in wily and xenial, as the fix went into
trunk at revision 4028.
https://code.launchpad.net/~rvb/maas/lp-1313550/+merge/262314
** Changed in: maas (Ubuntu Wily)
Status: New => Fix Released
** Changed in: maas (Ubuntu)
Status: Confirmed => Fix Relea
Committed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bug
just for some more info, I asked for clarification from cjwatson.
$ rmadison gfx-boot-theme-ubuntu
gfxboot-theme-ubuntu | 0.13.2 | precise | source, amd64, i386
gfxboot-theme-ubuntu | 0.13.3 | precise-updates | source, amd64, i386
gfxboot-theme-ubuntu | 0.16.1 | trusty | sourc
** Package changed: gfxboot (Ubuntu) => gfxboot-theme-ubuntu (Ubuntu)
** Also affects: syslinux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad
There was some conversation on irc yesterday.
http://irclogs.ubuntu.com/2016/04/11/%23ubuntu-devel.html#t20:18
cjwatson suggested likely gfxboot-theme-ubuntu as the bug component.
** Also affects: gfxboot (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => High
** Changed in: maas-images
Status: N
A quick bit of testing shows that this regressed between
ubuntu-15.04-server-amd64.iso and ubuntu-15.10-server-amd64.iso .
So:
WORKS: ubuntu-14.04.4-server-amd64.iso
WORKS: ubuntu-15.04-server-amd64.iso
FAILS: ubuntu-15.10-server-amd64.iso
FAILS: xenial-server-amd64-daily-20160411.2.iso
Thats go
Public bug reported:
recent changes to lxd added configuration of the lxd bridge.
We'd like to enable that in cloud-init.
The change allows the user to put config in cloud-config that will
basically map to the debconf keys and thus configure their lxd bridge
and lxd init on first boot making it
Public bug reported:
when i removed the symlink in the maas ephemeral image from
/etc/network/interfaces
the iscsi root boot fails, and maas deployment would also fail.
** Affects: cloud-init
Importance: Undecided
Status: New
** Affects: maas-images
Importance: Undecided
** Also affects: cloud-init (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Trusty)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu Trusty)
Importance: Undecided => Medium
--
You received this bug notification because you are a me
Hi,
I'm marking this bug as 'Invalid' as I'm not able to reproduce it. If you can
reproduce with current xenial please do re-open with details. I've collected
some virsh capabilities output from the system that I ran this on at
http://paste.ubuntu.com/15675510/
** Changed in: libvirt (Ubuntu)
** Package changed: cloud-init (Ubuntu) => open-iscsi (Ubuntu)
** Changed in: open-iscsi (Ubuntu)
Importance: Undecided => Medium
** Changed in: open-iscsi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Likely related/result of bug 1115710.
The reference to mlx4.conf is what lead me to believe that. I'll dig a bit more
tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/15664
ok. so after playing some, this all comes down to needing 'usb=off' on
the qemu command line.
works:
qemu-system-ppc64 -enable-kvm -machine usb=off -device
virtio-net-pci,netdev=net00 -netdev type=user,id=net00 -drive
if=virtio,file=xenial-server-cloudimg-ppc64el-disk1.img,format=qcow2 -drive
i
Note, that Michael Roth's comments are probably valid. I suspect that
if leftyfb ever saw this working on powerVM host, then it was through
the kvm_pr module. In my experience, that works generally pretty well
(buit my testing has only ever been done powerNV host).
--
You received this bug noti
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
To manage notifi
this is fix-released in any thing newere than revision 1008.
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/b
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1525361
Title:
Install of upstream Docker package only fails
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/b
*** This bug is a duplicate of bug 1311463 ***
https://bugs.launchpad.net/bugs/1311463
Hi, i've marked as a duplicate.
bug 1311463 is correctly triaged to have been nominated for the series that are
broken.
** This bug has been marked a duplicate of bug 1311463
disk-setup unable to parti
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Low
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Im
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.ne
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Also affects: cloud-init (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Precise)
Status: New => Co
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscri
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Low
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs
fixed in trunk at 1198.
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Importance: Undecided => Low
** Changed in: cloud-init
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubu
signee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1514407
Title:
NoCloud provider fails with empty ds_cfg
To manage notifications about
** 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)
Importance: Undecided => Medium
--
You received this bug notification
fixed in trunk at 1199.
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1565638
Title:
Cloud-init on Xenial wo
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Low
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, whi
Greg,
So digged a bit further, it seems that the ubuntu images do the right thing in
that /etc/machine-id is not present in the image itself. I suspect your
instances that you noticed this on were snapshotted from a once-booted instance
or in some other way booted. If that is the case, it would
Yeah, likely this happens to early in boot for cloud-init to affect.
I've marked livecd-rootfs as a target, which is (i think) proper for changing
the images themselves.
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu)
1 - 100 of 3193 matches
Mail list logo
