[Group.of.nepali.translators] [Bug 1891608] Re: openvswitch-switch isn't installed if netplan schema defines an ovs bridge
This bug was fixed in the package curtin - 20.1-20-g1304d3ea-0ubuntu1
---
curtin (20.1-20-g1304d3ea-0ubuntu1) groovy; urgency=medium
* New upstream snapshot.
- curthooks: uefi_find_grub_device_ids handle type:mount without path
(LP: #1892242)
- netplan openvswitch yaml changed (LP: #1891608)
- tools/curtainer: do not wait for snapd.seeded.service
- tools/curtainer: enable using ubuntu-minimal images
- vmtests: add Groovy [Paride Legovini]
- Drop the Eoan vmtests (EOL) [Paride Legovini]
- tools: rename remove-vmtest-release to vmtest-remove-release
- Snooze the tests failing because of LP: #1861941 for two more months
[Paride Legovini]
- LP: #1671951 is Fix Released => Drop the PPA [Paride Legovini]
- swaps: handle swapfiles on btrfs (LP: #1884161)
- curtainer: fail is masking of zfs-mount or zfs-share fails
[Paride Legovini]
- multipath: handle multipath nvme name fields correctly (LP: #1878041)
- curtainer: mask the zfs-mount and zfs-share services [Paride Legovini]
- tools/jenkins-runner: shuffle test-cases to randomize load
[Paride Legovini]
- Add Trusty/UEFI/HWE-X vmtest, drop realpath add, drop shell code
- LP: #1881977 - Install realpath on Trusty UEFI. [Lee Trager]
- vmtests: fix PreservePartitionWipeVg storage config
- Fix mdraid name creates broken configuration
[James Falcon] (LP: #1803933)
- vmtests: update skiptests
- vmtest: allow installed centos images to reboot (LP: #1881011)
-- Ryan Harper Thu, 20 Aug 2020 09:10:33 -0500
** Changed in: curtin (Ubuntu Groovy)
Status: New => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1891608
Title:
openvswitch-switch isn't installed if netplan schema defines an ovs
bridge
Status in curtin:
Fix Committed
Status in curtin package in Ubuntu:
Fix Released
Status in curtin source package in Xenial:
New
Status in curtin source package in Bionic:
New
Status in curtin source package in Focal:
New
Status in curtin source package in Groovy:
Fix Released
Bug description:
If the network config defines an openvswitch bridge, curtin doesn't
install the openvswitch-switch package, which is needed. For examle, a
schema like this:
network:
version: 2
bridges:
br-empty:
openvswitch: {}
Looking at the current code in curtin, it only handles the case
where's there's a top-level 'openvswitch' section, or the renderer is
'openvswitch' (which was the previous proposal for openvswitch support
in netplan)
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1891608/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1891608] Re: openvswitch-switch isn't installed if netplan schema defines an ovs bridge
** Also affects: curtin (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1891608
Title:
openvswitch-switch isn't installed if netplan schema defines an ovs
bridge
Status in curtin:
Fix Committed
Status in curtin package in Ubuntu:
New
Status in curtin source package in Xenial:
New
Status in curtin source package in Bionic:
New
Status in curtin source package in Focal:
New
Status in curtin source package in Groovy:
New
Bug description:
If the network config defines an openvswitch bridge, curtin doesn't
install the openvswitch-switch package, which is needed. For examle, a
schema like this:
network:
version: 2
bridges:
br-empty:
openvswitch: {}
Looking at the current code in curtin, it only handles the case
where's there's a top-level 'openvswitch' section, or the renderer is
'openvswitch' (which was the previous proposal for openvswitch support
in netplan)
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1891608/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1861452] Re: sru curtin 2020-02-14 - 19.3-26-g82f23e3d-0ubuntu1
** Changed in: curtin (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1861452 Title: sru curtin 2020-02-14 - 19.3-26-g82f23e3d-0ubuntu1 Status in curtin package in Ubuntu: Fix Released Status in curtin source package in Xenial: Fix Committed Status in curtin source package in Bionic: Fix Committed Status in curtin source package in Eoan: Fix Committed Bug description: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: - multipath removal handling - centos8 support - curthooks update initramfs only once for faster deployment - block schema updates for raid, vtoc and ptable - vmtest arch support for ppc64le and aarch64 See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CurtinUpdates Curtin now contains an extensive integration test suite that is ran using the SRU package for each releases. These suite has documentation here: https://curtin.readthedocs.io/en/latest/topics/integration-testing.html In order to avoid regression to existing MAAS product, the MAAS team will run their continuous integration test against the curtin that is in -proposed. A successful run will be required before the proposed curtin can be let into -updates. The curtin team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Curtin team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. Curtin VMTEST results attached: - curtin-vmtest-proposed-x-console.log - curtin-vmtest-proposed-x-artifacts.tar.xz - curtin-vmtest-proposed-x-console-v2.log - curtin-vmtest-proposed-x-artifacts-v2.tar.xz - curtin-vmtest-proposed-b-console.log - curtin-vmtest-proposed-b-artifacts.tar.xz - curtin-vmtest-proposed-b-console-v2.log - curtin-vmtest-proposed-b-artifacts-v2.tar.xz - curtin-vmtest-proposed-e-console.log - curtin-vmtest-proposed-e-artifacts.tar.xz - curtin-vmtest-proposed-e-artifacts-v2.tar.xz MAAS QA proposed results attached: - maas-qa-curtin-sru-xenial.zip - maas-qa-curtin-sru-bionic.zip CDO QA results - https://solutions.qa.canonical.com/#/testplans/testplaninstance/e303f452-9467-4f55-9eec-49dd3b6aeff6 [Discussion] == End SRU Template == == changelog == curtin (19.3-26-g82f23e3d-0ubuntu1~19.10.1) - install-grub: refactor uefi partition/disk searching (LP: #1862846) - doc: update Canonical contributors URL [Paul Tobias] - block-discover: detect additional "extended" partition types in MBR (LP: #1861251) - vmtests: skip focal bcache tests due to kernel bug - net/deps.py: detect openvswitch cfg and install openvswitch packages - vmtest: collection of vmtest related fixes to make things triple green (LP: #1862971) - clear-holders: umap the parent mpath to wipe the underlying partitions (LP: #1862973) - vmtests: bump fixby date out and fix false positive when date passes - vmtests: drop disco tests using a tool to automate the process curtin (19.3-17-g50ffca46-0ubuntu1~19.10.1) - clear-holders: ensure we wipe device even if multipath enabled not not mp - block_meta: use reliable fs_spec entries for block devices (LP: #1851899) - multipath: handle removal of multipath partitions correctly (LP: #1857042) - vmtests: skip Focal deploying Centos70 ScsiBasic - vmtests: fix network mtu tests, separating ifupdown vs networkd - doc: Fix kexec documentation bug. [Mike Pontillo] - vmtests: Add Focal Fossa - centos: Add centos/rhel 8 support, enable UEFI Secure Boot [Lee Trager] (LP: #1788088) - Bump XFS /boot skip-by date out a while - vmtest: Fix a missing unset of OUTPUT_FSTAB - curthooks: handle s390x/aarch64 kernel install hooks (LP: #1856038) - clear-holders: handle arbitrary order of devices to clear - curthooks: only run update-initramfs in target once (LP: #1842264) - test_network_mtu: bump fixby date for MTU tests - block-discover: don't skip partitions on virtual devices (LP: #1853018) - block-discover: handle partial probe data (LP: #1852351) - Fix parsing of squashfs: uri prefix for installation sources [Daniel Fox] (LP: #1851271) - Release 19.3 (LP: #1851390) - Update HACKING.rst with Josh
[Group.of.nepali.translators] [Bug 1831772] Re: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1
Not an upstream bug. ** Changed in: curtin Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1831772 Title: sru curtin 2019-06-05 - 19.1-7-g37a7a0f4-0ubuntu1 Status in curtin: Invalid Status in curtin package in Ubuntu: New Status in curtin source package in Xenial: New Status in curtin source package in Bionic: New Status in curtin source package in Cosmic: New Status in curtin source package in Disco: New Bug description: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: * See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CurtinUpdates Curtin now contains an extensive integration test suite that is ran using the SRU package for each releases. These suite has documentation here: https://curtin.readthedocs.io/en/latest/topics/integration-testing.html In order to avoid regression to existing MAAS product, the MAAS team will run their continuous integration test against the curtin that is in -proposed. A successful run will be required before the proposed curtin can be let into -updates. The curtin team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Curtin team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. [Discussion] == End SRU Template == To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1831772/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1819067] Re: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1
** Changed in: cloud-init (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1819067 Title: cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1 Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Bionic: Fix Released Status in cloud-init source package in Cosmic: Fix Released Status in cloud-init source package in Disco: Fix Released Bug description: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: * cc_apt_pipelining: stop disabling pipelining by default * Enable encrypted_data_bag_secret support for Chef * azure: Filter list of ssh keys pulled from fabric [Jason Zions (MSFT)] * EC2: Rewrite network config on AWS Classic instances every boot * netplan: Don't render yaml aliases when dumping netplan * clean: cloud-init clean should not trace when run from within cloud_dir See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CloudinitUpdates The cloud-init team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. cloud-init team members will not mark ‘verification-done’ until this has happened. * Automated Test Results DONE: attach automated cloud-init-proposed test artifacts from tests for each release with lxd artifacts DONE: attach automated cloud-init-proposed test artifacts from tests for each release with kvm artifacts DONE: attach MAAS Team test results for each SRU release * Manual Test Results DONE: attach manual cloud-init-proposed test artifacts from tests for each release on ec2 datasource DONE: attach manual cloud-init-proposed test artifacts from tests for each release on gce datasource DONE: attach manual cloud-init-proposed test artifacts from tests for each release on azure datasource [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. == End SRU Template == == Changelog == cloud-init (18.5-45-g3554ffe8-0ubuntu1) disco; urgency=medium * New upstream snapshot. - cloud-init-per: POSIX sh does not support string subst, use sed (LP: #1819222) -- Daniel Watkins Fri, 08 Mar 2019 17:42:34 -0500 cloud-init (18.5-44-g7c07af28-0ubuntu2) disco; urgency=medium * d/postinst: remove now-incorrect apt pipelining configuration -- Daniel Watkins Fri, 08 Mar 2019 09:56:42 -0500 cloud-init (18.5-44-g7c07af28-0ubuntu1) disco; urgency=medium * New upstream snapshot. - Support locking user with usermod if passwd is not available. [Scott Moser] - Example for Microsoft Azure data disk added. [Anton Olifir] - clean: correctly determine the path for excluding seed directory - helpers/openstack: Treat unknown link types as physical (LP: #1639263) - drop Python 2.6 support and our NIH version detection - tip-pylint: Fix assignment-from-return-none errors - net: append type:dhcp[46] only if dhcp[46] is True in v2 netconfig [Kurt Stieger] - cc_apt_pipelining: stop disabling pipelining by default - tests: fix some slow tests and some leaking state - util: don't determine string_types ourselves - cc_rsyslog: Escape possible nested set - Enable encrypted_data_bag_secret support for Chef [Eric Williams] - azure: Filter list of ssh keys pulled from fabric [Jason Zions (MSFT)] - doc: update merging doc with fixes and some additional details/examples - tests: integration test failure summary to use traceback if empty error - cloud-init-per mishandles commands with dashes [Vitaly Kuznetsov] - EC2: Rewrite network config on AWS Classic instances every boot [Guilherme G. Piccoli] - netinfo: Adjust ifconfig output parsing for FreeBSD ipv6 entries - netplan: Don't render yaml aliases when dumping netplan - add PyCharm IDE .idea/ path to .gitignore [Dominic Schlegel] - correct grammar issue in instance metadata documentation [Dominic Schlegel] - clean: cloud-init clean should not trace when run from within cloud_dir - Resolve flake8 comparison and pycodestyle over-ident issues [Paride Legovini] * Update netplan dependency package * Fix build-depends-on-obsolete-package for dh-systemd * Change Priority from extra to optional * Override lintian
[Group.of.nepali.translators] [Bug 1655440] Re: "unconfigured" NIC can still get IPv6 addresses via RA
Curtin will pass the MAAS provided network config to the target. In netplan format, the accept-ra configuration is present and this will be passed through to the target system and reflected in the installed system. I'm marking the curtin portion here invalid. If curtin does need to do something (for say xenial deployments/ifupdown) then please re-open the task and we'll triage accordingly. ** Changed in: curtin Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1655440 Title: "unconfigured" NIC can still get IPv6 addresses via RA Status in curtin: Invalid Status in MAAS: Triaged Status in netplan: Fix Released Status in nplan package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Released Status in nplan source package in Zesty: Fix Released Bug description: [Impact] Some users omit configuration for some interfaces, and expect that the lack of configuration translates to "no IP address" on the interface, as per netplan documentation. [Test case] /!\ Requires an IPv6-capable network. 1) Update nplan. 2) Ensure the nplan configure includes the 'accept-ra: no' option. 3) Run 'netplan apply' 4) Verify that there is no IPv6 address set for the interface where 'accept-ra: no is set; using 'ip -6 addr'. [Regression potential] Incorrect configuration of the IPv6 addresses on a device would consistute a regression: for instance, getting an IPv6 SLAAC address when 'accept-ra: no' is set; or no IPv6 address when RAs are being received and 'accept-ra' is not set. Furthermore, possible regressions may look like incorrect IPv6 configuration or missing options on IPv6 or IPv4 setups, in the form of not retrieving an IP address or getting the wrong IP. --- TL;DR A MAAS NIC that is set to "unconfigured" (or "link up") will get no IPv4 address, but it might still get an IPv6 address via router advertisements (RA), if there is such a service in that network segment. Whether this is a bug or not is up for discussion. That's the point of this ticket, actually, so that this discussion can be had and be recorded. We found out about this when we couldn't get any connectivity to instances of an openstack cloud deployed by the autopilot. After much debugging, we found that the problem was with the br-data bridge on the neutron-gateway node: it didn't have the external NIC (eth1) as part of the bridge. The neutron-gateway charm, before adding any NIC to a bridge, performs certain checks to see if it's really unused. One of these checks looks for IP addresses on the NIC, both IPv4 and IPv6. In MAAS, that node had eth1 set to "unconfigured", so that eth1 is just "up", but has no IP (v4) address. Turns out this NIC had gotten an IPv6 ULA from an openwrt router in that network segment. That was enough for the charm to not add it to the br-data bridge, thus breaking connectivity to openstack instances that were later brought up. We shut down the RA service on the openwrt router and then everything worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1655440/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1817964] Re: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1
** Changed in: curtin (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1817964 Title: sru curtin 2019-02-27 - 18.2-10-g7afd77fa-0ubuntu1 Status in curtin package in Ubuntu: Fix Released Status in curtin source package in Xenial: New Status in curtin source package in Bionic: New Status in curtin source package in Cosmic: New Status in curtin source package in Disco: Fix Released Bug description: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: * - dname: relax dname req for disk serial/wwn presence for compatibility (LP: #1735839) - clear-holders: handle FileNotFound when probing for bcache device slaves (LP: #187) - Adjust helpers/common to edit GRUB_CMDLINE_LINUX_DEFAULT in place. (LP: #1527664) - dname: persistent names based on serial or wwn (LP: #1735839) - Fix bug in is_swap_device if a device was smaller than page_size. (LP: #1803672) - Add clear-holders to meta-simple (LP: #1786736) - block_meta: use wipe config when clearing partitions (LP: #1800153) - apt: Use new format apt config when writing preserve_sources_list. (LP: #1735950) See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CurtinUpdates Curtin now contains an extensive integration test suite that is ran using the SRU package for each releases. These suite has documentation here: https://curtin.readthedocs.io/en/latest/topics/integration-testing.html In order to avoid regression to existing MAAS product, the MAAS team will run their continuous integration test against the curtin that is in -proposed. A successful run will be required before the proposed curtin can be let into -updates. The curtin team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Curtin team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. [Other Info] This SRU will be replacing the current version in -proposed (LP: #1795712) [Discussion] == End SRU Template == curtin (18.2-10-g7afd77fa-0ubuntu1) disco; urgency=medium * New upstream snapshot. - Support for multi-layers images fsimage-layered:// URI [Jean-Baptiste Lallement] - dname: relax dname req for disk serial/wwn presence for compatibility (LP: #1735839) - flake8: fix some E117 over-indented issues [Paride Legovini] - bcache: ensure partitions on bcache devices are detected as partition - vmtest: bump skip_by_date out a year for trusty bcache bug - Fix typo in doc/topics/integration-testing.rst. [Paride Legovini] - flake8: Fix two issues found with new version of flake8 - clear-holders: handle FileNotFound when probing for bcache device slaves (LP: #187) - vmtests: network mtu fix-by bump to post 19.04 release - vmtest: Fix bug preventing explicit disabling of system_upgrade. -- Ryan Harper Wed, 27 Feb 2019 16:43:21 -0600 curtin (18.2-0ubuntu1) disco; urgency=medium * New upstream release (18.2). - Release 18.2 - Adjust helpers/common to edit GRUB_CMDLINE_LINUX_DEFAULT in place. (LP: #1527664) - dname: persistent names based on serial or wwn (LP: #1735839) - Fix bug in is_swap_device if a device was smaller than page_size. (LP: #1803672) - vmtest: add disco tests [Joshua Powers] - unittest: change directory to tmpdir for testing relative files. - Add clear-holders to meta-simple (LP: #1786736) - vmtests: check install log for Out of memory kernel messages and fail - unittest: correctly use tmpdir for my.img [Joshua Powers] (LP: #1803611) - block_meta: use wipe config when clearing partitions (LP: #1800153) - tests: fix vmtests for apt perserve_source_list changes - apt: Use new format apt config when writing preserve_sources_list. (LP: #1735950) - vmtests: multipath mount /home with nofail and validate in unittest - vmtests: fix common collect scripts to not exit failure. - vmtest: handle collect disk unpack failure - vmtests: dont use multiple subclasses in uefi 4k tests - vmtests: disable snapd/seeding to avoid boot hang - jenkins-runner: fix when using --filter only -- Ryan Harper Thu, 06
[Group.of.nepali.translators] [Bug 74747] Re: Default sources.list file has source packages enabled by default
This bug is believed to be fixed in cloud-init in version 18.5. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: cloud-init Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/74747 Title: Default sources.list file has source packages enabled by default Status in cloud-init: Fix Released Status in apt-setup package in Ubuntu: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in apt-setup source package in Xenial: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in apt-setup source package in Bionic: Fix Released Status in cloud-init source package in Bionic: Confirmed Status in apt-setup source package in Cosmic: Fix Released Status in cloud-init source package in Cosmic: Fix Released Bug description: The default sources.list file has source packages enabled by default, this is bad for the average user (especially those on modems) because they are very unlikely to use source packages, however they will still have the download overhead of the packages list. For most people the deb-src lines could simply be commented out by default. (Bug reported at the behest of Robert Collins) Implementing this would probably invalidate bug 301602. See also bug 987264. Mailing list discussion: https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2013-May/thread.html#14503 https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2013-July/thread.html#14617 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/74747/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1798424] Re: Xenial Azure: Make generation of network config from IMDS hotplug scripts configurable opt-in
This bug is believed to be fixed in cloud-init in version 18.5. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: cloud-init Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1798424 Title: Xenial Azure: Make generation of network config from IMDS hotplug scripts configurable opt-in Status in cloud-init: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Bug description: === Begin SRU Template === [Impact] By default, Xenial needs to rely on existing cloud image hotplug scripts and only generate fallback network config (dhcp on eth0) by default. If consumers want to generate dynamic network from Azure's IMDS service, thus removing cloud image hotplug scripts, then a datasource configuration option is surfaced. [Test Case] 1. Deploy stock Xenial cloud image 2. upgrade cloud-init -proposed 3. Run cloud-init clean --reboot --logs 4. Confirm that network is not sourced from IMDS content and hotplug scripts still exist 5. Add datasource configuration setting Azure: apply_network_config: true 6. Run cloud-init clean --reboot --logs 7. Confirm that network is sourced from IMDS and hotplug scripts are removed. [Regression Potential] [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=15a75ea1 === End SRU Template === === Original Description === cloud-init v. 18.4-0ubuntu1~16.04.1 in -proposed automatically renders network configuration from Azure's IMDS by default instead of fallback config of dhcp on eth0. This represents a difference in behavior from current Xenial. On Xenial Azure, Ubuntu cloud images have udev scripts to handle network hotplug. Azure datasource has the ability to read full network config from their IMDS service and render hotplugged devices as well as remove the cloud-image default scripts. Make the cloud-init hotplug behavior configurable and default it to off in Xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1798424/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1728742] Re: curtin dname for bcache uses unstable devname instead of UUID
This bug is believed to be fixed in curtin in version18.1-17-gae48e86f-
0ubuntu1. If this is still a problem for you, please make a comment and
set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1728742
Title:
curtin dname for bcache uses unstable devname instead of UUID
Status in bcache-tools:
New
Status in curtin:
Fix Released
Status in curtin package in Ubuntu:
Fix Released
Status in bcache-tools source package in Trusty:
Invalid
Status in curtin source package in Trusty:
Won't Fix
Status in bcache-tools source package in Xenial:
Invalid
Status in curtin source package in Xenial:
New
Status in bcache-tools source package in Artful:
Invalid
Status in curtin source package in Artful:
New
Status in bcache-tools source package in Bionic:
Invalid
Status in curtin source package in Bionic:
Fix Released
Status in bcache-tools package in Debian:
Confirmed
Bug description:
[Impact]
* Current users of bcache devices may encounter unreliable device
numbering as the Linux kernel does not guarantee that bcache
minor numbers are assigned to the same devices at each boot.
Users who may have used /dev/bcacheN in paths to a specific
device could possible be pointing to a different dataset
altogether. bcache udev rules do provide some mechanism to
generate persistent symlinks in /dev/bcache/by-uuid or
/dev/bcache/by-label which is based on superblock data on
the underlying device. However, the Linux kernel does not
always generate an kernel uevent to trigger the udev rules
to create the symlink.
* The fix adds a udev program which will read bcache superblock
of slave devices and extract the UUID and LABEL, exporting them
to udev for use in the bcache rule files.
* This is affected in upstream bcache-tools, the owning package
of the udev rules. This affects all releases of bcache-tools
as the rules rely upon the kernel to trigger these events,
though that is not a requirement to resolve the lack of
persistent links.
[Test Case]
* Launch and Ubuntu Cloud Image with 3 unused disks
- apt install bcache-tools tree
- make-bcache -C /dev/vdb
- make-bcache -B /dev/vdc
- make-bcache -B /dev/vdd
- echo "vdc" > /sys/class/block/bcache0/bcache/label
- echo "vdd" > /sys/class/block/bcache1/bcache/label
- reboot
- Run this test:
#!/bin/bash
FAIL=0
[ ! -d /dev/bcache ] && {
echo "FAIL: /dev/bcache is not a directory";
exit 1
}
for label in /dev/bcache/by-label/*; do
LABEL_TARGET="$(ls -1 /sys/class/block/`basename $label`/holders/)"
DEVNAME=`readlink -f $label`;
KNAME="${DEVNAME#*/dev/}"
if [ "$LABEL_TARGET" != "$KNAME" ]; then
echo "FAIL: label points to $LABEL_TARGET but symlink points to
$DEVNAME";
FAIL=1
fi;
done
if [ "$FAIL" == "0" ]; then
echo "PASS";
exit 0
fi
exit 1
[Regression Potential]
* As bcache minor numbers and these symlinks have been unreliable in
the past there may be code that makes assumptions about
/dev/bcache* expanded only to the block devices, versus
/dev/bcache which is a directory.
[Original Description]
Bcache device names like /dev/bcache0 are unstable. Bcache does not
use any predictable ordering when assembling bcache devices, so on
systems with multiple bcache devices, a symlink to /dev/bcache0 may
end up pointing do a different device.
the bcache dname symlink should point to the /dev/bcache/by-
uuid/ which matches the backing device UUID that's set at
creation time.
Related bugs:
* bug 1729145: [kernel] /dev/bcache/by-uuid links not created after reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/bcache-tools/+bug/1728742/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1761240] Re: SRU pollinate 4.31
** Also affects: pollinate (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: pollinate (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: pollinate (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1761240 Title: SRU pollinate 4.31 Status in pollinate package in Ubuntu: New Status in pollinate source package in Trusty: New Status in pollinate source package in Xenial: New Status in pollinate source package in Artful: New Bug description: === Begin SRU Template === [Impact] The key change is that the user agent string as of Bionic now contains the contents of systemd-detect-virt and /etc/cloud/build.info. In aggregate, this gives us important usage data to detect improvements and regressions in Ubuntu boot times. [Test Case] Launch a privileged container with: 1. lxc launch ubuntu-daily:xenial -c security.privileged=true x1-priv 2. lxc exec x1-priv -- apt update && apt -y install pollen Run a local pollen server and have the pollinate (client) connect with that via: 3. lxc exec x1-priv -- pollinate -r --insecure -s https://localhost Then check in /var/log/syslog for the client user-agent string. On systems without the updated pollinate client, the USER_AGENT value does not include virt: root@x1-priv:~# grep pollen /var/log/syslog | grep -c virt 0 root@x1-priv:~# After upgrading to the newer client, virt is now present in the pollen entries: root@x1-priv:~# grep pollen /var/log/syslog | grep -c virt 2 root@x1-priv:~# [Regression Potential] The script runs with 'set -e', that means that the 'pollinate' script will exit failure if either of the commands or files above fail. These scenarios seem unlikely, especially in Ubuntu environments. === End SRU Template === To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1761240/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1756987] [NEW] chrony install does not stop systemd-timesyncd
Public bug reported: 1. root@ubuntu:~# lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 root@ubuntu:~# uname -a Linux ubuntu 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 2. root@ubuntu:~# apt-cache policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages root@ubuntu:~# apt-cache policy chrony chrony: Installed: 2.1.1-1 Candidate: 2.1.1-1 Version table: *** 2.1.1-1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status 3. installing chrony should stop systemd-timesyncd so they both don't try to adjust time 4. after chrony is installed both systemd-timesyncd and chronyd are running. root@ubuntu:~# ps aux | egrep "(chrony|timesync)" systemd+ 1086 0.0 0.2 100324 2368 ?Ssl 19:34 0:00 /lib/systemd/systemd-timesyncd _chrony 2770 0.0 0.2 105780 2920 ?S19:38 0:00 /usr/sbin/chronyd root 3077 0.0 0.0 12944 924 pts/0S+ 19:52 0:00 grep -E --color=auto (chrony|timesync) Note, on bionic the chrony package successfully stops systemd-timesyncd and only chronyd remains running after install. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chrony 2.1.1-1 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Mar 19 19:51:06 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chrony UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chrony (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: chrony (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: chrony (Ubuntu Artful) Importance: Undecided Status: New ** Affects: chrony (Ubuntu Bionic) Importance: Undecided Status: Fix Released ** Tags: amd64 apport-bug uec-images xenial ** Also affects: chrony (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: chrony (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: chrony (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: chrony (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1756987 Title: chrony install does not stop systemd-timesyncd Status in chrony package in Ubuntu: Fix Released Status in chrony source package in Xenial: New Status in chrony source package in Artful: New Status in chrony source package in Bionic: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 root@ubuntu:~# uname -a Linux ubuntu 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 2. root@ubuntu:~# apt-cache policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages root@ubuntu:~# apt-cache policy chrony chrony: Installed: 2.1.1-1 Candidate: 2.1.1-1 Version table: *** 2.1.1-1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status 3. installing chrony should stop systemd-timesyncd so they both don't try to adjust time 4. after chrony is installed both systemd-timesyncd and chronyd are running. root@ubuntu:~# ps aux | egrep "(chrony|timesync)" systemd+ 1086 0.0 0.2 100324 2368 ?Ssl 19:34 0:00 /lib/systemd/systemd-timesyncd _chrony 2770 0.0 0.2 105780 2920 ?S19:38 0:00 /usr/sbin/chronyd root 3077 0.0 0.0 12944 924 pts/0S+ 19:52 0:00 grep -E --color=auto (chrony|timesync) Note, on bionic the chrony package successfully stops systemd-timesyncd and only chronyd remains running after install. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chrony 2.1.1-1 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion:
[Group.of.nepali.translators] [Bug 1728742] Re: curtin dname for bcache uses unstable devname instead of UUID
** Bug watch added: Debian Bug tracker #890446 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890446 ** Also affects: bcache-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890446 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1728742 Title: curtin dname for bcache uses unstable devname instead of UUID Status in bcache-tools: New Status in curtin: New Status in bcache-tools package in Ubuntu: In Progress Status in bcache-tools source package in Trusty: Confirmed Status in bcache-tools source package in Xenial: Confirmed Status in bcache-tools source package in Artful: Confirmed Status in bcache-tools source package in Bionic: In Progress Status in bcache-tools package in Debian: Unknown Bug description: Bcache device names like /dev/bcache0 are unstable. Bcache does not use any predictable ordering when assembling bcache devices, so on systems with multiple bcache devices, a symlink to /dev/bcache0 may end up pointing do a different device. the bcache dname symlink should point to the /dev/bcache/by- uuid/ which matches the backing device UUID that's set at creation time. To manage notifications about this bug go to: https://bugs.launchpad.net/bcache-tools/+bug/1728742/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
