I have verified fix in amd64 xenial VM.
Test case:
* `sudo apt install python3-virtualenv virtualenv python-virtualenv`
* Confirm that any `pip` operations fail as per bug description
* `virtualenv -p /usr/bin/python3 venv/py3 --verbose`
* `source ./venv/py3/bin/activate`
* `pip list`
* Ena
I also verified the fix with a python2 virtualenv.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912248
Title:
virtualenv on xenial: easy_install syntax error
To manage notifications about this bu
@sil2100 We have now successfully tested reboot with grub-efi-
amd64-signed 1.167~16.04.2+2.04-1ubuntu44 from xenial-proposed with
image ubuntu-1604-xenial-v20200429 in GCE
And I confirmed the bug with grub-efi-amd64-signed
1.66.23+2.02~beta2-36ubuntu3.23 prior to testing
Marking verification-don
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
otherw
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 kernel
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] https://github.com/chrisglass/ubuntu-
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] https://github.com/chrisglass/ubuntu-
@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-
fileshare.canonical.com/~philroch
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.
On
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
** 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
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
ins
I'd like to reopen this following Disco minimal images failing to set up
networking due to similar reasons to this bug with the only difference
being that no nic was found.
A workaround was found to set up cloud-init service config:
/etc/systemd/system/cloud-init-local.service.d/gcp.conf
```
[Un
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 GCE
Public bug reported:
Following some debug of the docker.io package in universe, we (Canonical
CPC) discovered that the ubuntu-fan package from main and the netcat-
traditional package from universe were being installed.
This was due to the following dependency/recommends tree:
* docker.io (in un
It appears that a bug was already filed against netcat
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1780316
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861704
Title:
ubuntu-fan
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 ho
** 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 abou
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.
https://bugs.launchpad.
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
--
Thank you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840135
Title:
Request for new Eoan build of python-simplestreams
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
Public bug reported:
Following the merge of MP
https://code.launchpad.net/~philroche/simplestreams/+git/simplestreams/+merge/369682
would it be possible to get a new build of simplestreams published to
Eoan?
This change might not be SRUable as it could change behavior that
current users are alrea
This is being tracked in setuptools upstream too
https://github.com/pypa/setuptools/issues/2541
The cause is that python-virtualenv is pulling in setuptools 51.3.3
`virtualenv -p /usr/bin/python3 venv/py3 --verbose`
```
snip...
Installing setuptools, pkg_resources, pip, wheel...
Collecti
I have found the following workaround on Ubuntu 16.04 Xenial
Do not install setuptools on virtualenv creation:
`virtualenv -p /usr/bin/python3 venv/py3 --verbose --no-setuptools`
Install a supported setuptools version after virtualenv creation and
activation:
`python3 -m pip install --upgrade '
@stefanor
Thanks for the explanation.
I have a one liner workaround now:
```
virtualenv -p /usr/bin/python3 venv/py3 --verbose --no-download && .
venv/py3/bin/activate && python3 -m pip install --upgrade 'setuptools;
python_version >= "3.6"' 'setuptools<51.3.0; python_version < "3.6" and
pyth
Public bug reported:
We want to the revert of initramfs package removal in KVM image.
[Impact]
* We don't want any packages marked for auto-removal on a published kvm
cloud image.
[Test Case]
* Perform livefs build with project ubuntu-base
* Boot *-disk-kvm.img using kvm
* Confirm it bo
** Description changed:
- We want to the revert of initramfs package removal in KVM image.
+ No packages marked for auto-removal should be present in a published
+ cloud image.
+
+ The current kvm binary hook in livecd-rootfs removes the packages
+ `initramfs-tools` and `busybox-initramfs`. This
debdiff for focal SRU
** Patch added: "lp-1880170-kvm-revert-of-initramfs-package-removal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+attachment/5375692/+files/lp-1880170-kvm-revert-of-initramfs-package-removal.debdiff
--
You received this bug notification
debdiff for eoan SRU
** Patch added:
"lp-1880170-kvm-revert-of-initramfs-package-removal-eoan.debdiff"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+attachment/5375695/+files/lp-1880170-kvm-revert-of-initramfs-package-removal-eoan.debdiff
--
You received this bug not
debdiff for focal SRU rev2. Building package without extraneous contents
as per https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html
#build-noextra
** Patch added:
"lp-1880170-kvm-revert-of-initramfs-package-removal-focal-rev2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/livecd-r
debdiff for eoan SRU rev2. Building package without extraneous contents
as per https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html
#build-noextra
** Patch added:
"lp-1880170-kvm-revert-of-initramfs-package-removal-eoan-rev2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/livecd-roo
Verification of livecd-rootfs 2.620.3 in eoan -proposed completed.
The following verification was completed.
* Perform livefs build with project ubuntu-base
* Boot *-disk-kvm.img using kvm
* Confirm it boots
* Confirm there is no boot speed regression
* Confirm that running `sudo apt-g
Verification of livecd-rootfs 2.664.2 in focal -proposed completed.
The following verification was completed.
* Perform livefs build with project ubuntu-base
* Boot *-disk-kvm.img using kvm
* Confirm it boots
* Confirm there is no boot speed regression
* Confirm that running `sudo apt-
CPC are seeing this issue in _all_ minimal cloud images testing with LXD
snap version 4.2 or greater. This blocks promotion of all minimal cloud
download images and blocks build and publication of both daily and
release cloud images.
--
You received this bug notification because you are a member
This does not appear to be docker specific but the chromium package has
moved to a snap package.
What is your host OS and kernel version?
Is the snapd service running in the container?
We have added the chromium package to this bug so they can investigate.
** Changed in: cloud-images
Sta
** Also affects: grub (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/1885571
Title:
Can't set boot kernel in GRUB on focal image
To manage notifi
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 succee
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
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.
https:
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 bug
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 Ubuntu.
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 Ubuntu.
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 ubuntu-phil
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 migra
** 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 c
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 propo
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] https://github.com/chrisglass/ubuntu-
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 ope
** 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 18
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
** 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 o
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.
https://bug
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.
https://bugs
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.
https://bugs
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.
https://bugs.launchpad.
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 Ub
Fix where GCE shutdown scripts are run during shutdown when using
Upstart
** Patch added: "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-orderin
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 gce-comp
** 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: "lp1667277-fix-shutdown-script-ordering
** 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:
+*
Updated patch using correct version number 20160930-0ubuntu3~14.04.1
** Patch added: "lp1667277-fix-shutdown-script-ordering-upstart.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1667277/+attachment/4825370/+files/lp1667277-fix-shutdown-script-ordering-upst
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 Ubuntu
.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 subscri
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 receive
** 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 image
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 added:
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
f
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: "daily-ubuntu-gcip-sru-1604-x
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: "daily-ubuntu-gcip-sru-1604-x
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
** 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
** 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"
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+att
Merge proposals created:
Master/Zesty:
https://code.launchpad.net/~philroche/ubuntu/+source/gce-compute-image-packages/+git/gce-compute-image-packages/+merge/320377
Yakkety:
https://code.launchpad.net/~philroche/ubuntu/+source/gce-compute-image-packages/+git/gce-compute-image-packages/+merge/3203
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"
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+attachme
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"
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+attach
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"
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+attac
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"
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+attach
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.
https://bugs.launchpad.net
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"
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packag
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"
https://bugs.launchpad.net/ubuntu/+source/gce-compute
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"
https://bugs.launchpad.net/ubuntu/+source/gce-compute-i
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"
https://bugs.launchpad.net/ubuntu/+source/gce-compute-i
** 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,
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
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 Ubun
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 Xe
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 it
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 t
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 c
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
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 ntp
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
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 memb
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
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 verif
1 - 100 of 197 matches
Mail list logo
