Disco vmtest artifacts
** Attachment added: "Disco vmtest artifacts"
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275688/+files/curtin-vmtest-proposed-d-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Cosmic vmtest console log from rerunning tests that timed out.
** Attachment added: "Cosmic vmtest console log from rerunning tests that timed
out."
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275687/+files/curtin-vmtest-proposed-c-diglett-console.log
--
You received this
Bionic vmtest artifacts from repeating tests that timed out.
** Attachment added: "Bionic vmtest artifacts from repeating tests that timed
out."
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275680/+files/curtin-vmtest-proposed-b-diglett-artifacts.tar.xz
--
You received this
Cosmic vmtest artifacts
** Attachment added: "Cosmic vmtest artifacts"
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275684/+files/curtin-vmtest-proposed-c-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Bionic vmtest console log
** Attachment added: "Bionic vmtest console log"
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275679/+files/curtin-vmtest-proposed-b-console.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Bionic curtin-proposed test artifacts.
** Attachment added: "Bionic curtin-proposed test artifacts."
https://bugs.launchpad.net/curtin/+bug/1831772/+attachment/5275669/+files/curtin-vmtest-proposed-b-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
The shutdown plan requires that the config for a device being cleared to
not include the preserve: True config. The "raid" partition, vda3 is
explicitly marked as preserved: true:
- device: disk-vda
size: 20947402752
flag: linux
preserve: true
type: partition
id:
Without the patch, I can reproduce the hang fairly frequently, in one or
two loops, which fails in this way:
[ 1069.711956] bcache: cancel_writeback_rate_update_dwork() give up waiting for
dc->writeback_write_update to quit
[ 1088.583986] INFO: task kworker/0:2:436 blocked for more than 120
I've setup our integration test that runs the the CDO-QA bcache/ceph
setup.
On the updated kernel I got through 10 loops on the deployment before it
stacktraced:
http://paste.ubuntu.com/p/zVrtvKBfCY/
[ 3939.846908] bcache: bch_cached_dev_attach() Caching vdd as bcache5 on set
I think you'll want to run:
cloud-init clean --logs
After doing your changes to the images; this will remove most cloud-init
state.
--
cloud-init will always run on each boot that it detects that it has data to
process. So on VMWare, if an OVF iso is provided, or the vmdata is set in the
Hrm, something looks a bit odd. In the collect logs, I can see that
cloud-init found an OVF attached to the instance, however in the cloud-
init.log there appears to be an existing boot of cloud-init already
present:
2019-06-21 15:33:41,226 - main.py[DEBUG]: Execution continuing, no previous run
Yuck. This is quite awkward. Neither half of probert wants the other
half.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834897
Title:
probert has too many dependencies for consoleconf
To
Hi,
Could you run:
cloud-init collect-logs
and attach the tarball it creates?
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Wrong source package
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: evince (Ubuntu)
Status: New => Invalid
** Merge proposal linked:
https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/368902
--
You received this
Thanks, we'll be uploading a replacement source package which drops the
dependency on probert in bionic, cosmic and disco. Thanks for the
review
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831772
since probert is not yet in main, we can't have probert as a depends in
any of the releases.
** Also affects: curtin (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu
Do you happen to have a cloud-init collect-logs output ? I suspect it's
easy enough to recreate bug if you've already got logs available, please
attach.
** Summary changed:
- vm fails to boot due to conflicting network configuration when cloudinit
switches from netplan to eni
+ vm fails to
** Changed in: netplan
Status: Incomplete => Invalid
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
https://git.launchpad.net/curtin/commit/?id=55aa836f04657dac67445e154b2ee5fe78b8db8a
** Changed in: curtin (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
nly
+
+ -- Ryan Harper Wed, 05 Jun 2019 13:46:57 -0500
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Looks like this issue, I think:
https://github.com/systemd/systemd/issues/12490
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Not an upstream bug.
** Changed in: curtin
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/1831772
Title:
sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1
To manage
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:
*
See the changelog entry below for a full list of changes and
Public bug reported:
On Xenial
1. add-apt-repository --enable-source --yes ppa:curtin-dev/daily
2. apt-get install --no-install-recommends -qy curtin
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
On Mon, Jun 3, 2019 at 2:05 PM Andrey Grebennikov <
agrebennikov1...@gmail.com> wrote:
> Is there an estimate on getting this package in bionic-updates please?
>
We are starting an SRU of curtin this week. SRU's take at least 7 days
from when they hit -proposed
possibly longer depending on test
Can you collect:
systemctl list-jobs?
>From the logs, it appears that snapd has not yet seeded, which blocks
cloud-final.service from running, so it's blocking until snapd is ready.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
IIUC
"proper partition setup" for callers of curtin is:
/boot/EFI partition *and* a grub_bios partition.
Something like:
config:
- id: main_disk
type:
Looks to have a fix committed now.
https://github.com/CanonicalLtd/netplan/commit/ee94ec118a8aabef8d79e78e7b2f028615a28ce8
** Changed in: netplan
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking this invalid since DASDs can't be used directly without a
partition table.
** Changed in: bcache-tools (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Wed, May 8, 2019 at 11:55 PM Trent Lloyd
wrote:
> I have been running into this (curtin 18.1-17-gae48e86f-
> 0ubuntu1~16.04.1)
>
> I think this commit basically agrees with my thoughts but I just wanted
> to share them explicitly in case they are interesting
>
> (1) If you *unregister* the
Xenial GA kernel bcache unregister oops:
http://paste.ubuntu.com/p/BzfHFjzZ8y/
--
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
Reading through the lxd issue log, it appears that a host networking
issue/packaging issue triggered on upgrade; unrelated to cloud-init
inside the containers. If you feel that cloud-init isn't doing
something correct, please re-open this bug with new information.
Thanks.
** Changed in:
** Changed in: curtin (Ubuntu)
Importance: Undecided => High
** Changed in: curtin (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805673
Title:
dname for
** Changed in: curtin (Ubuntu)
Importance: Undecided => High
** Changed in: curtin (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805674
Title:
curtin
This was fixed in commit:
https://git.launchpad.net/cloud-
init/commit/?id=947d3c20891815f164f4c7a8884d1f02ae4a9c5b
** Changed in: cloud-init
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Thanks for reporting this.
DataSourceConfigDrive doesn't currently set this value, and likely won't
by default. However, we do want to allow user-config to opt-in to this
behavior.
This is a work-in-progress feature, currently here:
** Changed in: cloud-init (Ubuntu)
Status: New => 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/1824185
Title:
Release a new upstream snapshot to disco
To manage notifications
** Changed in: cloud-init (Ubuntu)
Status: New => 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/1825444
Title:
"make rpm" fails on CentOS after commit 947d3c208
To manage
** Changed in: curtin (Ubuntu)
Importance: Undecided => Medium
** Changed in: curtin (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827929
Title:
curtin
Sorry, I missed responding.
This were run in separate VMs, this is under our curtin vmtest
integration testing.
Yes, let me get the q35 trace; it doesn't happen as often.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks like I got it wrong. The critical step is to have *both* serial
and wwn set to the same value in the -device config like so:
-device scsi-
hd,drive=drv2,serial=0x39cc071e72c64cc4,wwn=0x39cc071e72c64cc4
and then the sg_inq command succeeds like so:
# /usr/bin/sg_inq --export
Public bug reported:
In vmtest, we use virtio-scsi controller with scsi-hd devices. When we
supply them with a wwn property, 60-persistent-storage.rules will create
a /dev/disk/by-id/wwn- to point to the disk with said
property.
In disco, we now include multipath-tools which brings in
Hi Seth,
notice only one of the stack tracks have the floppy, the mdadm one does
not. I've also recreated this on a qemu q35 machine type which does not
include the floppy device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
1. disco
2. # apt-cache policy linux-image-virtual
linux-image-virtual:
Installed: 5.0.0.13.14
Candidate: 5.0.0.13.14
Version table:
*** 5.0.0.13.14 500
500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status
3.
root@ubuntu:~# lspci -v -nn
00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma]
[8086:1237] (rev 02)
Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
Flags: fast devsel
00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton
ged in: curtin
Status: New => Confirmed
** Changed in: curtin
Assignee: (unassigned) => Ryan Harper (raharper)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825007
Title:
chzdev expor
On Mon, Apr 15, 2019 at 9:21 AM Pengzhen(Peter) Cao
wrote:
> Hi Ryan,
>
> As you said, "cloudinit/sources/helpers/vmware/imc/config_nic.py" now
> generates v1 network_state dictionary. Should I just add a "DHCPFROMDNS:
> true/false" key as V1 format or should I update the output to v2
> together
What zfs property are you aware of that takes yes/no or maybe?
** Changed in: curtin (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824172
Title:
Do not
@Steve,
In preparing an upload for probert, in addition to the functional
changes, there are some debian directory clean-ups, wondering if those
are acceptable under this FFe? (some of the changes are adding package
deps for the feature, so I'd assume those are).
Hi,
For now, the version from dpkg is the best way. Netplan does have plans
for querying feature-flags/--version.
https://trello.com/c/ls9KUQuV/42-feature-availability-documentation-
introspection-feature-flags
--
You received this bug notification because you are a member of Ubuntu
Bugs,
On Thu, Apr 4, 2019 at 9:06 PM Seth Arnold <1817...@bugs.launchpad.net>
wrote:
> Two methods come to mind:
>
> - Writing an apt sources.list that omits the -updates pocket
> - Writing apt pinning rules that omits the -updates pocket.
>
> I would prefer we install all updates, unless the user has
** Changed in: curtin (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750732
Title:
grub package will change the boot order for MaaS deployed system
To
I'm closing the cloud-init task; If there is further information about
what cloud-init would need to do here, please reopen.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Matt,
This is expected behavior. MAAS provides network configuration to
cloud-init (via curtin). Cloud-init will rename interfaces that are
part of the provided network configuration to ensure the configuration
will apply. If you need to reconfigure or provide additional
configuration, you
Comment #3 correctly diagnoses the issue (bad network-config) which
caused cloud-init to error out. And Comment #11 suggests that this
configuration has been resolved. I'm closing the cloud-init task here.
Please re-open if you believe there is a cloud-init issue that needs
fixing.
** Changed
There are no restrictions on non-dasd devices so we can update curtin to
ensure that we don't allow creating bcache devices on dasd without a
partition.
I'm not sure whether or not it's worth adding dasd specific checks to
bcache-tools to refuse when supplied with a dasd block device.
--
You
Thanks for reporting the error.
Curtin is attempting to extract BootOrder and BootCurrent. A non-zero return
code from running efibootmgr -v is unexpected.
It's not clear to me if this is a fatal error; it doesn't appear that
way to me.If it isn't then ideally we'll need to determine the
** Attachment added: "core from bcache-super-show"
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1821353/+attachment/5249549/+files/_usr_sbin_bcache-super-show.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
1. # lsb_release -rd
Description:Ubuntu Disco Dingo (development branch)
Release:19.04
2. # apt-cache policy bcache-tools
bcache-tools:
Installed: 1.0.8-3
Candidate: 1.0.8-3
Version table:
*** 1.0.8-3 500
500 http://us.ports.ubuntu.com/ubuntu-ports
Just to close the loop on comment #17, the SRU includes this commit:
https://git.launchpad.net/curtin/commit/?id=b473fd507e6e6ae76c30df3199fdd3adc697d825
which was the additional change needed to completely resolve the issue.
--
You received this bug notification because you are a member of
Cosmic MAAS QA artifacts.
** Attachment added: "maas-qa-sru-proposed-cosmic-curtin-sru-manual.zip"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+attachment/5247673/+files/maas-qa-sru-proposed-cosmic-curtin-sru-manual.zip
** Tags removed: verification-needed
Xenial curtin-proposed test log. Note there is one expected failure
(DiscoAllindata); not a curtin issue (LP: #1818876)
** Attachment added: "curtin-vmtest-proposed-x-console.log"
disabling of system_upgrade.
-- Ryan Harper Wed, 27 Feb 2019 16:43:21
-0600
curtin (18.2-0ubuntu1) disco; urgency=medium
* New upstream release (18.2).
- Release 18.2
- Adjust helpers/common to edit GRUB_CMDLINE_LINUX_DEFAULT in place.
(LP: #1527664)
** Changed in: cloud-init (Ubuntu)
Status: Triaged => 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/1819038
Title:
[FFe] New upstream snapshot
To manage notifications about
** Changed in: cloud-init (Ubuntu Disco)
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/1819067
Title:
cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 ->
MAAS QA Results for cloud-init on Xenial
** Attachment added: "maas-sru-proposed-cloudinit-xenial.zip"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5247649/+files/maas-sru-proposed-cloudinit-xenial.zip
--
You received this bug notification because you are a
MAAS QA Results for cloud-init on Cosmic
** Attachment added: "maas-sru-proposed-cloudinit-cosmic.zip"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5247651/+files/maas-sru-proposed-cloudinit-cosmic.zip
--
You received this bug notification because you are a
MAAS QA Results for cloud-init on Bionic
** Attachment added: "maas-sru-proposed-cloudinit-bionic.zip"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5247650/+files/maas-sru-proposed-cloudinit-bionic.zip
--
You received this bug notification because you are a
Kernel oops when attempting to stop an online bcache device.
** Attachment added: "trusty-bcache-null.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820754/+attachment/5247406/+files/trusty-bcache-null.txt
** Tags added: curtin
--
You received this bug notification because you
Public bug reported:
1) # cat /proc/version_signature
Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-generic 3.13.0.167.178
ProcVersionSignature: Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39
Uname: Linux 3.13.0-166-generic x86_64
NoCloud Xenial, Bionic and Cosmic Manual test results.
** Attachment added: "nocloud-all-18.5-45-g3554ffe8-0ubuntu1.txt"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5246599/+files/nocloud-all-18.5-45-g3554ffe8-0ubuntu1.txt
--
You received this bug
OpenStack Xenial, Bionic, Cosmic manual test results.
** Attachment added: "openstack-sru-18.5-45-g3554ffe8-0ubuntu1.txt"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5246598/+files/openstack-sru-18.5-45-g3554ffe8-0ubuntu1.txt
--
You received this bug
GCE Xenial, Bionic and Cosmic manual test results!
** Attachment added: "gce-sru-18.5-45-g3554ffe8-0ubuntu1.txt"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5246597/+files/gce-sru-18.5-45-g3554ffe8-0ubuntu1.txt
--
You received this bug notification because
Azure Xenial, Bionic and Cosmic Manual Test results
** Attachment added: "azure-sru-18.5-45-g3554ffe8-0ubuntu1.txt"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5246593/+files/azure-sru-18.5-45-g3554ffe8-0ubuntu1.txt
--
You received this bug notification
Xenial proposed automated testing of lxd, nocloud-kvm and ec2 platforms,
18.5-45-g3554ffe8-0ubuntu1_16.04.1.
** Attachment added: "cloud-init-integration-proposed-x-console.log"
EC2 Xenial, Bionic and Cosmic manual test results.
** Attachment added: "ec2-sru-18.5-45-g3554ffe8-0ubuntu1.txt"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1819067/+attachment/5246592/+files/ec2-sru-18.5-45-g3554ffe8-0ubuntu1.txt
--
You received this bug notification because
Cosmic proposed automated testing of lxd, nocloud-kvm and ec2 platforms,
18.5-21-g8ee294d5-0ubuntu1_18.10.1
** Attachment added: "cloud-init-integration-proposed-c-console.log"
Bionic proposed automated testing of lxd, nocloud-kvm and ec2 platforms,
18.5-45-g3554ffe8-0ubuntu1_18.04.1
** Attachment added: "cloud-init-integration-proposed-b-console.log"
Bionic curtin-proposed test log. Note there is one expected failure
(DiscoAllindata); not a curtin issue (LP: #1818876)
** Attachment added: "curtin-vmtest-proposed-b-console.log"
Xenial MAAS QA artifacts.
** Attachment added: "maas-qa-sru-proposed-xenial-curtin-sru-manual.zip"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+attachment/5246223/+files/maas-qa-sru-proposed-xenial-curtin-sru-manual.zip
--
You received this bug notification because you are
Cosmic curtin-proposed artifacts.
** Attachment added: "curtin-vmtest-proposed-c-artifacts.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+attachment/5246219/+files/curtin-vmtest-proposed-c-artifacts.tar.xz
--
You received this bug notification because you are a
Bionic MAAS QA artifacts
** Attachment added: "maas-qa-sru-proposed-bionic-curtin-sru-manual.zip"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+attachment/5246222/+files/maas-qa-sru-proposed-bionic-curtin-sru-manual.zip
--
You received this bug notification because you are
Cosmic curtin-proposed test log. Note there is one expected failure
(DiscoAllindata); not a curtin issue (LP: #1818876)
** Attachment added: "curtin-vmtest-proposed-c-console.log"
Bionic curtin-proposed artifacts.
** Attachment added: "curtin-vmtest-proposed-b-artifacts.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1817964/+attachment/5246221/+files/curtin-vmtest-proposed-b-artifacts.tar.xz
--
You received this bug notification because you are a
subiquity is providing configuration to cloud-init to perform
configuration on first boot already; cloud-init will happily do what
it's told.
I think there are several options on the configuration provided to
cloud-init. Subiquity can provide the hostname statically into the
image and not ask
OK, this is easily reproduced by adding a single static IP in the same
subnet as the IP that comes from dhcp'ing on the interface.
For example, if you launch an instance with a 10.0.0./24 subnet, the
dhcp IP is something like 10.0.0.4
You can login and
curl -H Metadata:true
** Description changed:
== 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:
- opennebula: incremental updates to exclude
GCE Xenial, Bionic and Cosmic Manual test results.
** Attachment added: "gce-sru-18.5.21.txt"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+attachment/5244180/+files/gce-sru-18.5.21.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
MAAS QA Xenial Test Results
** Attachment added: "sru-proposed-cloudinit-xenial.zip"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+attachment/5244177/+files/sru-proposed-cloudinit-xenial.zip
** Description changed:
== Begin SRU Template ==
[Impact]
This release
MAAS QA Bionic test results
** Attachment added: "sru-proposed-cloudinit-bionic.zip"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+attachment/5244175/+files/sru-proposed-cloudinit-bionic.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Azure Xenial, Bionic and Cosmic Manual Test results
** Attachment added: "azure-sru-18.5.21.txt"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+attachment/5244173/+files/azure-sru-18.5.21.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
OpenStack Xenial, Bionic and Cosmic Manual test results.
** Attachment added: "openstack-sru-18.5.21.txt"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+attachment/5244174/+files/openstack-sru-18.5.21.txt
--
You received this bug notification because you are a member of
Bionic proposed automated testing of lxd, nocloud-kvm and ec2 platforms,
18.5-21-g8ee294d5-0ubuntu1_18.04.1
** Attachment added: "cloud-init-integration-proposed-b-console.log"
Cosmic proposed automated testing of lxd, nocloud-kvm and ec2 platforms
18.5-21-g8ee294d5-0ubuntu1_18.10.1
** Attachment added: "cloud-init-integration-proposed-c-console.log"
EC2 Xenial, Bionic and Cosmic manual test results.
** Attachment added: "ec2-sru-18.5.21.txt"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1813346/+attachment/5244091/+files/ec2-sru-18.5.21.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Xenial proposed automated testing of lxd, nocloud-kvm and ec2 platforms,
18.5-21-g8ee294d5-0ubuntu1_16.04.1
** Attachment added: "cloud-init-integration-proposed-x-console.log"
** Changed in: curtin
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796977
Title:
Ubuntu 18.04 server installation fails
To manage notifications about this bug go
Curtin will pass the MAAS provided network config to the target. In
netplan format, the accept-ra configuration is present and this will be
passed through to the target system and reflected in the installed
system. I'm marking the curtin portion here invalid. If curtin does
need to do
This looks like an issue with the installer. I've added the package to
this bug.
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
I added the shim package to this bug as it appears that your issue is
related to the shim rather than curtin. If you believe that curtin is
related to your issue, please provide additional details about how
curtin is involved in your scenario.
** Also affects: shim (Ubuntu)
401 - 500 of 1546 matches
Mail list logo