[Group.of.nepali.translators] [Bug 1844400] Re: xenial/linux-deeplens: 4.15.0-1009.9 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available on ccc and as attachment. Amazon AWS DeepLens: https://certification.canonical.com/hardware/201801-26078/submission/151197/ Amazon AWS DeepRacer: https://certification.canonical.com/hardware/201903-26883/submission/151196/ ** Changed in: kernel-sru-workflow/certification-testing 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/1844400 Title: xenial/linux-deeplens: 4.15.0-1009.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1844401 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Testing phase-changed: Thursday, 19. September 2019 20:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress replaces: bug 1842592 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844400/+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 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem
This bug has not seen any activity in the last 6 months, so it is being automatically closed. If you are still experiencing this issue, please feel free to re-open. MAAS Team ** Changed in: maas Status: Confirmed => 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/1629972 Title: networking stop incorrectly disconnects from (network) root filesystem Status in MAAS: Invalid Status in ifupdown package in Ubuntu: Fix Released Status in ifupdown source package in Xenial: Fix Released Status in ifupdown source package in Yakkety: Fix Released Status in ifupdown package in Debian: Fix Released Bug description: === Begin SRU Template === [Impact] The systemd networking.service unit will bring down the loopback device (lo) when it is stopped. This behavior differs from the behavior in other Ubuntu releases (upstart's networking.conf), where 'lo' is not taken down. The problem that was seen was that iscsi root over ipv6 would hang on shutdown. [Test Case] Test is fairly simple and can be demonstrated in lxc container. The key is really that the lo device should not have its link set down after stopping networking.service. So, below: out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty should not show 'empty', but should have LOOPBACK,UP,LOWER in its output. $ release=yakkety; name=y1 $ lxc launch ubuntu-daily:$release $name $ sleep 10 $ lxc exec $name /bin/bash ## show only things that are up (note output has LOOPBACK,UP,LOWER_UP) % ip link show dev lo 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 % ip address show dev lo up 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever ## Stop the service and show lo link is down (no 'UP' or 'LOWER_UP'). % systemctl stop networking.service % ip link show dev lo 1: lo: mtu 65536 qdisc noqueue state DOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty empty ## Now enable proposed, install update, reboot and show. % rel=$(lsb_release -sc) % echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" | sudo tee /etc/apt/sources.list.d/proposed.list % sudo apt update -qy && sudo apt install -qy ifupdown mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 % ip address show dev lo up 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever % systemctl stop networking.service % ip link show dev lo 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever [Regression Potential] Should be pretty low. zesty and yakkety-proposed have this. Taking down 'lo' is often cause of problems, and never the solution to problems as far as I'm aware. [Other Info] === End SRU Template === With the switch to systemd, all support for iscsi root (and other) filesystems disappeared, since shutdown yanks the rug out from under us. Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i creates..), the DEV check should be expanded to include iscsi devices, and networking.service ExecStop should honor those checks. Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1621507: ipv6 network boot does not work To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1629972/+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
[Group.of.nepali.translators] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
Reopening the ibus (ubuntu) task. Background: The change in ibus 1.5.19-1ubuntu3, which set the abstract socket path to 'unix:tmpdir=/tmp/ibus', was upstreamed and is now included in the 1.5.21 source. However, the path proved to not work well on BSD systems: https://github.com/ibus/ibus/issues/2116 That resulted in a new upstream approach to make the path indistinguishable, and to make a long story short, the path is about to be changed in 1.5.22 to 'unix:tmpdir=$XDG_CACHE_HOME/ibus'. To prevent yet another change in this respect in the ff cycle, I propose that we change it in eoan again and add two upstream commits so Ubuntu 19.10 is released with the new (final?) path. Proposed upload in this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus ** Bug watch added: github.com/ibus/ibus/issues #2116 https://github.com/ibus/ibus/issues/2116 ** Changed in: ibus (Ubuntu) Status: Fix Released => In Progress -- 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/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in ibus: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in ibus package in Ubuntu: In Progress Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Released Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes
[Group.of.nepali.translators] [Bug 1686086] Re: glance mirror and nova-lxd need support for squashfs images
For Xenial SRU, please read summary at: https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1686437/comments/19 ** Changed in: simplestreams (Ubuntu Xenial) Status: Confirmed => In Progress ** Also affects: simplestreams (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: simplestreams (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: simplestreams (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: simplestreams (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: simplestreams (Ubuntu Xenial) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: simplestreams (Ubuntu Bionic) Status: New => Fix Released ** Changed in: simplestreams (Ubuntu Disco) Status: New => Fix Released ** Description changed: + [Impact] + Zesty does not produce root.tar.gz or root.tar.xz images. This means that for a nova lxd cloud we need some changes to support zesty images. * simplestreams will need to learn that lxd can support a 'squashfs' image type, and how to upload that to glance (what 'disk_format' option to put on the glance image). * nova-lxd will need to know that it can handle squashfs images (it may already do that) * nova-lxd will possibly need to do something special with that. + + [Test Case] + + According to comment #4, a reproducer was hard to be found. + + [Regression Potential] + + This part was added specifically for the Xenial backport, including: + + - 455-nova-lxd-support-squashfs-images.patch (LP: #1686086) + + And chances of regression are small based on the MR feedback from SEG + and this particular bug already stating the issue was fixed. + + [Other Info] + + N/A -- 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/1686086 Title: glance mirror and nova-lxd need support for squashfs images Status in nova-lxd: Fix Released Status in simplestreams: Fix Released Status in simplestreams package in Ubuntu: Fix Released Status in simplestreams source package in Xenial: In Progress Status in simplestreams source package in Artful: Won't Fix Status in simplestreams source package in Bionic: Fix Released Status in simplestreams source package in Disco: Fix Released Bug description: [Impact] Zesty does not produce root.tar.gz or root.tar.xz images. This means that for a nova lxd cloud we need some changes to support zesty images. * simplestreams will need to learn that lxd can support a 'squashfs' image type, and how to upload that to glance (what 'disk_format' option to put on the glance image). * nova-lxd will need to know that it can handle squashfs images (it may already do that) * nova-lxd will possibly need to do something special with that. [Test Case] According to comment #4, a reproducer was hard to be found. [Regression Potential] This part was added specifically for the Xenial backport, including: - 455-nova-lxd-support-squashfs-images.patch (LP: #1686086) And chances of regression are small based on the MR feedback from SEG and this particular bug already stating the issue was fixed. [Other Info] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/nova-lxd/+bug/1686086/+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 1583276] Re: glance restarted during image upload, image stuck in "saving" state
** Description changed:
+ [Impact]
+
CI run: https://ci.lscape.net/job/landscape-system-tests/2451/
gs3 log attached. Below some excerpts:
It looks like the problem started when it uploaded the first image (14.04) to
glance. That failed:
WARNING * 05-18 13:36:48 [PID:10259] * root * No rabbitmq connection
available for msg{'status': 'Syncing', 'message':
'ubuntu-trusty-14.04-amd64-server-20160516 99%\n
DEBUG * 05-18 13:36:50 [PID:10259] * glanceclient.common.http * curl -i
-X POST -H 'x-image-meta-property-source_content_id:
com.ubuntu.cloud:released:download' -H 'INFO * 05-18 13:37:01 [PID:10364]
* root * glance-simplestreams-sync started.
INFO * 05-18 13:37:01 [PID:10364] * root *
/var/run/glance-simplestreams-sync.pid is locked, exiting
ERROR * 05-18 13:37:07 [PID:10259] * root * Glance Client exception
during do_sync:
Error communicating with http://10.96.10.146:9292 [Errno 32] Broken pipe
Will continue polling.
Traceback (most recent call last):
- File "/usr/share/glance-simplestreams-sync/glance-simplestreams-sync.py",
line 444, in main
- do_sync(charm_conf, status_exchange)
- File "/usr/share/glance-simplestreams-sync/glance-simplestreams-sync.py",
line 215, in do_sync
- tmirror.sync(smirror, path=initial_path)
- File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/__init__.py",
line 91, in sync
- return self.sync_index(reader, path, data, content)
- File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/__init__.py",
line 254, in sync_index
- self.sync(reader, path=epath)
- File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/__init__.py",
line 89, in sync
- return self.sync_products(reader, path, data, content)
- File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/__init__.py",
line 341, in sync_products
- self.insert_item(item, src, target, pgree, ipath_cs)
- File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/glance.py",
line 303, in insert_item
- ret = self.gclient.images.create(**create_kwargs)
- File "/usr/lib/python2.7/dist-packages/glanceclient/v1/images.py", line
253, in create
- 'POST', '/v1/images', headers=hdrs, body=image_data)
- File "/usr/lib/python2.7/dist-packages/glanceclient/common/http.py", line
289, in raw_request
- return self._http_request(url, method, **kwargs)
- File "/usr/lib/python2.7/dist-packages/glanceclient/common/http.py", line
235, in _http_request
- raise exc.CommunicationError(message=message)
+ File "/usr/share/glance-simplestreams-sync/glance-simplestreams-sync.py",
line 444, in main
+ do_sync(charm_conf, status_exchange)
+ File "/usr/share/glance-simplestreams-sync/glance-simplestreams-sync.py",
line 215, in do_sync
+ tmirror.sync(smirror, path=initial_path)
+ File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/__init__.py",
line 91, in sync
+ return self.sync_index(reader, path, data, content)
+ File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/__init__.py",
line 254, in sync_index
+ self.sync(reader, path=epath)
+ File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/__init__.py",
line 89, in sync
+ return self.sync_products(reader, path, data, content)
+ File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/__init__.py",
line 341, in sync_products
+ self.insert_item(item, src, target, pgree, ipath_cs)
+ File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/glance.py",
line 303, in insert_item
+ ret = self.gclient.images.create(**create_kwargs)
+ File "/usr/lib/python2.7/dist-packages/glanceclient/v1/images.py", line
253, in create
+ 'POST', '/v1/images', headers=hdrs, body=image_data)
+ File "/usr/lib/python2.7/dist-packages/glanceclient/common/http.py", line
289, in raw_request
+ return self._http_request(url, method, **kwargs)
+ File "/usr/lib/python2.7/dist-packages/glanceclient/common/http.py", line
235, in _http_request
+ raise exc.CommunicationError(message=message)
CommunicationError: Error communicating with http://10.96.10.146:9292 [Errno
32] Broken pipe
INFO * 05-18 13:37:07 [PID:10259] * root * sync done.
INFO * 05-18 13:38:01 [PID:10372] * root * glance-simplestreams-sync
started.
+
+ [Test Case]
Found evidence in the juju logs for glance/0 that it restarted right at
13:37:07:
2016-05-18 13:37:07 INFO ceph-relation-changed ^MReading state information...
0%^MReading state information... 0%^MReading state information... Done
2016-05-18 13:37:07 INFO juju-log ceph:50: Loaded template from
templates/ceph.conf
2016-05-18 13:37:07 INFO juju-log ceph:50: Rendering from template: ceph.conf
2016-05-18 13:37:07 INFO juju-log ceph:50: Wrote template
/var/lib/charm/glance/ceph.conf.
2016-05-18 13:37:07 INFO ceph-relation-changed glance-api stop/waiting
2016-05-18 13:37:07 INFO ceph-relation-changed glance-api start/running,
process 62839
[Group.of.nepali.translators] [Bug 1728982] Re: [SRU] openstack mirror with keystone v3 always imports new images
** Also affects: simplestreams (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: simplestreams (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: simplestreams (Ubuntu Xenial) Status: New => Fix Released ** Changed in: simplestreams (Ubuntu Xenial) Status: Fix Released => In Progress ** Changed in: simplestreams (Ubuntu Xenial) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: simplestreams (Ubuntu Disco) Status: New => Fix Released ** Changed in: simplestreams (Ubuntu Bionic) Importance: High => Medium ** Changed in: simplestreams (Ubuntu) Importance: High => Medium -- 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/1728982 Title: [SRU] openstack mirror with keystone v3 always imports new images Status in simplestreams: Fix Released Status in simplestreams package in Ubuntu: Fix Released Status in simplestreams source package in Xenial: In Progress Status in simplestreams source package in Artful: Won't Fix Status in simplestreams source package in Bionic: Fix Released Status in simplestreams source package in Disco: Fix Released Bug description: [Impact] On every execution of /etc/cron.*/glance_simplestreams_sync simplestreams will upload all the images that match the configured filters no matter of those same images were already uploaded in a previous execution. This will potentially lead to the inability to upload new images due to not having enough free space. [Test Case] * deploy artful-pike juju deploy ./artful-pike.yaml # http://paste.ubuntu.com/p/RZqm3cGjqk/ * Wait until glance-simplestreams-sync runs the first sync-up execution. * Verify the images are in glance running "openstack image list" * Run the synchronization script again juju ssh glance-simplestreams-sync/0 sudo /etc/cron.daily/glance_simplestreams-sync Expected results: "openstack image list" prints the same list of images as before running the synchronization script for the 2nd time Actual result: "openstack image list" prints a list of images duplicates, e.g.: $ openstack image list +--+---++ | ID | Name | Status | +--+---++ | 7f946cbf-57e1-4704-92ea-928d8d4e9454 | auto-sync/ubuntu-trusty-14.04-amd64-server-20180404-disk1.img | active | | 7a5afbf8-f072-49af-9629-483fc27c627a | auto-sync/ubuntu-trusty-14.04-amd64-server-20180404-disk1.img | active | | c9a1dfbd-9e5d-4261-b43f-585e65f9733a | auto-sync/ubuntu-xenial-16.04-amd64-server-20180405-disk1.img | active | | a731c994-61f3-43ea-b86c-227baec101e3 | auto-sync/ubuntu-xenial-16.04-amd64-server-20180405-disk1.img | active | +--+---++ [Potential Regression] * this patch allows simplestreams to connect to swift and verify if the image was already uploaded or not, any possible regression will manifest around the ability of simplestreams to connect to swift. [Other Info] When using the newly added (revno 450) v3 support for mirroring to openstack simplestreams will not notice that images already exist in glace. The result is that every 'sync' will import all new images. The issue was simply that the tenant_id was not being correctly passed through to the glance query. It ended considering only existing images that were owned by None, which didn't match anything. Note: * This bug is present in Artful when using the v3 keystone api. It is *not* present in xenial or zesty as they do not have v3 keystone support, and the code that is submitted for merge request has the fix included. To manage notifications about this bug go to: https://bugs.launchpad.net/simplestreams/+bug/1728982/+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 1719879] Re: [SRU] swift client needs to use v1 auth prior to ocata
** Also affects: simplestreams (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: simplestreams (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: simplestreams (Ubuntu Xenial) Status: New => In Progress ** Changed in: simplestreams (Ubuntu Xenial) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: simplestreams (Ubuntu Disco) Status: New => Fix Released ** Changed in: simplestreams (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: simplestreams (Ubuntu Disco) Importance: Undecided => Medium -- 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/1719879 Title: [SRU] swift client needs to use v1 auth prior to ocata Status in simplestreams: Fix Released Status in simplestreams package in Ubuntu: Fix Released Status in simplestreams source package in Xenial: In Progress Status in simplestreams source package in Artful: Won't Fix Status in simplestreams source package in Bionic: Fix Released Status in simplestreams source package in Disco: Fix Released Bug description: [Impact] Users upgrading their environment by stages may see problems with the image synchronization when swift is left in mitaka (or newton) while other services have been upgraded to keystone, it's common for clouds where the API is availability is strict to do this kind of upgrades. [Test Case] * deploy openstack artful-pike except swift juju deploy ./bundle.yaml # http://paste.ubuntu.com/p/27mzxxX9jC/ * Add swift to the already deployed model juju deploy ./swift.yaml # http://paste.ubuntu.com/p/RzZ2JMBjbg/ * Once things have settled run the script /etc/cron.daily/glance_simplestreams_sync in glance-simplestreams-sync/0 juju ssh glance-simplestreams-sync/0 sudo /etc/cron.daily/glance_simplestreams_sync in glance-simplestreams-sync/0 Expected result: Images for xenial and trusty are uploaded available in glance (openstack image list) Actual result: The synchronization scripts fails due that it's not possible to authenticate with swift [Potential Regression] * This patch attempts to authenticate using v3 and falls back to v2, so environments where keystone is configured to authenticate using v2 AND v3 may see a change in the behavior where simplestreams will be silently preferring v3 over v2 while before this patch only v2 was being used. [Other Info] I talked with David today (thedac) and he mentioned that the support for adding keystone v3 auth to simplestreams glance sync has issues when using older swift clients. The swift client lagged behind other openstack client libraries in gaining support for v3 auth. Note: This bug does not affect xenial or zesty. They do not have the keystone v3 support yet, and the code submitted for SRU contains this fix. Related bugs: * bug 1686437: glance sync: need keystone v3 auth support To manage notifications about this bug go to: https://bugs.launchpad.net/simplestreams/+bug/1719879/+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 1584938] Re: Incomplete simplestreams metadata and failed juju bootstrap
** Also affects: simplestreams (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: simplestreams (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: simplestreams (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: simplestreams (Ubuntu Disco) Status: New => Fix Released ** Changed in: simplestreams (Ubuntu Bionic) Status: New => Fix Released ** Changed in: simplestreams (Ubuntu Xenial) Status: New => In Progress ** Changed in: simplestreams (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: simplestreams (Ubuntu) Importance: High => Medium ** Changed in: simplestreams (Ubuntu Xenial) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Description changed: + [Impact] + This was seen on a Landscape Autopilot deployment (using ceph/ceph) after the fix for lp:1583276 was committed: root@juju-machine-0-lxc-1:/var/lib/landscape/juju-homes/1# juju ssh glance-simplestreams-sync/0 apt-cache policy python-simplestreams Warning: Permanently added 'node-11.vmwarestack,10.245.202.81' (ECDSA) to the list of known hosts. Warning: Permanently added '10.245.201.73' (ECDSA) to the list of known hosts. python-simplestreams: - Installed: 0.1.0~bzr434~trunk-0ubuntu1~ubuntu14.04.1 - Candidate: 0.1.0~bzr434~trunk-0ubuntu1~ubuntu14.04.1 + Installed: 0.1.0~bzr434~trunk-0ubuntu1~ubuntu14.04.1 + Candidate: 0.1.0~bzr434~trunk-0ubuntu1~ubuntu14.04.1 - - The glance-simplestreams-sync.log [1] shows that the xenial image was not completely updated and got stuck in the queued state: + The glance-simplestreams-sync.log [1] shows that the xenial image was + not completely updated and got stuck in the queued state: WARNING * 05-23 16:29:08 [PID:18247] * sstreams * Ignoring inactive image 37d8dfe7-f829-48e0-a66f-aff0cbe0a201 with status 'queued' + The log then shows that another xenial image was downloaded and + ultimately the sync process switches to the daily cron. - The log then shows that another xenial image was downloaded and ultimately the sync process switches to the daily cron. + [Test Case] The problem occurs with the user tries to juju bootstrap with trusty. It appears that the trusty simplestreams metadata is incomplete [2,3] and leads to a failed bootstrap [4]. Creating a trusty instance via horizon (no juju involved) works fine and a bootstrap with xenial works also. - Attached are a collection of logs including all of the pastebins linked + [Regression Potention] + + This part was added specifically for the Xenial backport, including: + + - 436-glance-fix-race-conditions.patch (LP: #1584938) + + And chances of regression are small based on the MR feedback from SEG + and this particular bug already stating the issue was fixed. + + [Other Info] + + Attached are a collection of logs including all the pastebins linked here. [1] - https://pastebin.canonical.com/157049/ [2] - https://pastebin.canonical.com/157058/ [3] - https://pastebin.canonical.com/157059/ [4] - https://pastebin.canonical.com/157060/ -- 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/1584938 Title: Incomplete simplestreams metadata and failed juju bootstrap Status in Glance - Simplestreams Sync Charm: Invalid Status in Landscape Server: Fix Committed Status in Landscape Server 16.06 series: Won't Fix Status in simplestreams: Fix Released Status in simplestreams package in Ubuntu: Fix Released Status in simplestreams source package in Xenial: In Progress Status in simplestreams source package in Bionic: Fix Released Status in simplestreams source package in Disco: Fix Released Bug description: [Impact] This was seen on a Landscape Autopilot deployment (using ceph/ceph) after the fix for lp:1583276 was committed: root@juju-machine-0-lxc-1:/var/lib/landscape/juju-homes/1# juju ssh glance-simplestreams-sync/0 apt-cache policy python-simplestreams Warning: Permanently added 'node-11.vmwarestack,10.245.202.81' (ECDSA) to the list of known hosts. Warning: Permanently added '10.245.201.73' (ECDSA) to the list of known hosts. python-simplestreams: Installed: 0.1.0~bzr434~trunk-0ubuntu1~ubuntu14.04.1 Candidate: 0.1.0~bzr434~trunk-0ubuntu1~ubuntu14.04.1 The glance-simplestreams-sync.log [1] shows that the xenial image was not completely updated and got stuck in the queued state: WARNING * 05-23 16:29:08 [PID:18247] * sstreams * Ignoring inactive image 37d8dfe7-f829-48e0-a66f-aff0cbe0a201 with status 'queued' The log then shows that another xenial image was downloaded and ultimately the sync process switches to the daily cron. [Test Case] The problem occurs with the user tries to juju bootstrap with trusty. It appears that the trusty
[Group.of.nepali.translators] [Bug 1775784] Re: inotify08 in LTP syscall test failed with X/X-LTS/X-HWE/A/B kernel
Test blacklisted, patch: https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=ca9bfef38fe6bf4189b173a7530e8c9dad597111 ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Won't Fix -- 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/1775784 Title: inotify08 in LTP syscall test failed with X/X-LTS/X-HWE/A/B kernel Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Released Bug description: <<>> tag=inotify08 stime=1527762360 cmdline="inotify08" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s inotify08.c:201: INFO: ovl/test_file ino=27918358, dev=8:1 inotify08.c:212: INFO: ovl/test_file ino=27918363, dev=8:1 inotify08.c:150: FAIL: didn't get event: mask=4 inotify08.c:150: FAIL: didn't get event: mask=20 inotify08.c:150: FAIL: didn't get event: mask=8 Summary: passed 0 failed 3 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24~16.04.1 ProcVersionSignature: User Name 4.15.0-22.24~16.04.1-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jun 8 08:08:27 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1775784/+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 1570110] Re: evolution crashed with SIGSEGV, while pasting from clipboard
** Changed in: webkitgtk (Ubuntu Trusty) Status: Confirmed => Won't Fix ** Changed in: webkitgtk (Ubuntu Trusty) Assignee: Sebastien Bacher (seb128) => (unassigned) -- 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/1570110 Title: evolution crashed with SIGSEGV, while pasting from clipboard Status in WebKit: Fix Released Status in webkitgtk package in Ubuntu: Fix Released Status in webkitgtk source package in Trusty: Won't Fix Status in webkitgtk source package in Xenial: Fix Released Bug description: * Impact some webkitgtk consumers like the evolution composer hit segfault issues * Test case - Click New > Compose Email Message - Enter any email address in 'To:' - Enter anything into 'Subject" - Go to any webpage, and highlight a few lines - Click 'ctrl c' - Place cursor into the body of the open Compose Message window - Click 'ctrl v' * Regression potential it's a webkit update so could impact other clients of the library, check that the html rendering in those Guys, Evolution on Xenial crashes most of times that I want to copy and paste stuff into Mail composer window. From what I'm seeing, if the stuff inside of the clipboard is formatted, with big fonts, tables, etc, it crashes. The workaround is to use "Diodon" to paste into Evolution without any formatting, or, to open an vim session on Terminal, paste into it first, then, copy it again from vim, and paste into Evolution, this way, it doesn't crash. Looks very easy to reproduce! Cheers! Thiago ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: evolution 3.18.5.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Wed Apr 13 18:35:02 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2016-01-30 (74 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160130) ProcCmdline: evolution SegvAnalysis: Segfault happened at: 0x7f9bdaf3d949:cmpq $0x0,0x18(%rax) PC (0x7f9bdaf3d949) ok source "$0x0" ok destination "0x18(%rax)" (0x654e2073656d696c) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: evolution StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0 Title: evolution crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/webkit-open-source/+bug/1570110/+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 1836760] Re: ixgbe{vf} - Physical Function gets IRQ when VF checks link state
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: linux (Ubuntu Trusty)
Status: New => In Progress
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
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/1836760
Title:
ixgbe{vf} - Physical Function gets IRQ when VF checks link state
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
In Progress
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux source package in FF-Series:
Fix Released
Bug description:
[Impact]
* Intel NICs that are SR-IOV capable and are managed by ixgbe driver presents
a potentially harmful behavior when the ixgbevf-managed VFs (Virtual Functions)
perform an ethtool link check. The ixgbevf driver issues a mailbox command in
the ethtool link state handler, which induces one IRQ in the PF (Physical
Function) per link check.
* This was reported as a sort of "denial-of-service" from a guest; due to
some link check loop running inside a guest with PCI-PT of a ixgbevf-managed
VF, the host received a huge amount of IRQs causing soft-lockups.
* The patch proposed in this SRU request fix this behavior by relying in the
saved link state (obtained in the ixgbevf's watchdog routine) instead of
issuing a mailbox command to the PF in every link state check request. The
commit is available on Linus tree: 1e1b0c658d9b ("ixgbevf: Use cached link
state instead of re-reading the value for ethtool")
http://git.kernel.org/linus/1e1b0c658d9b
[Test case]
Reproducing the behavior is pretty simple; having a machine with an
Intel NIC managed by ixgbe, proceed with the following steps:
a) Create one or more VFs
(echo 1 > /sys/class/net//device/sriov_numvfs)
b) In a different terminal, monitor the non-TxRx PF IRQs:
(watch -n1 "cat /proc/interrupts | grep | grep -v Tx")
c) Run "ethtool " in a loop
Without the hereby proposed patch, the PF IRQs will increase.
[Regression potential]
The patch scope is restricted to ixgbevf ethtool link-check procedure,
and was developed by the vendor itself. Being a self-contained patch
affecting only this driver's ethtool handler, the worst potential
regression would be a wrong link state report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836760/+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 1842742] Re: xenial/linux-deeplens: 4.15.0-1007.7 -proposed tracker
*** This bug is a duplicate of bug 1844400 *** https://bugs.launchpad.net/bugs/1844400 Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available on ccc and as attachment. Amazon AWS DeepLens: https://certification.canonical.com/hardware/201801-26078/submission/150961/ Amazon AWS DeepRacer: https://certification.canonical.com/hardware/201903-26883/submission/150960/ ** Changed in: kernel-sru-workflow/certification-testing 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/1842742 Title: xenial/linux-deeplens: 4.15.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842744 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Testing phase-changed: Tuesday, 10. September 2019 20:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress replaces: bug 1840004 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842742/+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 1844398] Re: xenial/linux-gcp: 4.15.0-1045.47 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1844403 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Packaging - phase-changed: Wednesday, 18. September 2019 08:26 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 20. September 2019 08:26 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait replaces: bug 1842590 trackers: xenial/linux-gcp/gcp-kernel: bug 1844396 xenial/linux-gcp/gke-kernel: bug 1844397 variant: debs -- 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/1844398 Title: xenial/linux-gcp: 4.15.0-1045.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1844403 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Friday, 20. September 2019 08:26 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait replaces: bug 1842590 trackers: xenial/linux-gcp/gcp-kernel: bug 1844396 xenial/linux-gcp/gke-kernel: bug 1844397 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844398/+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
