** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)
** Changed in: livecd-rootfs (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached is the debdiff to reintroduce the tarball for bionic.
** Patch added: "bionic-1585233.debdiff"
https://bugs.launchpad.net/cloud-images/+bug/1585233/+attachment/5171264/+files/bionic-1585233.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
That change hasn't yet landed in the cosmic archive, so isn't yet
suitable for SRU to bionic.
This new hook will get updated along with all the other tarball
generation when the xattrs change is backported.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
This is still present in bionic (gnome-shell 3.28.2-0ubuntu0.18.04.1).
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734759
I have built an image from -proposed and the .tar.xz was included in the
output; verification done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
B
Public bug reported:
In minimal images, rsyslog is not installed by default; this means that
sshguard will fail to start if installed.
** Affects: sshguard (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Hi shatun,
On Sun, Jul 22, 2018 at 09:15:53AM -, shatun wrote:
> Any chance this will be assigned and fixed any time soon?
This work is in-progress at the moment; you can see the artifacts are
now being produced for cosmic[0]. The next step is a backport to
bionic, which I would anticipate
Public bug reported:
We have explicit release gating in place, which can be relaxed now that
linux-kvm will exist in non-LTS releases.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Assignee: Dan Watkins (daniel-thewatkins)
Status: New
--
You received this bug
I believe the attached patch does the trick; I'll submit it as a branch
once my current branch has landed.
** Patch added: "1775472.patch"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1775472/+attachment/5149495/+files/1775472.patch
--
You received this bug notification becau
I can't remember the exact details, but I believe that this change was
landed to support a CloudStack deployment that didn't support SSH keys
at all. In my ignorance of the broader CloudStack ecosystem, I assumed
that this was true of all CloudStack deployments, so setting it in the
data source ma
** Changed in: cloud-images
Status: In Progress => 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/1747426
Title:
Vagrant <2.x can no longer fetch box metadata from Hashicorp
To m
On Wed, Mar 07, 2018 at 11:42:29PM -, Jason Hobbs wrote:
> Is there a workaround for this? I can just rm /etc/resolv.conf and
> create it with the contents I want, right?
Yep, though you'll need to recreate it every so often as it will be
replaced.
--
You received this bug notification becau
Public bug reported:
(Such as during image builds.)
** Affects: systemd (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: New
** Tags: amd64 apport-bug bionic
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Also affects: linux-kvm (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/1566468
Title:
systemd-modules-load.service: Failing due to missing modu
On Thu, Mar 08, 2018 at 04:30:30PM -, Scott Moser wrote:
> I'm pretty sure that if you you rm /etc/resolv.conf
> and then just write what ever you want in there, it wont get overritten.
>
> mv /etc/resolv.conf /etc/resolv.conf.dist
> echo "nameserver 8.8.8.8" > /etc/resolv.conf
Apologies, I t
Public bug reported:
When the jedi-vim plugin runs colorama.init(), colorama assumes that the
vim.message object which is sys.stdout (and/or sys.stderr) will have a
'closed' attribute. It doesn't which causes the following traceback:
Traceback (most recent call last):
File "/home/daniel/.vim/bu
Public bug reported:
Using google-chrome-stable from Google's upstream repositories, numbers
in the Ubuntu font are rendered strangely. When part of a word, they are
rendered full-height (as I would expect) but when standalone (or part of
a string of numbers), they are rendered at lower-case heigh
On a xenial system, when enabling xenial-proposed and running "apt-get
install squid", I get the below error. Note that I have 'DAEMON=nope' in
/etc/default/squid3 to stop squid3 from starting (because it's only
installed for squid-deb-proxy).
Setting up squid (3.5.12-1ubuntu1) ...
Removing obsole
N.B. This issue doesn't appear in Firefox.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554508
Title:
Numbers rendered at different heights based on word
To manage notifications about this bug go
I have tested all of the above cases with the cloud-init from -proposed
and it behaved as expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Confirmed in trusty, xenial and zesty. ({t,x,z}-ipv6 are just
containers launched from the latest images)
$ lxc exec t-ipv6 cat /etc/hosts
127.0.0.1 localhost
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff
The relevant file is http://bazaar.launchpad.net/~ubuntu-core-dev
/livecd-rootfs/trunk/view/head:/live-build/ubuntu-
cpc/includes.chroot/etc/hosts. This is included wholesale in the images
(because it's in includes.chroot).
--
You received this bug notification because you are a member of Ubuntu
As suggested to me by smoser in #cloud-init, this doesn't actually
reproduce on xenial and yakkety; I'll focus on fixing it in trusty.
** Changed in: cloud-init (Ubuntu Yakkety)
Status: Confirmed => Invalid
** Changed in: cloud-init (Ubuntu Xenial)
Status: Fix Committed => Invalid
** Changed in: cloud-init (Ubuntu Precise)
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/1603222
Title:
Azure: incorrect entry in fstab for ephemeral disk
To manage
** Description changed:
+ [Impact]
+ There is a chance that Azure users' ephemeral disks will not be mounted
properly if the device names change after a reboot.
+
+ [Test Case]
+
+ 1) Provision an Ubuntu VM on Azure (I tested with 14.04.4)
+ 2) The fstab entry for the ephemeral disk (/mnt) corr
I have built a trusty Azure image using -proposed, and confirmed that
this now behaves as expected.
** Tags removed: verification-needed
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Public bug reported:
[Impact]
Anything that cloud-init does to configure the instance may not have
happened before the startup scripts run, or may happen _while_ the
startup scripts are running. The specific example that can happen every
time is mirror configuration. Region-specific mirrors are
** Also affects: gce-compute-image-packages (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: gce-compute-image-packages (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: gce-compute-image-packages (Ubuntu)
Status: In Progress => Fix Rele
On Wed, Jun 07, 2017 at 06:00:32PM -, ChristianEhrhardt wrote:
> I just checked this happens up to artful but I wonder.
> Is anybody using the 2.0 at all?
> I mean it fails right away.
>
> There is also the non 2.0 agent in /usr/sbin/waagent
> Is that what people use?
>
> Do they use the pack
** Also affects: gce-compute-image-packages (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: gce-compute-image-packages (Ubuntu Trusty)
Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)
** Changed in: gce-compute-image-packages (Ubuntu Trusty)
Sta
As per https://wiki.ubuntu.com/gce-compute-image-packages-Updates, I
have created a new image in ubuntu-os-cloud-devel (daily-ubuntu-
console-1404-trusty-v20170424) and run all of our automated testing
against it. The GCE team have confirmed that this image looks good to
them.
** Tags removed: ve
** Changed in: walinuxagent (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603581
Title:
Azure Linux Agent (WALA) 2.1.5 Released
To manage notificatio
** Also affects: walinuxagent (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: walinuxagent (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: walinuxagent (Ubuntu Trusty)
Assignee: (unassigned) => Dan Watkins (daniel-thewatk
My proposed packaging for this can be found at https://git.launchpad.net
/~daniel-thewatkins/ubuntu/+source/gce-compute-image-packages/+git/gce-
compute-image-
packages/commit/?id=d2f044fc635864f4ca24159766c6e2254e98af31
--
You received this bug notification because you are a member of Ubuntu
Bug
Public bug reported:
Per https://cloud.google.com/compute/docs/storing-retrieving-metadata,
the attribute is now instance/attributes/ssh-keys (not sshKeys).
** Affects: cloud-init
Importance: Undecided
Assignee: Dan Watkins (daniel-thewatkins)
Status: In Progress
** Affects
On Mon, Nov 06, 2017 at 11:19:10PM -, ruffsl wrote:
> Could the "current" folder in Index of /core/trusty at https://partner-
> images.canonical.com/core/trusty/ be updated to redirect to 20171102
> instead of 20170817, as it is presently? The docker library ubuntu image
> build is I think poin
I can't reproduce this locally, or in an lxd container; are you sure you
don't have a weird local Python environment that could be causing the
issue?
** Summary changed:
- gsutil stacktraces on artful
+ gsutil tracebacks on artful
** Summary changed:
- gsutil tracebacks on artful
+ gsutil trace
Upon further inspection, this isn't actually a tab-switching issue. Hit
Return a bunch of times, and then Ctrl-L; your prompts will ghost
temporarily. Furthermore, my blinking cursor also ghosts from time to
time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Public bug reported:
Steps to Reproduce:
1) Open gnome-terminal on an external monitor (or move an existing session
there)
2) Open a second tab
3) Produce some output on the current tab
4) Switch to the other tab
Expected Behaviour:
No ghosting.
Actual Behaviour:
The previous content is
** Summary changed:
- Ghosting when switching tabs with "Use transparency from system theme"
enabled on an external monitor
+ Ghosting with "Use transparency from system theme" enabled on an external
monitor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Changed in: cloud-images
Milestone: y-2016-06-02 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573095
Title:
16.04 cloud image hangs at first boot
To manage notifications about this
The latest xenial daily no longer exhibits this issue.
** Changed in: cloud-images
Status: In Progress => 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/1485685
Title:
Users are
We've seen a couple of potential regressions in artful, so we should
hold off on this xenial SRU until we've triaged these:
https://bugs.launchpad.net/cloud-images/+bug/1740176
https://bugs.launchpad.net/cloud-images/+bug/1740178
--
You received this bug notification because you are a member of
snapd has migrated to xenial-updates without this change landing;
unfortunately, that makes snapd uninstallable on powerpc (as that's the
only architecture where it isn't statically compiled). snapd is
installed during image builds, so this migration is currently blocking
powerpc cloud images from
Public bug reported:
The GCE image build process currently installs gce-compute-image-
packages (amongst others) with --no-install-recommends. We would like
to be able to install Recommends, but including libpam-cracklib on the
image would represent a substantial change in behaviour for users.
*
I've followed the steps Chris gave above, and have confirmed that the
vagrant user is the default via SSH. The ubuntu user also exists, and
is in the appropriate groups.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
I can confirm that this is happening, and it's in the output that comes
from the buildds, so it's a livecd-rootfs/live-build bug.
(It's probably the former, so adding that package to this bug.)
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received t
This doesn't exhibit in xenial.
** Changed in: cloud-images
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/1711735
Title:
source.list for armhf includes trusty-securi
This was fixed for xenial in bug 1513529 and bug 1679252.
(Specifically, the former refactored sources.list generation
significantly and in a way which broke non-x86 architectures, and the
latter remedied that.)
Unfortunately, the changes to sources.list generation were fairly major,
so I don't th
The fix in bug 1679252 uses LB_PARENT_MIRROR_BINARY_SECURITY for
security lines (where currently trusty uses LB_PARENT_MIRROR_BINARY; I
don't _think_ this should work because LB_PARENT_MIRROR_BINARY is used
for the other sources.list lines which are fine, but it's worth a try.
Commit with that cha
I still think we should fix this in Ubuntu, just not with the full fix
from the aforementioned bugs. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711735
Title:
source.list for armhf includes tr
Public bug reported:
```
$ aws ec2 run-instances --image-id ami-720ae90a --instance-type t2.micro
--region us-west-2 --key canonical
'AWSHTTPSConnection' object has no attribute 'ssl_context'
```
** Affects: awscli (Ubuntu)
Importance: Undecided
Status: New
--
You received this
** Bug watch added: Debian Bug tracker #854382
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854382
** Also affects: awscli (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854382
Importance: Unknown
Status: Unknown
--
You received this bug notification because
On Wed, Aug 23, 2017 at 07:10:16PM -, ruffsl wrote:
> Hello Dan, was your latest commit successful in building a cloud image with a
> patched source list?
> https://git.launchpad.net/~daniel-thewatkins/ubuntu/+source/livecd-rootfs/commit/?id=1bc0b2eec50726f46510df4a340d2f27f62756bb
The packag
artful; I see there is a new version that I'm installing (along with a
million other things), so I'll see if the fix is included there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712364
Title:
'
Unfortunately my change didn't fix the issue; I'll revisit this soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711735
Title:
source.list for armhf includes trusty-security which does not exist
It is! \o/
** Changed in: awscli (Ubuntu)
Status: Incomplete => 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/1712364
Title:
'AWSHTTPSConnection' object has no attribute 'ssl_co
(Filing this in Ubuntu even though it's being tracked in Debian, because
I think this will be a papercut for a number of users if it ends up in
artful.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17
Public bug reported:
This was removed in my most recent upgrade on artful, 1:2.11.0-4 ->
1:2.14.1-1ubuntu3.
This is particularly frustrating as it caused a bunch of git operations
to start erroring for me, as I have the following in my .gitconfig:
[pager]
diff = perl /usr/share/doc/git/c
https://github.com/git/git/commit/0c977dbc8180892af42d7ab9235fd3e51d6c4078
introduced the need to run the diff-highlight Makefile to build diff-
highlight.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
I've successfully built new images with the livecd-rootfs in xenial-
proposed.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Public bug reported:
With the following cloud-config:
```
#cloud-config
bootcmd:
- touch /tmp/cloud-init-works
```
I see the following traceback in the cloud-init log when I launch a GCE
artful instance:
```
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/cm
The following reproduces (but produces an instance which I can't SSH in
to; I had to capture the boot disk to discover this):
```
$ cat << EOF > cfg
bootcmd:
- touch /tmp/cloud-init-works
EOF
gcloud compute instances create aa-$(date +%y%m%d-%H%M) --image
daily-ubuntu-alan-1710-artful-v20170915a
Ah, yeah, I mis-copied in my reproduced, but I was using cloud config
with #cloud-config when actually running this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717598
Title:
Traceback when passi
This bug is for _project-level_ SSH keys, bug 1693582 is for _instance-
level_ SSH keys.
** This bug is no longer a duplicate of bug 1693582
cloud-init uses a deprecated metadata path for GCE instance SSH keys
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
This was fixed upstream in
https://github.com/s3tools/s3cmd/commit/97482c283d61c937d26d45e1963e9dd72d40f328
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718948
Title:
Traceback when running `s3cmd
Public bug reported:
!
An unexpected error has occurred.
Please try reproducing the error using
the latest s3cmd code from the git master
branch found at:
https://github.com/s3tools/s3cmd
and have a look at the known issues list:
https:/
Public bug reported:
A short backtrace:
Thread 1 (Thread 0x77f948c0 (LWP 3606)):
#0 0x5562ee0e in cmd_parse_expunge (s=0x55a1a8a2 "42 EXPUNGE",
idata=0x55a13f60) at ../../../imap/command.c:209
#1 0x5562ee0e in cmd_handle_untagged (idata=0x55a13f60) at
../../../
This is mutt 1.8.3+neomutt20170609-2build1 on artful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719318
Title:
mutt segfaults in cmd_parse_expunge
To manage notifications about this bug go to:
This continues to be a real pain in day-to-day. Can we please fix this
gnome-terminal regression?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726439
Title:
Link copied with "Copy Link Address" c
** Also affects: vagrant (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/1747426
Title:
Error downloading box trusty64 metadata
To manage notifica
It looks like Hashicorp have discontinued the atlas.hashicorp.com API
endpoints used by the version of Vagrant in every Ubuntu release (in
favour of vagrantcloud.com).
I've confirmed that this is fixed in the version of Vagrant in bionic-
proposed:
# vagrant box add 'ubuntu/trusty64'
==> box: Loa
** Summary changed:
- Error downloading box trusty64 metadata
+ Vagrant <2.x can no longer fetch box metadata from Hashicorp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747426
Title:
Vagrant <2.
So this looks like it may not be an issue in trusty, because I believe
that predates Atlas/Vagrant Cloud in their entirety. I'm preparing
patches for xenial/artful.
** Also affects: vagrant (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: vagrant (Ubuntu Xenial)
Im
** Description changed:
+ [Impact]
+
+ As of February 2nd, the legacy Vagrant Cloud URLs were disabled by
+ Hashicorp[0], meaning that the versions of vagrant in xenial and artful
+ can no longer fetch Vagrant boxes from the global index (which is a
+ fundamental part of Vagrant use).
+
+
+ [0]
The attached photo displays what I end up stuck with.
** Attachment added: "20180207_165829.jpg"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1748029/+attachment/5050935/+files/20180207_165829.jpg
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug noti
Public bug reported:
I have an external monitor in portrait mode, which means that the top of
my external monitor is substantially above my laptop monitor (which has
the top bar). If I move a window by holding Meta and dragging it from
the bottom, and accidentally let go with the window overlappi
Hi Po-Hsu,
Could you confirm the serial of the image that you are seeing this in?
Are you able to test older serials to determine when we started seeing
the failure?
Thanks,
Dan
** Also affects: cloud-images
Importance: Undecided
Status: New
--
You received this bug notification be
On Wed, Feb 14, 2018 at 08:13:11AM -, Po-Hsu Lin wrote:
> So I think the bug status should be Fix Committed now?
I think this is actually fixed now; can you confirm?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
On Fri, Nov 24, 2017 at 10:23:18AM -, Egmont Koblinger wrote:
> Maybe related to bug 1726262?
It certainly sounds similar and, indeed, I can reproduce that on my
external monitor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
I can reproduce this on 17.10, but only on my external monitor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726262
Title:
17.10 - flickering overlay patterns in gnome-terminal
To manage notifica
Public bug reported:
I know that we effectively repackaged xe-guest-utilities between xenial
and artful. As part of that, the previous dependency on xenstore-utils
was dropped.
This is causing some problems for Xen-based partners/customers, who
would like xenstore-utils installed in their images
Public bug reported:
I just accidentally hit Meta-P and was extremely confused by the result.
As I only tapped it, I didn't see the on-screen menu, and my displays
were suddenly configured completely differently (both resolution _and_
orientation).
Furthermore, when I used Meta-P to switch back t
On Wed, Jan 17, 2018 at 03:32:32PM -, Scott Moser wrote:
> I'm curious why you would use the .vhd file. Is there something
> specific that you wanted from it *other* than the format of the disk
> image?
The VHD contains Hyper-V-specific customisations (such as the
linux-azure kernel), so ther
As I mentioned in comment #2, this can be worked around. The issue is
that GDM3 assumes that it can get an inotify watch and degrades
ungracefully when it can't.
** Summary changed:
- After a period of locked inactivity, gdm3 no longer lets me unlock my session
["No space left on device"]
+ gdm
Added the cloud-images project so we can more easily track this.
** Also affects: cloud-images
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/1746806
Title:
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629797
Title:
cloud-init seems to take most
The really time-consuming part seems to be this on EC2:
Oct 03 08:45:10 ubuntu cloud-init[1015]: [CLOUDINIT] handlers.py[DEBUG]: start:
init-network/search-GCE: searching for network data from DataSourceGCE
Oct 03 08:45:10 ubuntu cloud-init[1015]: [CLOUDINIT] __init__.py[DEBUG]: Seeing
if we can
For reference, a couple of EC2 image types give:
Startup finished in 9.548s (kernel) + 2min 55.205s (userspace) = 3min 4.753s
Startup finished in 6.911s (kernel) + 2min 21.522s (userspace) = 2min 28.434s
And GCE gives:
Startup finished in 6.661s (kernel) + 1min 30.434s (userspace) = 1min
37.095
(This bug seems to reproduce on every boot (not just first boot), which
at least makes debugging easier.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629797
Title:
cloud-init seems to take most o
Pretty much all that happens between logging "Seeing if we can get any
data from " in
cloudinit.sources and
"http://metadata.google.internal/computeMetadata/v1/ is not resolvable"
in cloudinit.sources.DataSourceGCE is that we attempt to resolve that
address.
So, my first guess is that something we
OK, my instrumented code[0] produces this, which seems to confirm my
hypothesis that DNS resolution is being weirdly slow:
Oct 03 09:23:06 ip-172-31-3-216 cloud-init[1041]: [CLOUDINIT]
__init__.py[DEBUG]: Seeing if we can get any data from
Oct 03 09:23:06 ip-172-31-3-216 cloud-init[1041]: [CLOUD
It is perhaps noteworthy that each failed resolution there appears to
take exactly 25 seconds. This would also explain the GCE boot time
being lower than EC2. Not only is the GCE resolution successful on GCE
(gaining 25 seconds) but the EC2 metadata source actually checks http
://instance-data.:8
The above log and tests were on EC2.
On GCE, an instrumented xenial gives:
Oct 03 09:40:43 xenial-161003-0956 cloud-init[1318]: [CLOUDINIT]
__init__.py[DEBUG]: Seeing if we can get any data from
Oct 03 09:40:43 xenial-161003-0956 cloud-init[1318]: [CLOUDINIT]
util.py[DEBUG]: Checking DNS redir
LP cuts off the conclusions in my previous comment, which were:
So it definitely looks like DNS resolution failure taking 25 seconds is
A Thing (TM). It's also taking 25 seconds on both EC2 and GCE, which
suggests the issue is somewhere in Ubuntu. It also is extremely unlikely
to be that networkin
In yakkety, a "resolve" service has been added to the hosts line in
nsswitch.conf[0]. Removing this service fixes the boot time issue.
[0] http://paste.ubuntu.com/23269859/ is the diff of nsswitch.conf between
xenial and yakkety.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Adding After=systemd-resolved.service to /lib/systemd/system/cloud-
init.service causes the following in journalctl:
Oct 03 12:05:04 yakkety-161003-0945 systemd[1]: basic.target: Found ordering
cycle on basic.target/start
Oct 03 12:05:04 yakkety-161003-0945 systemd[1]: basic.target: Found depende
Public bug reported:
When running `duply foo backup`, I get prompted for my GPG passphrase
despite it being configured in my conf file. Using GPG=gpg1 fixes this
issue, which suggests that the switch to gpg2 in yakkety is involved in
this breakage.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Pa
To determine if this has been fixed, boot an image that has the GCE data
source enabled (e.g. the image from cloud-images.ubuntu.com) but not on
GCE. Examine the output of `journalctl` and look for the following
lines:
Oct 07 16:17:39 ubuntu cloud-init[1009]: [CLOUDINIT] __init__.py[DEBUG]: Seein
Hmm, that seems like the obvious thing to have done now you say it.
Attached.
** Patch added: "lp1590751.debdiff"
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1590751/+attachment/4684839/+files/lp1590751.debdiff
** Changed in: walinuxagent (Ubuntu Trusty)
Status: Incompl
501 - 600 of 1034 matches
Mail list logo
