** Changed in: cloud-images
Milestone: y-2016-06-02 => y-2016-06-16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581044
Title:
Images ship with modified conffiles
To manage notifications
** Branch unlinked: lp:~philroche/cloud-init/trunk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581200
Title:
Ubuntu cloud-init expects trailing dot on GCE metadata FQDN
To manage notifications
** Branch unlinked: lp:~philroche/cloud-init/trunk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581200
Title:
Ubuntu cloud-init expects trailing dot on GCE metadata FQDN
To manage notifications
** Changed in: cloud-init (Ubuntu)
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/1581200
Title:
Ubuntu cloud-init expects trailing dot on GCE metadata FQDN
** Changed in: cloud-images
Status: In Progress => 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/1581044
Title:
Images ship with modified conffiles
To manage notifications
** Changed in: cloud-init (Ubuntu Trusty)
Assignee: (unassigned) => Philip Roche (philroche)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581200
Title:
Ubuntu cloud-init expects trailing
smoser has included the fix for this bug in cloud-init for 16.04 but the
attached lp-1581200-gce-metadatafqdn.debdiff patch is still awaiting
sponsorship for inclusion in cloud-init for 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: cloud-images
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/1581044
Title:
Images ship with modified conffiles
To manage notifications
** Changed in: cloud-images
Milestone: y-2016-07-14 => y-2016-07-28
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581044
Title:
Images ship with modified conffiles
To manage notifications
Hi Nish,
lp:1595302 targets Xenial and Yakkety only. The fix needs to be
backported to Trusty too. Patch attached to #3 is for Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581200
Title:
Attached patch has been tested and fixes the reported issue.
** Description changed:
+ [Impact]
+
+ * If bind9 is installed and configured as a local DNS server on an
+ ubuntu instance on GCE then on every reboot cloud-init will fail to
+ retrieve instance metadata from GCE due to the lookup
** Changed in: cloud-init (Ubuntu Trusty)
Status: New => 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/1581200
Title:
Ubuntu cloud-init expects trailing dot on GCE metadata FQDN
** Changed in: cloud-images
Milestone: y-2016-06-30 => y-2016-07-14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581044
Title:
Images ship with modified conffiles
To manage notifications
Correction:
gce-compute-image-packages in trusty-proposed has been verified.
A new _Trusty_ GCE image was built with proposed enabled and tested both
manually and by our automated testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
gce-compute-image-packages in trusty-proposed has been verified.
A new Xenial GCE image was built with proposed enabled and tested both
manually and by our automated testing.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you
** Changed in: gce-compute-image-packages (Ubuntu Yakkety)
Status: New => Fix Released
** Changed in: gce-compute-image-packages (Ubuntu Yakkety)
Assignee: (unassigned) => Philip Roche (philroche)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This has now been verified successfully manually and with automated
testing. I have tagged this bug verification-done
** 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
** Patch removed: "lp1667277-fix-shutdown-script-ordering-upstart.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1667277/+attachment/4825143/+files/lp1667277-fix-shutdown-script-ordering-upstart.debdiff
** Patch added:
** Description changed:
+ [Impact]
+
+ * Trusty images with gce-compute-image-packages package installed do
+ not run shutdown scripts.
+
+ [Test Case]
+
+ We have a number of automated tests that run against all GCE builds that
+ include this package.
+
+ * There are numerous tests:
+*
Assignee: Philip Roche (philroche)
Status: In Progress
** Changed in: gce-compute-image-packages (Ubuntu)
Assignee: (unassigned) => Philip Roche (philroche)
** Changed in: gce-compute-image-packages (Ubuntu)
Status: New => In Progress
--
You received this bug notification b
The above patch has passed all internal tests and been verified by the
GCE team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667277
Title:
Shutdown scripts do not run on 1404 images with
Fix where GCE shutdown scripts are run during shutdown when using
Upstart
** Patch added: "lp1667277-fix-shutdown-script-ordering-upstart.debdiff"
Updated patch using correct version number 20160930-0ubuntu3~14.04.1
** Patch added: "lp1667277-fix-shutdown-script-ordering-upstart.debdiff"
Please find attached patch for this bug. This is the same fix as
upstream (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806676
and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809344)
The patch adds "pool" to the "server" and "peer" list as well as
handling tabs and spaces in the
The issue if a broken set of NTP servers is received and having no
fallback is the case in Yakkety now too though and previously in Xenial
prior to the server/pool changeover in 1:4.2.8p3+dfsg-1.
I agree that ideally there would be a fallback if the received NTP
servers were broken but this bug
Public bug reported:
In 1:4.2.8p3+dfsg-1, the default config was changed to
"Use pool instead of server". This needs a corresponding
update to /etc/dhcp/dhclient-exit-hooks.d/ntp, since the
DHCP specified servers now get added to the default pool
config instead of replacing them.
This affects
Public bug reported:
GCE bug (lp:1639089) reported that NTP was misconfigured.
In ntp 1:4.2.8p3+dfsg-1, the default config was changed to
"Use pool instead of server".
This needs a corresponding change to gce-cloud-config since
the default servers it attempt to comment out no longer exist
as
This was marked as wont-fix due to gce-cloud-config being deprecated in
favour of gce-compute-image-packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656899
Title:
ntp: changing the default
gce-compute-image-packages in xenial-proposed has been verified.
A new Xenial GCE image was built with proposed enabled and tested both
manually and by our automated testing.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you
.html
** Changed in: gce-compute-image-packages (Ubuntu)
Assignee: (unassigned) => Philip Roche (philroche)
** Changed in: gce-compute-image-packages (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
to use or mimic here: https://github.com/GoogleCloudPlatform
/compute-image-
packages/blob/master/google_compute_engine_init/systemd/postinst.sh
** Affects: gce-compute-image-packages (Ubuntu)
Importance: Undecided
Assignee: Philip Roche (philroche)
Status: Confirmed
--
You re
** Changed in: gce-compute-image-packages (Ubuntu)
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/1667277
Title:
Shutdown scripts do not run on 1404
Apologies I forgot to include the version of cloud-init tested.
The version tested was 0.7.5-0ubuntu1.20
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581200
Title:
Ubuntu cloud-init expects
I have tested the proposed package and it behaves as expected and fixes
the reported issue.
** 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.
Hi Max, this is not intentional. I will investigate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581200
Title:
Ubuntu cloud-init expects trailing dot on GCE metadata FQDN
To manage
Hi Max,
When proposed pocket is enabled [1] then 0.7.5-0ubuntu1.20 [2] can be
installed.
This does include the patch.
The cloud-init_0.7.5.orig.tar.gz source archive linked to on [3] is the
source archive before patches are applied.
[1] https://wiki.ubuntu.com/Testing/EnableProposed
[2]
Merge proposal created for Ubuntu 16.10 Yakkety
https://code.launchpad.net/~philroche/ubuntu/+source/gce-compute-image-
packages/+git/gce-compute-image-packages/+merge/311821
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Merge proposal created for Ubuntu 16.04 Xenial
https://code.launchpad.net/~philroche/ubuntu/+source/gce-compute-image-
packages/+git/gce-compute-image-packages/+merge/311824
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Merge proposal created for Ubuntu 14.04 Trusty
https://code.launchpad.net/~philroche/ubuntu/+source/gce-compute-image-
packages/+git/gce-compute-image-packages/+merge/311823
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
- * GCE no longer wish to use gce-utils and instead want to use the new
+ * GCE no longer wish to use gce-utils and instead want to use the new
gce-compute-image-packages package
- * All supported versions of Ubuntu on GCE should have gce-compute-
+
debdiff attached for Yakkety
** Patch added: "fix-startup-script-ordering-yakkety"
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1643585/+attachment/4782925/+files/fix-startup-script-ordering.debdiff
--
You received this bug notification because you are a member
tu-os-cloud-devel/daily-ubuntu-testing-1610-yakkety-v20161110"
** Affects: gce-compute-image-packages (Ubuntu)
Importance: Undecided
Assignee: Philip Roche (philroche)
Status: In Progress
** Changed in: gce-compute-image-packages (Ubuntu)
Status: New => In Progres
This seems to be somewhat related to https://bugs.launchpad.net/cpc-
gce/+bug/1639089 (only affects Xenial).
In summary the "pool" entries in ntp.conf should be commented out by
gce-cloud-config but when ntp.conf transitioned from using "server" to
"pool" gce-cloud-config was not updated.
I will
Testing performed using 20160930-0ubuntu3~16.10.0 of Yakkety from
proposed.
All tests pass.
** 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.
Images with cloud-init version 0.7.8-49-g9e904bb-0ubuntu1~16.04.3 are
now available at https://partner-images.canonical.com/cpc-
cloudsigma/releases/xenial/20161221/
Please can you validate that this fixes the datasource issue.
--
You received this bug notification because you are a member of
gce-compute-image-packages version 20160930-0ubuntu6 in zesty-proposed
has been verified.
For reference attached testplan was used for verification.
** Attachment added: "gce-compute-image-packages-zesty-testplan-proposed.txt"
gce-compute-image-packages version 20160930-0ubuntu6~16.04.0 in xenial-
proposed has been verified.
For reference attached testplan was used for verification.
** Attachment added: "gce-compute-image-packages-xenial-testplan-proposed.txt"
gce-compute-image-packages version 20160930-0ubuntu3~14.04.2 in trusty-
proposed has been verified.
For reference attached testplan was used for verification.
** Attachment added: "gce-compute-image-packages-trusty-testplan-proposed.txt"
gce-compute-image-packages version 20160930-0ubuntu6~16.10.0 in yakkety-
proposed has been verified.
For reference attached testplan was used for verification.
** Attachment added: "gce-compute-image-packages-yakkety-testplan-proposed.txt"
Attached lp1668327-no-restart-of-startup-shutdown-scripts-on-upgrade-
xenial.debdiff fixes this bug for Xenial
** Patch added:
"lp1668327-no-restart-of-startup-shutdown-scripts-on-upgrade-xenial.debdiff"
Attached lp1668327-no-restart-of-startup-shutdown-scripts-on-upgrade-
zesty.debdiff fixes this bug for Zesty
** Patch added:
"lp1668327-no-restart-of-startup-shutdown-scripts-on-upgrade-zesty.debdiff"
Attached lp1668327-no-restart-of-startup-shutdown-scripts-on-upgrade-
xenial.debdiff fixes this bug for Xenial
** Patch added:
"lp1668327-no-restart-of-startup-shutdown-scripts-on-upgrade-xenial.debdiff"
** Description changed:
+ [Impact]
+
+ * This bug affects: Zesty, Yakkety, Xenial and Trusty
+
+ * When a user upgrades to a newer version of gce-cimpute-image-packages
+then the google-startup-scripts service is run which causes any configured
+startup scripts to be executed.
+
+
Attached lp1668327-no-restart-of-startup-shutdown-scripts-on-upgrade-
yakkety.debdiff fixes this bug for Yakkety
** Patch added:
"lp1668327-no-restart-of-startup-shutdown-scripts-on-upgrade-yakkety.debdiff"
Merge proposals created:
Master/Zesty:
https://code.launchpad.net/~philroche/ubuntu/+source/gce-compute-image-packages/+git/gce-compute-image-packages/+merge/320377
Yakkety:
Attached lp1668327-no-restart-of-startup-shutdown-scripts-on-upgrade-
trusty.debdiff fixes this bug for Trusty
** Patch added:
"lp1668327-no-restart-of-startup-shutdown-scripts-on-upgrade-trusty.debdiff"
Merge proposal created for Trusty:
https://code.launchpad.net/~philroche/ubuntu/+source/gce-compute-image-packages/+git/gce-compute-image-packages/+merge/320620
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi mterry.
RE: test case steps.
This surfaced for me initially while testing on GCE. On GCE NTP servers
are provided via DHCP so the easiest test case is to launch an instance
on GCE without our workaround configured.
One such image is "daily-ubuntu-ntpdebug-1604-xenial-v20170331" in
project
** Description changed:
In 1:4.2.8p3+dfsg-1, the default config was changed to
"Use pool instead of server". This needs a corresponding
update to /etc/dhcp/dhclient-exit-hooks.d/ntp, since the
DHCP specified servers now get added to the default pool
config instead of replacing them.
I have verified that ntp 1:4.2.8p4+dfsg-3ubuntu5.4 in xenial-proposed
passes the test case outlined in the description above.
* Launch GCE instance
* Enabled proposed
* Upgrade ntp
* Reboot
* Confirm `ntpq -p` returns only one entry
** Tags removed: verification-needed
** Tags added:
Trusty packages have been verified.
All automated tests pass for these suites using images built from
proposed.
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this bug notification because you are a
Xenial and Zesty packages have been verified.
All automated tests pass for these suites using images built from
proposed.
Trusty verification still in progress.
** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-done-xenial verification-done-zesty
For completeness I confirm that the automated tests also passed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1703647
Title:
google-compute-engine-oslogin 20170622-0ubuntu1~14.04.0 installation
Testing complete and verified for Trusty.
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700027
Testing complete and verified for Xenial. Testing of other releases is
still in progress.
** 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.net/bugs/1700027
Title:
Testing complete and verified for Yakkety. Testing of other releases is
still in progress.
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700027
Title:
Testing complete and verified for Zesty. Testing of other releases is
still in progress.
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700027
Title:
Update
Trusty, Xenial, Yakkety and Zesty packages have been verified.
All automated tests pass for these suites and manual verification has
also been completed using images built from proposed and also on
instances upgrading packages already installed.
** Tags removed: verification-needed
** Tags
Trusty, Xenial, Yakkety and Zesty packages have been verified.
All automated tests pass for these suites using images built from
proposed.
** Tags removed: verification-needed
** Tags added: verification-done-trusty verification-done-xenial
verification-done-yakkety verification-done-zesty
--
Trusty, Xenial, Yakkety and Zesty packages have been verified.
All automated tests pass for these suites and manual verification has
also been completed using images built from proposed and also on
instances upgrading packages already installed.
** Tags removed: verification-needed
** Tags
Automated tests for image validation have passed for both Xenial and
Zesty. Trusty tests still in progress. There are WALinux agent tests as
part of this suite that test that the agent is running and that there
has been no regressions wrt SSH config.
** Tags added: verification-done-xenial
Automated tests for image validation have now passed for Trusty.
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714299
Title:
walinuxagent update 2.2.16
To
I had the same issue. For me the issue was caused by a recent install of
EasyScreenCast gnome extension. I deleted the extension from
/home/$USER/.local/share/gnome-shell/extensions/ and was then able to
log in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have verified that building the Xenial cloud images using this branch of
livecd-rootfs with minimized flag results in
`build_name: minimal` in /etc/cloud/build.info.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
Given https://gitlab.gnome.org/GNOME/glib/commit/0d69462 referred to
above it does look like an intentional change and nothing to do with
udisks2. Please close if this is the case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also refer you to https://gitlab.gnome.org/GNOME/glib/commit/0d69462
which seems to be the cause.
https://gitlab.gnome.org/GNOME/nautilus/issues/312 refers to this too
but I have experienced this in Caja too, not just nautilus.
--
You received this bug notification because you are a member of
Public bug reported:
Apologies if this is not the correct package to file this bug/regression
against.
On my 18.04 desktop installs (Gnome shell and Ubuntu Mate) when mounting
network shares (SMB and NFS) they no longer appear under Devices in file
manager (Nautilus or Caja), the mounts do
I have verified gce-compute-image-packages version
20180510+dfsg1-0ubuntu4~18.04 in bionic.
All automated tests and manual tests passed.
Tests confirm expected services are running too.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this
Trusty image with gce-compute-image-packages
20180510+dfsg1-0ubuntu3~14.04.3 now published as "daily-ubuntu-gceip-
ppa-1404-trusty-v20180611" in project "ubuntu-os-cloud-devel". All
automated tests and manual tests passed.
@GCE-team, please can you verify these images before we proceed with
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770650
Title:
Update google
I have verified gce-compute-image-packages version
20180510+dfsg1-0ubuntu3~16.04 in xenial.
All automated tests and manual tests passed.
Tests confirm expected services are running too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have verified gce-compute-image-packages version
20180510+dfsg1-0ubuntu3~17.10 in artful.
All automated tests and manual tests passed.
Tests confirm expected services are running too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The following test images have been created with the proposed version of
gce-compute-image-packages:
daily-ubuntu-testing-1804-bionic-v20180525 in project ubuntu-phil
daily-ubuntu-testing-1604-xenial-v20180529 in project ubuntu-phil
daily-ubuntu-testing-1710-artful-v20180529 in project
Trusty image with gce-compute-image-packages
20180510+dfsg1-0ubuntu3~14.04.2 now published as "daily-ubuntu-gceip-
verify-1404-trusty-v20180530a" in project "ubuntu-os-cloud-devel". All
automated tests and manual tests passed.
In summary:
The following test images have been created with the
I too have verified the GCE bionic images with cloud-init 18.2-27
(currently in bionic-proposed) in europe-west region. 20 of 20 launched
successfully.
Nice work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
We (Canonical CPC) are seeing an issue with today's build of the bionic
minimal cloud images. Boot stops at "Starting Initial cloud-init job
(metadata service crawler)..." for nearly 5 minutes (booting on
scalingstack and locally with kvm) this is with a new kernel, but
Trusty, Xenial and Artful packages have been verified.
All automated tests pass for these suites using images built from
proposed.
Images are available for testing:
* Trusty: "daily-ubuntu-gcip-sru-1404-trusty-v20180201" in project
"ubuntu-os-cloud-devel"
* Xenial:
Trusty, Xenial and Artful packages have been verified.
All automated tests pass for these suites using images built from
proposed.
Images are available for testing:
* Trusty: "daily-ubuntu-gcip-sru-1404-trusty-v20180201" in project
"ubuntu-os-cloud-devel"
* Xenial:
I have verified xenial using a locally created test image.
Test image [1] was created using ubuntu-old-fashioned [2] and the
proposed branch of livecd-rootfs.
[1]
https://private-fileshare.canonical.com/~philroche/unminimize-verification-20180704/xenial/
[2]
The meta-packages have been rolled back and the fix is in progress of
being applied and uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779961
Title:
Boot delays with 4.15.0-24 based
I have verified bionic using a locally created test image.
Test image [1] was created using ubuntu-old-fashioned [2] and the
proposed branch of livecd-rootfs.
[1]
https://private-fileshare.canonical.com/~philroche/unminimize-verification-20180704/bionic/
[2]
I have verified xenial using a locally created test image.
Test image [1] was created using ubuntu-old-fashioned [2] and the
proposed branch of livecd-rootfs.
[1]
https://private-fileshare.canonical.com/~philroche/unminimize-verification-20180704/xenial/
[2]
Public bug reported:
We (CPC) are seeing failures when building 18.04 minimal images with the
following errors.
deb http://ppa.launchpad.net/canonical-foundations/hyperv-staging/ubuntu bionic
main
E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is
required for this
** Attachment removed: "/buildlog_ubuntu_bionic_amd64_cpc_BUILDING.txt"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1753945/+attachment/5071406/+files/buildlog_ubuntu_bionic_amd64_cpc_BUILDING_failure.txt
** Description changed:
We (CPC) are seeing failures when building
Myself and @kamalmostafa spoke and the issue is not obvious especially
as linux-azure is installed in the base image too which does not exhibit
the issue.
Although not obvious @kamalmostafa did suspect the issue to lie
somewhere with random number generation and a related package/kernel
patch.
@kamalmostafa @mhcerri
I noticed that linux-azure 4.18.0.1003.3 was uploaded to cosmic-proposed
so I built a new test image.
For convenience I have imported your SSH keys to 'ssh
ubuntu@51.140.217.58'.
All logs and VHD etc. have been uploaded to https://private-
** Attachment added: "cosmic minimal image with linux-azure 4.18.0.1002.2 (from
cosmic-proposed) boot log"
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+attachment/5195337/+files/chohv4Va7Ahx7-vm-imagedebug-boot.log
--
You received this bug notification because you are
On request on IRC I have tried a new image with linux-azure
4.18.0.1002.2 from cosmic-proposed.
This too exhibited the slow boot
5min 19.070s (kernel) + 41.724s (userspace) = 6min 794ms
Full logs @ https://private-fileshare.canonical.com/~philroche/azure-
cosmic-20181001/
--
You received this
Public bug reported:
Hi,
We're planning to share a new Cosmic minimal image for Azure including
the linux-azure custom kernel.
I have found boot speed increase from ~55s in non minimal image to over
6mins for minimal image.
I have gathered boot log, systemd logs and cloud-init logs for this
On guidance from raharper I have opened new bug for this @
https://bugs.launchpad.net/cloud-init/+bug/1822353
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766287
Title:
18.04 minimal images on
1 - 100 of 179 matches
Mail list logo
