[Bug 1912248] Re: virtualenv on xenial: easy_install syntax error
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` * Enable proposed as per https://wiki.ubuntu.com/Testing/EnableProposed * Upgrade packages using `sudo apt install python3-virtualenv virtualenv python-virtualenv` * Confirm that any `pip` operations succeed * `virtualenv -p /usr/bin/python3 venv/py3-verification --verbose` * I also confirm here that the pip and setup tools were being pinned here > Installing setuptools < 51.3, pkg_resources, pip < 21, wheel... * `source ./venv/py3-verification/bin/activate` * `pip list` Tags added verification-done-xenial verification-done ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done 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/1912248 Title: virtualenv on xenial: easy_install syntax error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1912248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912248] Re: virtualenv on xenial: easy_install syntax error
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 bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1912248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928040] Re: GCE instances drop to a grub prompt when GRUB_DISTRIBUTOR=Debian is set
@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-done and verification-done-xenial ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done 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/1928040 Title: GCE instances drop to a grub prompt when GRUB_DISTRIBUTOR=Debian is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1928040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779961] [NEW] Bionic minimal image boot hang with linux-image-4.15.0-1012-kvm kernel
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 otherwise no changes over the prior image. Image (manifest and logs) exhibiting this behaviour @ https://private- fileshare.canonical.com/~philroche/bionic-minimal-20180703/ With server teams's help we have narrowed it down to "Synchronized to time server 91.189.91.157:123 (ntp.ubuntu.com)." taking over 4 minutes. On Kamal's instruction we also tried linux-kvm 4.15.0-1013.13 and bionic GA linux (4.15.0-24.26). Both of which also exhibit this regression. For reference: Kamal noted on IRC that the problem was possibly introduced in the GA kernel and is not specific to the kvm kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic -- 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: Bionic minimal image boot hang with linux-image-4.15.0-1012-kvm kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779961] Re: Boot delays with 4.15.0-24 based kernels in images
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 kernels in images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778777] Re: unminimize script is not restoring man-db
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-old-fashioned/ ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778777 Title: unminimize script is not restoring man-db To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1778777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778777] Re: unminimize script is not restoring man-db
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-old-fashioned/ ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done 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/1778777 Title: unminimize script is not restoring man-db To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1778777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795017] Re: linux-azure on cosmic minimal image boot speed
@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/~philroche/azure-cosmic-20181011/ ** Attachment added: "cosmic minimal image with linux-azure 4.18.0.1003.3 (from cosmic-proposed) boot log" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+attachment/5199957/+files/eeDaquoh3aiqu-vm-imagedebug-boot.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795017 Title: linux-azure on cosmic minimal image boot speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795017] Re: linux-azure on cosmic minimal image boot speed
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. One line of investigation is to check the package diff between the minimal image with initramfs-tools installed and the image without that installed. That diff is @ https://pastebin.canonical.com/p/7hJTSQHbyD/ Another possibility is to check the package diff between base and minimal. That diff is @ https://pastebin.canonical.com/p/B9m7GbsFhs/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795017 Title: linux-azure on cosmic minimal image boot speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795017] Re: linux-azure on cosmic minimal image boot speed
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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795017 Title: linux-azure on cosmic minimal image boot speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795017] Re: linux-azure on cosmic minimal image boot speed
** 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 a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795017 Title: linux-azure on cosmic minimal image boot speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795017] [NEW] linux-azure on cosmic minimal image boot speed
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 instance @ https://private-fileshare.canonical.com/~philroche/azure- cosmic-20180927/minimal/. You can see the same logs for the non minimal image @ https://private-fileshare.canonical.com/~philroche/azure- cosmic-20180927/base Most of the time seems to be spent in crng and "task swapper/0:1" (?) [5.774760] sd 3:0:0:0: [sdc] Attached SCSI disk [ 71.388989] random: crng init done [ 242.656057] INFO: task swapper/0:1 blocked for more than 120 seconds. [ 242.688434] Not tainted 4.15.0-1018-azure #18-Ubuntu Source: https://private-fileshare.canonical.com/~philroche/azure- cosmic-20180927/minimal/iengal3seeSee-vm-imagedebug-boot.log Please let me know if you need any more information or would like me to launch an instance for testing. I understand that minimal images are intended to boot without initramfs but I did install initramfs-tools in another test image which did result in much better boot times. See https://private-fileshare.canonical.com/~philroche/azure- cosmic-20180928/ for logs. Minimal image boot time 48.784s ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Attachment added: "cosmic minimal image with linux-azure boot log" https://bugs.launchpad.net/bugs/1795017/+attachment/5194121/+files/iengal3seeSee-vm-imagedebug-boot.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795017 Title: linux-azure on cosmic minimal image boot speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766287] Re: 18.04 minimal images on GCE intermittently fail to set up networking
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 ``` [Unit] After=systemd-udev-trigger.service [Service] ExecStartPre=/bin/udevadm settle ``` The goal of this workaround is to: 1) ensure that cloud-init-local.service runs after systemd-udev-trigger.service starts (this is what triggers udev coldplug events, like plugging in the nic) 2) Run udevadm settle before we start cloud-init local so that any nic processing is completed before cloud-init starts looking for a nic. Currently this is only required on minimal images but there is a chance it could occur in base images too should they boot quick enough. Minimal disco does not have snap preseeding as base images do and due to this running before cloud-init it makes it extremely unlikely to happen in base images. I understand that cloud-init might not be the place to fix the issue for all images but I'd like to re-open this bug to start that discussion. I have attached cloud-init logs, netplan yaml, image manifest and sosreports from an instance that failed to set up networking. ** Attachment added: "Disco GCE Minimal Failed Networking Setup Logs" https://bugs.launchpad.net/cloud-init/+bug/1766287/+attachment/5250709/+files/20190322-Disco-GCE-Minimal-Failed-Networking-Setup-Logs.tar.gz -- 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 intermittently fail to set up networking To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1766287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766287] Re: 18.04 minimal images on GCE intermittently fail to set up networking
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 intermittently fail to set up networking To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1766287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861704] [NEW] ubuntu-fan recommends netcat package in universe
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 universe) recommends ubuntu-fan (main) * ubuntu-fan (main) recommends netcat (universe) * netcat (universe) is a transitional package and depends on netcat-traditional (universe) Our concern is that this might be a packaging violation as ubuntu-fan is recommending a package not in main. > In addition, the packages in main > > must not require a package outside of main for compilation or execution > (thus, the package must > not declare a "Depends", "Recommends", or "Build-Depends" relationship on a > non-main package), Source: https://people.canonical.com/~cjwatson/ubuntu-policy/policy.html /ch-archive.html#s-main I will file a bug against netcat too to start a discussion on netcat being built from netcat-openbsd (main) instead of netcat-traditional (universe). Our feeling is that netcat is such a frequently depended on or recommended package that it being present in main would benefit Ubuntu. ** Affects: ubuntu-fan (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/1861704 Title: ubuntu-fan recommends netcat package in universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1861704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861704] Re: ubuntu-fan recommends netcat package in universe
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 recommends netcat package in universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1861704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581200] Re: Ubuntu cloud-init expects trailing dot on GCE metadata FQDN
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 hostname not
+ resolving.
+
+ * Backporting of this is necessary as instances with bind9 installed
+ can no longer take advantage of cloud-init
+
+ * The patch fixes this bug by updating the hostname used in the
+ metadata lookup to one that is included in /etc/hosts. As such it will
+ resolve, even if bind9 hasn't started yet.
+
+ [Test Case]
+
+ #launch an instance of ubuntu 14.04 on GCE
+ sudo apt-get update
+ sudo apt-get install -y bind9
+ #Add the Google DNS servers as global forwarders and configure bind9 for the
GCE environment
+ cat << EOF | sudo tee /etc/bind/named.conf.options
+ options {
+ directory "/var/cache/bind";
+
+ forwarders {
+ 169.254.169.254;
+ };
+
+ recursion yes;
+ dnssec-validation no;
+ dnssec-enable no;
+ auth-nxdomain no;
+ listen-on { 127.0.0.1; };
+ };
+ EOF
+ sudo service bind9 restart
+ #setup your instance to use bind9 instead of the Google server
+ echo "supersede domain-name-servers 127.0.0.1;" | sudo tee -a
/etc/dhcp/dhclient.conf
+ sudo dhclient -pf /run/dhclient.eth0.pid -x
+ sudo dhclient -1 -v -pf /run/dhclient.eth0.pid -lf
/var/lib/dhcp/dhclient.eth0.leases eth0
+ if grep -q "nameserver 127.0.0.1" "/etc/resolv.conf"; then echo "resolv.conf
has been updated"; fi
+ if host -t A metadata.google.internal | grep '169.254.169.254' > /dev/null;
then echo "host lookup succeeded as expected"; fi
+ sudo service bind9 stop
+ if host -t A metadata.google.internal | grep 'connection timed out' >
/dev/null; then echo "host lookup failed as expected"; fi
+
+ #Now reboot the instance
+ sudo reboot
+ #Once rebooted run the following
+ if grep -q "http://metadata.google.internal./computeMetadata/v1/ is not
resolvable" "/var/log/cloud-init.log"; then echo "cloud-init failed to lookup
metadata as expected"; else echo "cloud-init did _not_ fail to lookup metadata
as expected"; fi
+
+ A patched ubuntu14.04 has been built. To test the patch run the above but
after reboot run
+ #launch a patched instance
+ gcloud compute instances create ubuntu1404-patched-cloudinit --image
daily-ubuntu-proche-cloudinit-1404-trusty-v20160627 --image-project
ubuntu-os-cloud-devel
+
+ #on a patched instance run the following after reboot
+ if grep -q "http://metadata.google.internal/computeMetadata/v1/ is not
resolvable" "/var/log/cloud-init.log"; then echo "cloud-init failed to retrieve
metadata"; else echo "cloud-init did successfully retrieve metadata as
expected"; fi
+
+ [Regression Potential]
+
+ * GCE are questing this change.
+ * The reported issue only affects GCE users and only a small set of those
users will be using a local DNS server.
+ * The change is a single character change and has been tested and as such
has limited regression potential.
+
+
+ [Original Bug Report]
+
cloud-init hostname breaks because /etc/hosts does not have the trailing
dot on metadata FQDN.
Background:
On Ubuntu, cloud-init sets the hostname using our metadata service. To do
this, it hits "metadata.google.internal." (note trailing dot) via HTTP.
We have entries in /etc/hosts for the metadata service to ensure that we
can access it at boot time (if DNS is not yet up) as we have other init
scripts which block bootup when metadata cannot be reached. However,
these /etc/hosts entries only have "metadata.google.internal" (no
trailing dot) entries.
When a customer runs their own bind9 daemon, it starts *after* cloud-
init, meaning that cloud-init must use /etc/hosts to find the metadata
service. When it cannot, it incorrectly sets the hostname to
"$hostname.localdomain" instead of just $hostname.
Proposed fix:
Update:
http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/sources/DataSourceGCE.py
Line 28 should read:
'metadata_url': 'http://metadata.google.internal/computeMetadata/v1/'
** Patch added: "lp-1581200-gce-metadatafqdn.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1581200/+attachment/4692729/+files/lp-1581200-gce-metadatafqdn.debdiff
--
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1581200/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581200] Re: Ubuntu cloud-init expects trailing dot on GCE metadata FQDN
** 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1581200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581044] Re: Images ship with modified conffiles
** 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 about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1581044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766287] Re: 18.04 minimal images on GCE intermittently fail to set up networking
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.net/bugs/1766287 Title: 18.04 minimal images on GCE intermittently fail to set up networking To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1766287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759519] Re: [SRU] Ensure "minimal" images have "minimal" in their /etc/cloud/build.info
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759519 Title: [SRU] Ensure "minimal" images have "minimal" in their /etc/cloud/build.info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1759519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840135] Re: Request for new Eoan build of python-simplestreams
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/ubuntu/+source/simplestreams/+bug/1840135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840135] [NEW] Request for new Eoan build of python-simplestreams
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 already used to. ** Affects: simplestreams (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/1840135 Title: Request for new Eoan build of python-simplestreams To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1840135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912248] Re: virtualenv on xenial: easy_install syntax error
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... Collecting setuptools Using cached https://files.pythonhosted.org/packages/b2/81/509db0082c0d2ca2af307c6652ea422865de1f83c14b1e1f3549e415cfac/setuptools-51.3.3-py3-none-any.whl Collecting pkg_resources Collecting pip Using cached https://files.pythonhosted.org/packages/54/eb/4a3642e971f404d69d4f6fa3885559d67562801b99d7592487f1ecc4e017/pip-20.3.3-py2.py3-none-any.whl Collecting wheel Using cached https://files.pythonhosted.org/packages/65/63/39d04c74222770ed1589c0eaba06c05891801219272420b40311cd60c880/wheel-0.36.2-py2.py3-none-any.whl Installing collected packages: setuptools, pkg-resources, pip, wheel Successfully installed pip-20.3.3 pkg-resources-0.0.0 setuptools-51.3.3 wheel-0.36.2 ...snip... ``` But 51.3.0 dropped support for python 3.5 which is what ships with Xenial. The fix would be to pin setuptools to `<51.3.0`. ** Bug watch added: github.com/pypa/setuptools/issues #2541 https://github.com/pypa/setuptools/issues/2541 -- 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 bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1912248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912248] Re: virtualenv on xenial: easy_install syntax error
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 'setuptools; python_version >= "3.6"' 'setuptools<51.3.0; python_version < "3.6" and python_version >= "3.0"'` > Ignoring setuptools: markers 'python_version >= "3.6"' don't match your > environment > Ignoring setuptools: markers 'python_version < "3.0"' don't match your > environment > Collecting setuptools<51.3.0 > Using cached setuptools-50.3.2-py3-none-any.whl (785 kB) > Installing collected packages: setuptools > Successfully installed setuptools-50.3.2 or by adding the following to your requirements.txt ``` setuptools; python_version >= "3.6" setuptools<51.3.0; python_version < "3.6" and python_version >= "3.0" ``` This results in `python3 -m pip list`: > pip20.3.3 > setuptools 50.3.2 > wheel 0.36.2 -- 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 bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1912248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912248] Re: virtualenv on xenial: easy_install syntax error
@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 python_version >= "3.0"' pip wheel && python3 -m pip list ``` Which uses the bundled pip, wheel and setuptools initially but then upgrades pip, wheel and setuptools using environment markers to ensure the supported version is installed. I do question the EOL argument. Xenial 16.04 is nearly at the end of standard support yes, but there will be many users continuing to use Xenial 16.04 with ESM for another five years. -- 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 bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1912248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] [NEW] SRU: Revert of initramfs package removal in KVM image
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 boots * Confirm there is no boot speed regression [Regression Potential] * Boot speed regression * Unable to boot KVM image [Other Info] * Original bug filed against cloud-images @ https://bugs.launchpad.net/cloud-images/+bug/1875400 * MP already merged in to ubuntu/master @ https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd-rootfs/+merge/384105 * livecd-rootfs version 2.667 in groovy was uploaded with this patch and was verified ** Affects: livecd-rootfs (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/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] Re: SRU: Revert of initramfs package removal in KVM image
** 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 results in many packages + [1] being marked for auto-removal. These packages are still required in + the image and should not be marked for auto-removal. + + The removal of initramfs-tools and busybox-initramfs was to avoid the + generation of initramfs in images that should boot initramfsless. + + This requirement is obsolete now because the initramfsless boot handling + is now handled via setting GRUB_FORCE_PARTUUID in /etc/default/grub.d/40-force-partuuid.cfg. [Impact] - * We don't want any packages marked for auto-removal on a published kvm - cloud image. + * No packages marked for auto-removal. This is a requirement for all + public cloud images. [Test Case] - * Perform livefs build with project ubuntu-base - * Boot *-disk-kvm.img using kvm -* Confirm it boots -* Confirm there is no boot speed regression + * 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-get autoremove` results in no packages being removed +* Verify that `GRUB_FORCE_PARTUUID` is set in /etc/default/grub.d/40-force-partuuid.cfg. [Regression Potential] - * Boot speed regression - * Unable to boot KVM image + * Boot speed regression + * Unable to boot KVM image [Other Info] - * Original bug filed against cloud-images @ https://bugs.launchpad.net/cloud-images/+bug/1875400 - * MP already merged in to ubuntu/master @ https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd-rootfs/+merge/384105 - * livecd-rootfs version 2.667 in groovy was uploaded with this patch and was verified + * Original bug filed against cloud-images @ https://bugs.launchpad.net/cloud-images/+bug/1875400 + * MP already merged in to ubuntu/master @ https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd-rootfs/+merge/384105 + * livecd-rootfs version 2.667 in groovy was uploaded with this patch and was verified + + + [1] apport apport-symptoms at bc bcache-tools bolt btrfs-progs byobu cryptsetup cryptsetup-bin cryptsetup-run dmeventd ethtool finalrd + fonts-ubuntu-console fwupd fwupd-signed git git-man htop initramfs-tools-bin klibc-utils kpartx landscape-common libaio1 libarchive13 + libcurl3-gnutls libdevmapper-event1.02.1 liberror-perl libevent-2.1-7 libfl2 libfwupd2 libfwupdplugin1 libgcab-1.0-0 libgpgme11 + libgudev-1.0-0 libgusb2 libisns0 libjson-glib-1.0-0 libjson-glib-1.0-common libklibc liblvm2cmd2.03 libmspack0 libreadline5 + libsgutils2-2 libsmbios-c2 libtss2-esys0 liburcu6 libutempter0 libxmlb1 libxmlsec1 libxmlsec1-openssl libxslt1.1 lvm2 lxd-agent-loader + lz4 mdadm open-iscsi open-vm-tools patch pollinate python3-apport python3-automat python3-click python3-colorama python3-constantly + python3-debconf python3-debian python3-hamcrest python3-hyperlink python3-incremental python3-newt python3-problem-report python3-pyasn1 + python3-pyasn1-modules python3-service-identity python3-systemd python3-twisted python3-twisted-bin python3-zope.interface run-one + screen sg3-utils sosreport thin-provisioning-tools tmux tpm-udev update-notifier-common xfsprogs zerofree -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] Re: SRU: Revert of initramfs package removal in KVM image
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] Re: SRU: Revert of initramfs package removal in KVM image
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] Re: SRU: Revert of initramfs package removal in KVM image
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-rootfs/+bug/1880170/+attachment/5375696/+files/lp-1880170-kvm-revert-of-initramfs-package-removal-focal-rev2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] Re: SRU: Revert of initramfs package removal in KVM image
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-rootfs/+bug/1880170/+attachment/5375697/+files/lp-1880170-kvm-revert-of-initramfs-package-removal-eoan-rev2.debdiff ** Patch removed: "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 ** Patch removed: "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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] Re: SRU: Revert of initramfs package removal in KVM image
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-get autoremove` results in no packages being removed * Verify that `GRUB_FORCE_PARTUUID` is set in /etc/default/grub.d/40-force-partuuid.cfg. See test images @ https://people.canonical.com/~philroche/lp-1880170-Revert-of-initramfs-package-removal-in-KVM-image/eoan/ ** Tags removed: verification-needed verification-needed-eoan verification-needed-focal ** Tags added: verification-done verification-done-eoan verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880170] Re: SRU: Revert of initramfs package removal in KVM image
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-get autoremove` results in no packages being removed * Verify that `GRUB_FORCE_PARTUUID` is set in /etc/default/grub.d/40-force-partuuid.cfg. See test images @ https://people.canonical.com/~philroche/lp-1880170-Revert-of-initramfs-package-removal-in-KVM-image/focal/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880170 Title: SRU: Revert of initramfs package removal in KVM image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882955] Re: LXD 4.2 broken on linux-kvm due to missing VLAN filtering
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882955 Title: LXD 4.2 broken on linux-kvm due to missing VLAN filtering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1882955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869963] Re: Unable to install chromium-browser 20.04
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 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/1869963 Title: Unable to install chromium-browser 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1869963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885571] Re: Can't set boot kernel in GRUB on focal image
** 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 notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1885571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773334] [NEW] Ubuntu 18.04 mounted network shares not appearing under devices in file manager
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 succeed and are accessible at their mount points. In 16.04 and 17.10 these mounts appeared under Devices (Screenshot of mounted network shares on Ubuntu Mate 17.10 attached) I am using the following code to mount NFS shares `sudo mount.nfs 192.168.2.123:/mnt/freenas-data1/photobackup /media/philroche/photobackup` and for SMB shares `sudo mount.cifs //192.168.2.123/photobackup /media/philroche/photobackup` Is this a bug/regression, or perhaps it is an intentional change? I did ask this on IRC in #ubuntu and askubuntu.com but no reply. Expected behaviour: I expected the mounted network shares to appear under Devices in File manager Actual behaviour: Mounting network shares does succeed as expected but does not appear under Devices in File manager as it did in previous releases. Requested details: Description:Ubuntu 18.04 LTS Release:18.04 udisks2: Installed: 2.7.6-3 Candidate: 2.7.6-3 Version table: *** 2.7.6-3 500 500 http://ie.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshots of hoe mounted network shares appears pre 18.04" https://bugs.launchpad.net/bugs/1773334/+attachment/5144162/+files/Ubuntu17.10MountedNetworkShares.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773334 Title: Ubuntu 18.04 mounted network shares not appearing under devices in file manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1773334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773334] Re: Ubuntu 18.04 mounted network shares not appearing under devices in file manager
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773334 Title: Ubuntu 18.04 mounted network shares not appearing under devices in file manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1773334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773334] Re: Ubuntu 18.04 mounted network shares not appearing under devices in file manager
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://bugs.launchpad.net/bugs/1773334 Title: Ubuntu 18.04 mounted network shares not appearing under devices in file manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1773334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770650] Re: Update google compute-image-packages to 20180510
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770650 Title: Update google compute-image-packages to 20180510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1770650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770650] Re: Update google compute-image-packages to 20180510
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. https://bugs.launchpad.net/bugs/1770650 Title: Update google compute-image-packages to 20180510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1770650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770650] Re: Update google compute-image-packages to 20180510
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. https://bugs.launchpad.net/bugs/1770650 Title: Update google compute-image-packages to 20180510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1770650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770650] Re: Update google compute-image-packages to 20180510
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 All have passed automated and manual tests. Build of Trusty image with gce-compute-image-packages 20180510+dfsg1 is 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/1770650 Title: Update google compute-image-packages to 20180510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1770650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770650] Re: Update google compute-image-packages to 20180510
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 migration to -updates pocket of the archive. -- 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 compute-image-packages to 20180510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1770650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770650] Re: Update google compute-image-packages to 20180510
** 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 compute-image-packages to 20180510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1770650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770650] Re: Update google compute-image-packages to 20180510
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 proposed version of gce-compute-image-packages: * daily-ubuntu-gceip-verify-1404-trusty-v20180530a in project ubuntu-os-cloud-devel * daily-ubuntu-testing-1604-xenial-v20180529 in project ubuntu-phil * daily-ubuntu-testing-1710-artful-v20180529 in project ubuntu-phil * daily-ubuntu-testing-1804-bionic-v20180525 in project ubuntu-phil @GCE-team, please can you verify these images before we proceed with migration to -updates pocket of the archive. ** Changed in: gce-compute-image-packages (Ubuntu) Assignee: Balint Reczey (rbalint) => The Cpc-gce team (cpc-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/1770650 Title: Update google compute-image-packages to 20180510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1770650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779406] Re: Pollinate missing from xenial minimal images
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-old-fashioned/ ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done 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/1779406 Title: Pollinate missing from xenial minimal images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1779406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1753945] [NEW] Failure to build 18.04 minimal images due to missing gpg packages
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 operation See attached snippet from build log from build for more context. I understand that there has been recent changes to which gpg packages are installed in 18.04. Is this a bug or should we be explicitly installing gpg packages now? We started seeing these build failures on 03-Mar-2018. This is blocking build of all 18.04 minimal images. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Attachment added: "/buildlog_ubuntu_bionic_amd64_cpc_BUILDING.txt" https://bugs.launchpad.net/bugs/1753945/+attachment/5071406/+files/buildlog_ubuntu_bionic_amd64_cpc_BUILDING_failure.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753945 Title: Failure to build 18.04 minimal images due to missing gpg packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1753945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1753945] Re: Failure to build 18.04 minimal images due to missing gpg packages
** 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.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 operation - - - See attached snippet from build log from build for more context. + E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them + is required for this operation I understand that there has been recent changes to which gpg packages are installed in 18.04. Is this a bug or should we be explicitly installing gpg packages now? We started seeing these build failures on 03-Mar-2018. This is blocking build of all 18.04 minimal images. ** Description changed: We (CPC) are seeing failures when building 18.04 minimal images with the - following errors. + following errors when adding a PPA. E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation I understand that there has been recent changes to which gpg packages are installed in 18.04. Is this a bug or should we be explicitly installing gpg packages now? We started seeing these build failures on 03-Mar-2018. This is blocking build of all 18.04 minimal images. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753945 Title: Failure to build 18.04 minimal images due to missing gpg packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1753945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643585] [NEW] Backporting gce-compute-image-packages
Public bug reported: [Impact] * 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- image-packages installed to avail of any new features on GCE [Test Case] * There are no bugs to reproduce as this is a new package. * There are numerous tests run as part of Ubuntu cloud image for GCE creation. These tests have been updated to test any changes introduced by gce-compute-image-packages. All of these tests pass. * The simplest way to test this package is to launch a GCE instance with this package installed [2] and test that it is reachable via SSH using the keys specified when launching. Also check that any startup scripts specified are run and that NTP has set the time correctly. [Regression Potential] * Most harmful regression potential is GCE instance becoming unreachable. This was the case with gce-utils too though. [Other Info] * This change has been requested by GCE and is a requirement for any future Ubuntu cloud images for GCE. They are very eager to get this backported. [1] https://launchpad.net/ubuntu/+source/gce-utils [2] "/ubuntu-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 Progress ** Changed in: gce-compute-image-packages (Ubuntu) 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/1643585 Title: Backporting gce-compute-image-packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1643585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643585] Re: Backporting gce-compute-image-packages
** 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- + * All supported versions of Ubuntu on GCE should have gce-compute- image-packages installed to avail of any new features on GCE [Test Case] - * There are no bugs to reproduce as this is a new package. + * There are no bugs to reproduce as this is a new package. - * There are numerous tests run as part of Ubuntu cloud image for GCE - creation. These tests have been updated to test any changes introduced - by gce-compute-image-packages. All of these tests pass. + * There are numerous tests: +* ntp conf +* expected packages are installed +* expected services are running +* SSH access +* Kernel Config +* Hosts file is as expected - * The simplest way to test this package is to launch a GCE instance + These run as part of Ubuntu cloud image for GCE creation. These tests + have been updated to test any changes introduced by gce-compute-image- + packages. All of these tests pass. + + * The simplest way to test this package is to launch a GCE instance with this package installed [2] and test that it is reachable via SSH using the keys specified when launching. Also check that any startup scripts specified are run and that NTP has set the time correctly. [Regression Potential] - * Most harmful regression potential is GCE instance becoming + * Most harmful regression potential is GCE instance becoming unreachable. This was the case with gce-utils too though. [Other Info] - - * This change has been requested by GCE and is a requirement for any future Ubuntu cloud images for GCE. They are very eager to get this backported. + * This change has been requested by GCE and is a requirement for any + future Ubuntu cloud images for GCE. They are very eager to get this + backported. [1] https://launchpad.net/ubuntu/+source/gce-utils [2] "/ubuntu-os-cloud-devel/daily-ubuntu-testing-1610-yakkety-v20161110" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643585 Title: Backporting gce-compute-image-packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1643585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643585] Re: Backporting gce-compute-image-packages
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643585 Title: Backporting gce-compute-image-packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1643585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643585] Re: Backporting gce-compute-image-packages
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://bugs.launchpad.net/bugs/1643585 Title: Backporting gce-compute-image-packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1643585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643585] Re: Backporting gce-compute-image-packages
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.launchpad.net/bugs/1643585 Title: Backporting gce-compute-image-packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1643585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643585] Re: Backporting gce-compute-image-packages
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.launchpad.net/bugs/1643585 Title: Backporting gce-compute-image-packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1643585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645276] Re: google-startup-scripts runs before cloud-init has completed
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.net/bugs/1645276 Title: google-startup-scripts runs before cloud-init has completed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1645276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1648380] Re: cloud-init fails to find CloudSigma datasource with cloud-init 0.7.8-1-g3705bb5-0ubuntu1
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1648380 Title: cloud-init fails to find CloudSigma datasource with cloud-init 0.7.8-1-g3705bb5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1648380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667277] Re: Shutdown scripts do not run on 1404 images with gce-compute-image-packages installed
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-ordering-upstart.debdiff -- 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-compute-image- packages installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1667277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667277] [NEW] Shutdown scripts do not run on 1404 images with gce-compute-image-packages installed
Public bug reported: Trusty images with gce-compute-image-packages package installed so not run shutdown scripts. Image daily-ubuntu-philroche-1404-trusty-v20170216 in ubuntu-os-cloud- devel is one such image. ** Affects: gce-compute-image-packages (Ubuntu) Importance: Undecided 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 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-compute-image- packages installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1667277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667277] Re: Shutdown scripts do not run on 1404 images with gce-compute-image-packages installed
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-compute-image- packages installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1667277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667277] Re: Shutdown scripts do not run on 1404 images with gce-compute-image-packages installed
** 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-upstart.debdiff" https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1667277/+attachment/4825160/+files/lp1667277-fix-shutdown-script-ordering-upstart.debdiff -- 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-compute-image- packages installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1667277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667277] Re: Shutdown scripts do not run on 1404 images with gce-compute-image-packages installed
** 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: +* ntp conf +* expected packages are installed +* expected services are running +* SSH access +* Kernel Config +* Hosts file is as expected + + These run as part of Ubuntu cloud image for GCE creation. + + All of these tests pass. + + * The simplest way to test this patch manually is to launch a GCE + instance with this package installed specifying a shutdown script + + `gcloud compute instances create daily-ubuntu-shutdown2-1404-trusty-v20170222-2--image-project ubuntu-os-cloud-devel --image "daily-ubuntu-shutdown2-1404-trusty-v20170222" --metadata shutdown-script="#! /bin/bash + touch /home/ubuntu/shutdowntrusty.txt"` + + reboot or shutdown this instance. Upon restarting the instance you will + notice that /home/ubuntu/shutdowntrusty.txt has been created. + + [Regression Potential] + + * Most harmful regression potential is GCE instance not shutting down. + This has been tested and is not the case. + + [Other Info] + + * This change has been requested by GCE and is a requirement for any + future Ubuntu cloud images for GCE. They are very eager to get this + fixed. + + * Should you wish to test/observe previous behaviour, image daily- + ubuntu-philroche-1404-trusty-v20170216 in ubuntu-os-cloud-devel has the + previous version of the package installed and does not run the shutdown + scripts. + + + _Original Description_ + Trusty images with gce-compute-image-packages package installed so not run shutdown scripts. Image daily-ubuntu-philroche-1404-trusty-v20170216 in ubuntu-os-cloud- devel is one such image. -- 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-compute-image- packages installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1667277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667277] Re: Shutdown scripts do not run on 1404 images with gce-compute-image-packages installed
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-upstart.debdiff ** Changed in: gce-compute-image-packages (Ubuntu) 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/1667277 Title: Shutdown scripts do not run on 1404 images with gce-compute-image- packages installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1667277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667277] Re: Shutdown scripts do not run on 1404 images with gce-compute-image-packages installed
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. https://bugs.launchpad.net/bugs/1667277 Title: Shutdown scripts do not run on 1404 images with gce-compute-image- packages installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1667277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668327] Re: Startup scripts get run when guest packages are updated
The postinst file used in the ubuntu package was auto-generated by debhelper command sequencer [1]. I will start the process of including your postinst and prerm scripts instead of relying on debhelper command sequencer auto generated ones. [1] http://manpages.ubuntu.com/manpages/zesty/man1/dh.1.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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668327 Title: Startup scripts get run when guest packages are updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668327] [NEW] Startup scripts get run when guest packages are updated
Public bug reported: A user reported (https://github.com/GoogleCloudPlatform/compute-image- packages/issues/376) that startup scripts are running when the guest packages get updated on Ubuntu. This can of course have very unexpected consequences. I did some digging and found that the postinst you are using is not the same as ours and appears to start all the systemd services including startup and shutdown scripts when it runs. if [ -d /run/systemd/system ]; then systemctl --system daemon-reload >/dev/null || true deb-systemd-invoke start google-accounts-daemon.service google-clock-skew-daemon.service google-instance-setup.service google-ip-forwarding-daemon.service google-network-setup.service google-shutdown-scripts.service google-startup-scripts.service >/dev/null || true We have a postinst that works on other systemd platforms which you are welcome 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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668327 Title: Startup scripts get run when guest packages are updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667277] Re: Shutdown scripts do not run on 1404 images with gce-compute-image-packages installed
** 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 images with gce-compute-image- packages installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1667277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1696191] Re: [SRU] Update google compute-image-packages to 20170523
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696191 Title: [SRU] Update google compute-image-packages to 20170523 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1696191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690147] Re: Missing versioned dependency against python3-google-compute-engine
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: verification-done-trusty verification-done-xenial verification-done-yakkety 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/1690147 Title: Missing versioned dependency against python3-google-compute-engine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1690147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703647] Re: google-compute-engine-oslogin 20170622-0ubuntu1~14.04.0 installation fails on Trusty
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 fails on Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1703647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746588] Re: Update google compute-image-packages to 20180129
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-xenial-v20180205" in project "ubuntu-os-cloud-devel" * Artful: "daily-ubuntu-gcip-sru-1710-artful-v20180126" in project "ubuntu-os-cloud-devel" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746588 Title: Update google compute-image-packages to 20180129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1746588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741989] Re: Drop libpam-cracklib from gce-compute-image-packages Recommends
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-xenial-v20180205" in project "ubuntu-os-cloud-devel" * Artful: "daily-ubuntu-gcip-sru-1710-artful-v20180126" in project "ubuntu-os-cloud-devel" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741989 Title: Drop libpam-cracklib from gce-compute-image-packages Recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1741989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728383] Re: Unable to create a DBus proxy for GnomeScreensaver
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728383 Title: Unable to create a DBus proxy for GnomeScreensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1728383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581200] Re: Ubuntu cloud-init expects trailing dot on GCE metadata FQDN
** 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 dot on GCE metadata FQDN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1581200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668327] Re: Startup scripts get run when guest packages are updated
** 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. + + * Running these scripts more than once on a running instance is not exptected +behaviour and depending on the contents of the user's scripts could have +disastrous consequences. + + * The fix tis to use override_dh_systemd_start in the debian/rules to alter the +generated postinst, prerm and postrm files to not restart the startup or +shutdown scripts on upgrade or install. + + [Test Case] + + * Start instance with shutdown script and startup script + + gcloud compute instances create ubuntu-1604-xenial-v20170224 --image-project ubuntu-os-cloud + --image "ubuntu-1604-xenial-v20170224" --metadata shutdown-script="#! /bin/bash + touch /home/ubuntu/shutdown.txt",startup-script="#! /bin/bash + touch /home/ubuntu/startup.txt" + + # Run the following on the running instance + # clean up instance ready for testing + + rm -f ~/startup.txt + + # Add new PPA with fixed package + + sudo add-apt-repository -y ppa:philroche/gce-compute-image-packages + sudo apt-get update + sudo apt-get install --only-upgrade gce-compute-image-packages + + # Note that the first upgrade will always result in shutdown + # scripts being run as the initial gce-compute-image-packages postrm script are still in use. + # verify that the bug still exists + + if [ -f ~/shutdown.txt ]; then + echo "Shutdown File found! Bug still present" + rm -f ~/shutdown.txt + fi + + [Regression Potential] + + * Possible regressions are that the startup and shutdown script services never start and user's scripts to not get + executed. This has been tested and is not the case. + + [Original bug description] + + A user reported (https://github.com/GoogleCloudPlatform/compute-image- packages/issues/376) that startup scripts are running when the guest packages get updated on Ubuntu. This can of course have very unexpected consequences. I did some digging and found that the postinst you are using is not the same as ours and appears to start all the systemd services including startup and shutdown scripts when it runs. if [ -d /run/systemd/system ]; then - systemctl --system daemon-reload >/dev/null || true - deb-systemd-invoke start google-accounts-daemon.service google-clock-skew-daemon.service google-instance-setup.service google-ip-forwarding-daemon.service google-network-setup.service google-shutdown-scripts.service google-startup-scripts.service >/dev/null || true + systemctl --system daemon-reload >/dev/null || true + deb-systemd-invoke start google-accounts-daemon.service google-clock-skew-daemon.service google-instance-setup.service google-ip-forwarding-daemon.service google-network-setup.service google-shutdown-scripts.service google-startup-scripts.service >/dev/null || true We have a postinst that works on other systemd platforms which you are welcome to use or mimic here: https://github.com/GoogleCloudPlatform /compute-image- packages/blob/master/google_compute_engine_init/systemd/postinst.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668327 Title: Startup scripts get run when guest packages are updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668327] Re: Startup scripts get run when guest packages are updated
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/+attachment/4841035/+files/lp1668327-no-restart-of-startup-shutdown-scripts-on-upgrade-yakkety.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668327 Title: Startup scripts get run when guest packages are updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668327] Re: Startup scripts get run when guest packages are updated
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/320385 Xenial: https://code.launchpad.net/~philroche/ubuntu/+source/gce-compute-image-packages/+git/gce-compute-image-packages/+merge/320386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668327 Title: Startup scripts get run when guest packages are updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668327] Re: Startup scripts get run when guest packages are updated
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/+attachment/4841033/+files/lp1668327-no-restart-of-startup-shutdown-scripts-on-upgrade-zesty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668327 Title: Startup scripts get run when guest packages are updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668327] Re: Startup scripts get run when guest packages are updated
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/+attachment/4841037/+files/lp1668327-no-restart-of-startup-shutdown-scripts-on-upgrade-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668327 Title: Startup scripts get run when guest packages are updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668327] Re: Startup scripts get run when guest packages are updated
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/+attachment/4841148/+files/lp1668327-no-restart-of-startup-shutdown-scripts-on-upgrade-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668327 Title: Startup scripts get run when guest packages are updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668327] Re: Startup scripts get run when guest packages are updated
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/+attachment/4842264/+files/lp1668327-no-restart-of-startup-shutdown-scripts-on-upgrade-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668327 Title: Startup scripts get run when guest packages are updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668327] Re: Startup scripts get run when guest packages are updated
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/bugs/1668327 Title: Startup scripts get run when guest packages are updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668327] Re: Startup scripts get run when guest packages are updated
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-packages/+bug/1668327/+attachment/4842491/+files/gce-compute-image-packages-zesty-testplan-proposed.txt ** Tags added: verification-done ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668327 Title: Startup scripts get run when guest packages are updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668327] Re: Startup scripts get run when guest packages are updated
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-image-packages/+bug/1668327/+attachment/4843450/+files/gce-compute-image-packages-yakkety-testplan-proposed.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668327 Title: Startup scripts get run when guest packages are updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668327] Re: Startup scripts get run when guest packages are updated
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-image-packages/+bug/1668327/+attachment/4843449/+files/gce-compute-image-packages-xenial-testplan-proposed.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668327 Title: Startup scripts get run when guest packages are updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668327] Re: Startup scripts get run when guest packages are updated
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-image-packages/+bug/1668327/+attachment/4843451/+files/gce-compute-image-packages-trusty-testplan-proposed.txt ** 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.net/bugs/1668327 Title: Startup scripts get run when guest packages are updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643585] Re: Backporting gce-compute-image-packages
** 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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643585 Title: Backporting gce-compute-image-packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1643585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643585] Re: Backporting gce-compute-image-packages
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643585 Title: Backporting gce-compute-image-packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1643585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643585] Re: Backporting gce-compute-image-packages
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 Ubuntu. https://bugs.launchpad.net/bugs/1643585 Title: Backporting gce-compute-image-packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1643585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656801] [NEW] ntp: changing the default config from server to pool broke the dhcp hook
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 Xenial only as the Yakkety build includes the upstream fix (1:4.2.8p7+dfsg-1). Original Debian busg https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809344 & https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806676 ** Affects: ntp (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/1656801 Title: ntp: changing the default config from server to pool broke the dhcp hook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1656801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656801] Re: ntp: changing the default config from server to pool broke the dhcp hook
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 itself is a regression from functionality prior to 1:4.2.8p3+dfsg-1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656801 Title: ntp: changing the default config from server to pool broke the dhcp hook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1656801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656899] [NEW] ntp: changing the default config from server to pool broke default ntp configuration
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 they are now configured using "pool". This affects Xenial only. ** Affects: gce-utils (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Patch to fix Xenial ntp.conf" https://bugs.launchpad.net/bugs/1656899/+attachment/4805060/+files/lp-1639089-gce-ntp-servers.debdiff -- 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 config from server to pool broke default ntp configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-utils/+bug/1656899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656899] Re: ntp: changing the default config from server to pool broke default ntp configuration
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 config from server to pool broke default ntp configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-utils/+bug/1656899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643585] Re: Backporting gce-compute-image-packages
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643585 Title: Backporting gce-compute-image-packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1643585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656801] Re: ntp: changing the default config from server to pool broke the dhcp hook
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.conf better. ** Bug watch added: Debian Bug tracker #806676 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806676 ** Bug watch added: Debian Bug tracker #809344 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809344 ** Patch added: "lp-1656801-fix-dhcp-hook.debdiff" https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1656801/+attachment/4806257/+files/lp-1656801-fix-dhcp-hook.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656801 Title: ntp: changing the default config from server to pool broke the dhcp hook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1656801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652695] Re: GCE default NTP configuration uses both leap-smeared and true UTC sources
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 be fixing lp:1639089 in the GCE Xenial image build process initially followed by a fix for gce-cloud-config. Note that gce-cloud-config is being deprecated in favour of gce-compute- image-packages which does not have this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652695 Title: GCE default NTP configuration uses both leap-smeared and true UTC sources To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1652695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705448] Re: Update google compute-image-packages to 20170718
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705448 Title: Update google compute-image-packages to 20170718 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1705448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705448] Re: Update google compute-image-packages to 20170718
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705448 Title: Update google compute-image-packages to 20170718 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1705448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714299] Re: walinuxagent update 2.2.16
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 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/1714299 Title: walinuxagent update 2.2.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1714299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
