[Group.of.nepali.translators] [Bug 1808912] Re: scsi: libsas: fix a race condition when smp task timeout
** Also affects: linux (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/1808912 Title: scsi: libsas: fix a race condition when smp task timeout Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [Impact] When the lldd is processing the complete sas task in interrupt and set the task stat as SAS_TASK_STATE_DONE, the smp timeout timer is able to be triggered at the same time. And smp_task_timedout() will complete the task wheter the SAS_TASK_STATE_DONE is set or not. Then the sas task may freed before lldd end the interrupt process. Thus a use-after-free will happen. [Test Case] This is hard to reproduce, so regression test only. [Fix] b90cd6f2b9 scsi: libsas: fix a race condition when smp task timeout [Regression Risk] Only 2 line moved in libsas and maintainer has reviewed/approved. I will say it's low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808912/+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 1831181] Re: [aodh.notifier] Not setting user_domain_id raises keystone error: The resource could not be found.
** Also affects: cloud-archive 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/1831181 Title: [aodh.notifier] Not setting user_domain_id raises keystone error: The resource could not be found. Status in Aodh: New Status in OpenStack AODH Charm: In Progress Status in charm-interface-keystone: In Progress Status in Ubuntu Cloud Archive: New Status in aodh package in Ubuntu: New Status in aodh source package in Xenial: New Status in aodh source package in Bionic: New Status in aodh source package in Cosmic: New Status in aodh source package in Disco: New Status in aodh source package in Eoan: New Bug description: [Environment] Xenial/Queens [Description] If no user_domain_id is provided then, the following exception will be raised by the aodh-notifier component: $ openstack alarm-history show 1424b6fb-1d9d-4d69-b00a-ad455aad0ecb ==> /var/log/aodh/aodh-notifier.log <== 2019-05-31 02:07:26.663 15274 ERROR aodh.notifier File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/generic/base.py", line 201, in get_auth_ref 2019-05-31 02:07:26.663 15274 ERROR aodh.notifier return self._plugin.get_auth_ref(session, **kwargs) 2019-05-31 02:07:26.663 15274 ERROR aodh.notifier File "/usr/lib/python2.7/dist-packages/keystoneauth1/identity/v2.py", line 63, in get_auth_ref 2019-05-31 02:07:26.663 15274 ERROR aodh.notifier authenticated=False, log=False) 2019-05-31 02:07:26.663 15274 ERROR aodh.notifier File "/usr/lib/python2.7/dist-packages/keystoneauth1/session.py", line 848, in post 2019-05-31 02:07:26.663 15274 ERROR aodh.notifier return self.request(url, 'POST', **kwargs) 2019-05-31 02:07:26.663 15274 ERROR aodh.notifier File "/usr/lib/python2.7/dist-packages/keystoneauth1/session.py", line 737, in request 2019-05-31 02:07:26.663 15274 ERROR aodh.notifier raise exceptions.from_response(resp, method, url) 2019-05-31 02:07:26.663 15274 ERROR aodh.notifier NotFound: (http://10.5.0.36:35357/v2.0/tokens): The resource could not be found. (HTTP 404) (Request-ID: req-50d54903-d2af-4fd1-be68-a92498d91b85) 2019-05-31 02:07:26.663 15274 ERROR aodh.notifier Domain configuration for the aodh service is as follows: root@juju-95497c-controller-1:/home/ubuntu# grep domain /etc/aodh/aodh.conf gnocchi_external_domain_name = service_domain project_domain_name = service_domain user_domain_name = service_domain ### Explanation The following line https://github.com/openstack/aodh/blob/master/aodh/keystone_client.py#L51 enforces the existence of the user_domain_id for getting the authenticated keystone session. [Proposed Solution] * Use user_domain_name as a fallback if no user_domain_id is provided. * The charm templates should provide only user_domain_id if provided orelse fallback to user_domain_name. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1831181/+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 1831443] Re: [hint] [sru] autopkgtest regressed as an API key is now required
Hint added for bionic. No hint needed for xenial; per http://autopkgtest.ubuntu.com/packages/libg/libgeo-coder-googlev3-perl the xenial version of the package has no autopkgtest. We should not do an SRU of this solely for the autopkgtest update. ** Changed in: libgeo-coder-googlev3-perl (Ubuntu Bionic) Status: New => Fix Released ** Changed in: libgeo-coder-googlev3-perl (Ubuntu Xenial) 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/1831443 Title: [hint] [sru] autopkgtest regressed as an API key is now required Status in libgeo-coder-googlev3-perl package in Ubuntu: Fix Released Status in libgeo-coder-googlev3-perl source package in Xenial: Invalid Status in libgeo-coder-googlev3-perl source package in Bionic: Fix Released Bug description: libgeo-coder-googlev3-perl uses a remote Google Maps service, which has started to require unique API keys. As there is no API key for the autopkgtests, they have started to fail. Autopkgtests for 0.16-1 will thus now always fail and should be hinted as expected failure. In 0.17-1 networked tests have been disabled during autopkgtests, and I'm proposing to SRU such a fix to bionic too. [Impact] * Unbreak autopkgtests by disabling networked tests due to remote service requiring authentication API tokens. [Test Case] * autopkgtests should pass [Regression Potential] * as networked tests are no longer performed, further regressions in utilising the remote service will not be caught. [Hints] bionic: force-badtest libgeo-coder-googlev3-perl/0.16-1 xenial: force-badtest libgeo-coder-googlev3-perl/0.14-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgeo-coder-googlev3-perl/+bug/1831443/+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 1773529] Re: Missing DKIM fixes in Xenial (Exim 4.86)
** Also affects: exim4 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: exim4 (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: exim4 (Ubuntu Xenial) Status: New => Triaged ** Changed in: exim4 (Ubuntu) Status: Triaged => Fix Released ** Summary changed: - Missing DKIM fixes in Xenial (Exim 4.86) + [SRU] Missing DKIM fixes in Xenial (Exim 4.86) -- 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/1773529 Title: [SRU] Missing DKIM fixes in Xenial (Exim 4.86) Status in exim4 package in Ubuntu: Fix Released Status in exim4 source package in Xenial: Triaged Bug description: Exim is missing the following DKIM fixes, and probably many more: https://bugs.exim.org/show_bug.cgi?id=2278 https://bugs.exim.org/show_bug.cgi?id=1721 This package is not being maintained and only receives security fixes. It needs to either track the current Exim release or get bug fixes applied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1773529/+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 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/ZtkqccNY/1077-pc- kernel-440-150176-223 ** Changed in: kernel-sru-workflow/snap-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/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New 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 backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Friday, 31. May 2019 20:32 UTC reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present snap-certification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+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 1766740] Re: apport autopkgtest regression due to kernel packaging changes
** Also affects: apport (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/1766740 Title: apport autopkgtest regression due to kernel packaging changes Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Bionic: Fix Released Bug description: [SRU Justification] In bionic, linux-image-$kvers-$flavor is now built from the linux-signed source package on amd64, not from the linux source package. This now causes a test to fail in the apport test suite: [...] == FAIL: test_run_crash_kernel (__main__.T) run_crash() for a kernel error -- Traceback (most recent call last): File "./test_ui.py", line 1305, in test_run_crash_kernel self.assertEqual(self.ui.opened_url, 'http://linux.bugs.example.com/%i' % se lf.ui.crashdb.latest_id()) AssertionError: 'http://linux-signed.bugs.example.com/5' != 'http://linux.bugs.e xample.com/5' - http://linux-signed.bugs.example.com/5 ? --- + http://linux.bugs.example.com/5 -- Ran 70 tests in 79.815s FAILED (failures=1) [...] (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- bionic/bionic/amd64/a/apport/20180424_19_45dc8@/log.gz) This test needs to be fixed to know about the packaging change. Note that this packaging change is expected to soon be SRUed back to all Ubuntu releases, so apport's testsuite change should also be SRUed. [Test case] This passes if the autopkgtests pass. [Regression potential] The test could be changed to pass while leaving underlying issues in the code. This has probably not happened here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1766740/+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 1829208] Re: linux-oracle: 4.15.0-1014.16~16.04.1 -proposed tracker
4.15.0-1014.16~16.04.1 - oracle Regression test CMPL, RTB. Issue to note in oracle (amd64): ubuntu_kernel_selftests - global.get_metadata in seccomp (bug 1811057) net test failed to build (bug 1813883) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) access (bug 1831451) memory (bug 1831449) port80 (bug 1748105) pcid (bug 1827979) vmx (bug 1821394) vmx_hlt_with_rvi_test (bug 1822308) vmx_apicv_test (bug 1827866) vmx_apic_passthrough_thread (bug 1822309) debug (bug 1821906) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) statx05 (bug 1798524) sync_file_range02 (bug 1819116) ubuntu_lxc - Failed to fetch GPG key on VM.Standard2.24, passed on the rest Skipped / blacklisted: * libhugetlbfs * ubuntu_ltp * ubuntu_seccomp ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1829208 Title: linux-oracle: 4.15.0-1014.16~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: New 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: 1829210 phase: Ready for Testing phase-changed: Tuesday, 28. May 2019 23:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829208/+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 1830268] Re: Use changed nested VMX attribute as trigger to refresh libvirt capability cache
Hmm, we just don't need the xenial portion.
As already mentioned at the backport the code was way different then.
I can start a VMX defined guest on Xenial:
core2duo
Intel
And it becomes -cpu core2duo,+vmx for qemu commandline.
So Xenial is actually "invalid" as the issue described here doesn't apply there.
** Changed in: libvirt (Ubuntu Xenial)
Status: Triaged => 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/1830268
Title:
Use changed nested VMX attribute as trigger to refresh libvirt
capability cache
Status in libvirt package in Ubuntu:
Fix Released
Status in libvirt source package in Xenial:
Invalid
Status in libvirt source package in Bionic:
In Progress
Status in libvirt source package in Cosmic:
In Progress
Bug description:
[impact]
libvirt caches the 'nested vmx' capability of the host and does not
update that even if the host's capability to handle nested vmx
changes. Having this domcapability missing means no guests are able
to start any nested, kvm-accelerated, guests. Additionally, since
openstack live migration requires matching cpu features, this makes
migrating guests that do have vmx enabled impossible to hosts where
libvirt thinks nested vmx is disabled.
Once the kernel module (kvm_intel) is reloaded with 'nested' enabled,
libvirt does not update its domcapabilities cache, even over a
libvirtd restart, or even over an entire system reboot. Only certain
conditions cause libvirt to update its capabilities cache (possibly
libvirt upgrade, or qemu upgrade, or kernel upgrade...I haven't
verified any of those yet)
libvirt creates caches for its domcapabilities at
/var/cache/libvirt/qemu/capabilities/.
removing the cache xml files there and restarting libvirtd will cause the
caches to be recreated with the correct current values.
The fix backports the upstream fix:
https://libvirt.org/git/?p=libvirt.git;a=commit;h=b183a753
Which makes it always check the current vs the last stored attribute.
[test case]
check the kvm_intel module nested parameter:
$ cat /sys/module/kvm_intel/parameters/nested
Y
it can be Y or N. make sure libvirt agrees with the current setting:
$ virsh domcapabilities | grep vmx
if 'nested' is Y, domcapabilities should include a vmx feature line;
if 'nested' is N, it should have no output (i.e. vmx not supported in
guests).
Then, change the kernel nested setting, and re-check domcapabilities.
Restarting libvirtd doesn't update the cache, and even rebooting the
entire system doesn't update the cache.
$ virsh domcapabilities | grep vmx
$ cat /sys/module/kvm_intel/parameters/nested
N
$ sudo rmmod kvm_intel
$ sudo modprobe kvm_intel nested=1
$ cat /sys/module/kvm_intel/parameters/nested
Y
$ virsh domcapabilities | grep vmx
$ sudo systemctl restart libvirtd
$ virsh domcapabilities | grep vmx
$
Not only should it work, but further configurung libvirt debug [1] the fix
should leave a message like this when triggering:
VIR_DEBUG("Outdated capabilities for '%s': kvm kernel nested "
"value changed from %d",)
Test #2:
- restart libvirtd
- call `virsh domcapabilities`
- repeat the above
- this should later on use the cache (faster)
- If it always regenerates the cache (see spawned qemu's and new file
dates) the detection is wrong
Test #3:
- some arches (e.g. s390x) don't have this attribute, check on one of those
how their behavior changes.
[regression potential]
This will make libvirt refresh the capability cache more often. This is a
quite expensive tasks (depending on the number of qemu's installed which can be
anything from none to all arch emulators and the kvm based ones ~10. Those will
be forked and probed again. The new code now adds a rather safe detection as
the nested attribute would usually only change on a reboot or a module reload.
So it should be rather safe. The one real regression would be if the detection
would be wrong and always trigger.
I added Test #2 above to check for that.
[other info]
related RH bugs, though no changes appear to have resulted from either:
https://bugzilla.redhat.com/show_bug.cgi?id=1474874
https://bugzilla.redhat.com/show_bug.cgi?id=1650950
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1830268/+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 1831443] [NEW] [hint] [sru] autopkgtest regressed as an API key is now required
Public bug reported: libgeo-coder-googlev3-perl uses a remote Google Maps service, which has started to require unique API keys. As there is no API key for the autopkgtests, they have started to fail. Autopkgtests for 0.16-1 will thus now always fail and should be hinted as expected failure. In 0.17-1 networked tests have been disabled during autopkgtests, and I'm proposing to SRU such a fix to bionic too. [Impact] * Unbreak autopkgtests by disabling networked tests due to remote service requiring authentication API tokens. [Test Case] * autopkgtests should pass [Regression Potential] * as networked tests are no longer performed, further regressions in utilising the remote service will not be caught. [Hints] bionic: force-badtest libgeo-coder-googlev3-perl/0.16-1 xenial: force-badtest libgeo-coder-googlev3-perl/0.14-1 ** Affects: libgeo-coder-googlev3-perl (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: libgeo-coder-googlev3-perl (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: libgeo-coder-googlev3-perl (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libgeo-coder-googlev3-perl (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libgeo-coder-googlev3-perl (Ubuntu) Status: New => Fix Released ** Also affects: libgeo-coder-googlev3-perl (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/1831443 Title: [hint] [sru] autopkgtest regressed as an API key is now required Status in libgeo-coder-googlev3-perl package in Ubuntu: Fix Released Status in libgeo-coder-googlev3-perl source package in Xenial: New Status in libgeo-coder-googlev3-perl source package in Bionic: New Bug description: libgeo-coder-googlev3-perl uses a remote Google Maps service, which has started to require unique API keys. As there is no API key for the autopkgtests, they have started to fail. Autopkgtests for 0.16-1 will thus now always fail and should be hinted as expected failure. In 0.17-1 networked tests have been disabled during autopkgtests, and I'm proposing to SRU such a fix to bionic too. [Impact] * Unbreak autopkgtests by disabling networked tests due to remote service requiring authentication API tokens. [Test Case] * autopkgtests should pass [Regression Potential] * as networked tests are no longer performed, further regressions in utilising the remote service will not be caught. [Hints] bionic: force-badtest libgeo-coder-googlev3-perl/0.16-1 xenial: force-badtest libgeo-coder-googlev3-perl/0.14-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgeo-coder-googlev3-perl/+bug/1831443/+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 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
4.4.0-150.176 - generic Regression test CMPL, RTB. 53 / 54 tests were run, missing: xfstests Issue to note in amd64: ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) fanotify12 timeouted (bug 1828813) sync_file_range02 (bug 1819116) ubuntu_qrt_apparmor - apparmor issue (bug 1830802) ubuntu_ramfs_stress - proxy issue for Intel Cloud (bug 1828786) 48 / 49 tests were run, missing: xfstests Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427) ubuntu_kvm_unit_tests - pmu on ms10-34-mcdivittB0-kernel (bug 1751000) gicv2-mmio on X-ARM64 (bug 1828165) gicv2 related test failed on ThunderX (bug 1828153) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) fanotify12 timeouted (bug 1828813) sync_file_range02 (bug 1819116) ubuntu_qrt_apparmor - apparmor issue (bug 1830802) Issue to note in i386: ubuntu_kvm_smoke_test - timed out waiting for dnsmasq lease (bug 1802056) ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) fanotify12 timeouted (bug 1828813) sync_file_range02 (bug 1819116) ubuntu_qrt_apparmor - apparmor issue (bug 1830802) xfstests - xfs generic/308 timed out (bug 1738152) Issue to note in ppc64le (P8): ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 320M on Xenial P8 (bug 1813863) ubuntu_ltp_syscalls - fallocate05, fsetxattr01, fgetxattr01, fsync01, preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01 (bug 1785198) inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) fanotify12 timeouted (bug 1828813) ubuntu_qrt_apparmor - apparmor issue (bug 1830802) xfstests - btrfs generic/176 timed out Issue to note in s390x (KVM): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - All tests failed on s390x KVM (bug 1822542) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) fanotify12 timeouted (bug 1828813) sync_file_range02 (bug 1819116) ubuntu_qrt_apparmor - apparmor issue (bug 1830802) ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option should be enable on X s390x (bug 1813721) 47 / 48 tests were run, missing: ubuntu_boot Issue to note in s390x (Ubuntu on LPAR): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) fanotify12 timeouted (bug 1828813) sync_file_range02 (bug 1819116) ubuntu_qrt_apparmor - apparmor issue (bug 1830802) ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option should be enable on X s390x (bug 1813721) 47 / 48 tests were run, missing: ubuntu_boot Issue to note in s390x (zVM): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - skey failed on zVM (bug 1778705) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) fanotify12 timeouted (bug 1828813) sync_file_range02 (bug 1819116) ubuntu_qrt_apparmor - apparmor issue (bug 1830802) ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option should be enable on X s390x (bug 1813721) Note: The security team decided that the apparmor issue
[Group.of.nepali.translators] [Bug 1824212] Re: Update gce-compute-image-packages to 20190315
*** This bug is a duplicate of bug 1831436 *** https://bugs.launchpad.net/bugs/1831436 ** This bug is no longer a duplicate of bug 1830194 Update gce-compute-image-packages to 20190521 ** This bug has been marked a duplicate of bug 1831436 Update gce-compute-image-packages to 20190522 -- 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/1824212 Title: Update gce-compute-image-packages to 20190315 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Committed Status in gce-compute-image-packages source package in Xenial: Fix Committed Status in gce-compute-image-packages source package in Bionic: Fix Committed Status in gce-compute-image-packages source package in Cosmic: Fix Committed Status in gce-compute-image-packages source package in Disco: Fix Committed Bug description: [Impact] compute-image-packages is provided by Google for installation within guests that run on Google Compute Engine. It is a collection of tools and daemons, packaged as gce-compute-image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating gce-compute-image-packages to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. With this release we also add a new binary package to the suite - google-compute-engine-oslogin which is for a future feature of using OS Login on GCE VM instances. [Test Case] When a new version of gce-compute-image-packages is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the CPC team will write new automated tests to cover new testable functionality (if any) in the new package * the automated testing that the CPC team normally runs against GCE images before they are published will be run against the -proposed image * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1824212/+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 1308105] Re: [SRU] Xfce resets TV mode to NULL when power cycled
This bug was fixed in the package xfce4-settings - 4.12.0-2ubuntu1.16.04.1 --- xfce4-settings (4.12.0-2ubuntu1.16.04.1) xenial; urgency=medium * debian/patches/lp1308105.patch: - Fix Xfce resetting TV mode to NULL when power cycled (LP: #1308105) -- Sean Davis Tue, 26 Mar 2019 21:52:13 -0400 ** Changed in: xfce4-settings (Ubuntu Xenial) 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/1308105 Title: [SRU] Xfce resets TV mode to NULL when power cycled Status in Xfce4 Settings: Fix Released Status in xfce4-settings package in Ubuntu: Fix Released Status in xfce4-settings source package in Xenial: Fix Released Status in xfce4-settings source package in Bionic: Fix Released Bug description: [Impact] * When a TV is power-cycled, it is no longer detected as an available display. * The root issue is in xfce4-settings: xfsettingsd. * The related patch correctly handles the NULL mode the TV enters when powered off. [Test Case] * Connect a TV to a computer running xfce4-settings 4.12.0, this can be in a single configuration or dual-monitor. * Power the TV off. * Power the TV on. * Expected: TV powers on and remains connected as an available display. * Actual: TV powers on and is not connected or detected. [Regression Potential] * Regression potential is minimal: The associated patch targets this very specific scenario and behavior, and does not interact with the rest of the codebase. [Original Report] I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-settings/+bug/1308105/+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 1807439] Re: openvpn crashes when run with fips openssl
This bug was fixed in the package openvpn - 2.4.4-2ubuntu1.2 --- openvpn (2.4.4-2ubuntu1.2) bionic; urgency=medium * d/p/openvpn-fips-2.4.patch: Allow MD5 in FIPS mode (openssl) for PRF. (LP: #1807439) -- Joy Latten Wed, 09 Jan 2019 15:50:03 -0600 ** Changed in: openvpn (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: openvpn (Ubuntu Xenial) 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/1807439 Title: openvpn crashes when run with fips openssl Status in OpenVPN: Unknown Status in openvpn package in Ubuntu: Fix Released Status in openvpn source package in Xenial: Fix Released Status in openvpn source package in Bionic: Fix Released Status in openvpn source package in Cosmic: Fix Released Status in openvpn source package in Disco: Fix Released Bug description: [IMPACT] openvpn segfaults when using fips-mode openssl because of MD5. xenial has version 2.3.x and subsequent releases have 2.4.x. MD5 is used in 2 places in 2.3.x and one place in 2.4.x. First place: openvpn when estabishing a tls connection will segfault when used with Ubuntu's FIPS 140-2 libcrypto.so (openssl). openvpn tls connection does TLS PRF(pseudorandom function) to produce securely generated pseudo random output that is used to generate keys. MD5 is used as the hash in this computation. FIPS 140-2 does not permit MD5 use except when used for pseudorandom function (PRF). When openvpn requests MD5 operation to FIPS-mode libcrypto.so, since it is not allowed in general, FIPS-mode libcrypto.so goes into an error state. The context flag value, EVP_MD_CTX_FLAG_NON_FIPS_ALLOW, is defined in both FIPS and non-FIPS libcrypto.so. However, the MD5 check for it is only in FIPS-mode libcrypto.so to permit MD5. In non-FIPS libcrypto.so this check does not exist since it always permits MD5. openvpn should use this flag when it makes its MD5 request. Second place (only in 2.3.x): **NOTE: The openvpn 2.3 version in xenial has the above issue and an additional one. It also use MD5 internally for configuration status verification. It is not communicated externally. However, this particular use of MD5 is not allowed by FIPS and thus when openvpn tries to use FIPS-mode libcrypto.so to compute MD5, it results in openvpn segfaulting. This 2nd issue was fixed by upstream openvpn community in subsequent versions(2.4) to not use MD5 and use SHA(256) instead and thus why bionic, cosmic, and disco do not require any change for this 2nd issue. [TEST] Test data including commands and parameters are included below. Testing comprised establishing a tls connection between an openvpn client and server. Once the connection was successfully established, a ping thru the established vpn tunnel was done from the client for assurance. Interoperability testing was done to ensure no regression. Test data reflects testing was done between openvpn server and client with and without the patch and between various releases (xenial, bionic, and disco). Test was also done with FIPS-enabled libcrypto.so to ensure everything worked in FIPS mode. [REGRESSION] The context flag value, EVP_MD_CTX_FLAG_NON_FIPS_ALLOW, is defined in both FIPS-mode openssl and non-FIPS openssl. However, the MD5-permit check against this flag-value does not occur in non-FIPS libcrypto.so, so there should be no change in behaviour. non-FIPS libcrypto.so should continue to service all MD5 requests. xenial with version 2.3.x, has additional change of using SHA256 instead of MD5 for configuration status verification. This is an internal hash that is not communicated externally. Thus it should not regress interoperability or ability to establish connections. To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/1807439/+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 1762492] Re: pgsql resource agent should check for stats_temp_directory
Setting dev version to fix released per last comment. ** Changed in: resource-agents (Ubuntu) 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/1762492 Title: pgsql resource agent should check for stats_temp_directory Status in resource-agents package in Ubuntu: Fix Released Status in resource-agents source package in Xenial: New Status in resource-agents source package in Artful: Invalid Status in resource-agents source package in Bionic: New Bug description: [Impact] * Default postgres installation in Ubuntu (and Debian) configures stats_temp_directory inside /var/run/postgresql. However, this directory is not created after reboot. Usually this directory is created by pg_ctlcluster, which is a pg_ctl wraper called by systemd/upstart. However postgres resource agent is not using pg_ctlcluster when starting postgres, it calls pg_ctl directly, which won't recreate missing directories. This will prevent resource agent to properly start postgres. * This bug is already fixed in upstream: https://github.com/ClusterLabs/resource-agents/pull/1102/ * This SRU cherrypicks the commit from the upstream - the commit checks if configured stats directory exists, and if it does not it tries to create it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1762492/+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 1749283] Re: configured stats_temp_directory does not get created after reboot
Thanks for the clarification Mario! Now things fit together. I'll mark the resource agent tasks invalid here per these comments to make sure no one is confused again. TL;DR: - not fixed in postgresql-common - only fixed in resouce-agent for Xenial/Bionic via SRU in bug 1762492 ** Changed in: resource-agents (Ubuntu Xenial) Status: Confirmed => Invalid ** Changed in: resource-agents (Ubuntu Bionic) 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/1749283 Title: configured stats_temp_directory does not get created after reboot Status in postgresql-common package in Ubuntu: Won't Fix Status in resource-agents package in Ubuntu: Fix Released Status in postgresql-common source package in Xenial: Won't Fix Status in resource-agents source package in Xenial: Invalid Status in postgresql-common source package in Bionic: Won't Fix Status in resource-agents source package in Bionic: Invalid Status in postgresql-common package in Debian: Fix Released Bug description: Default postgres installation in Ubuntu (and Debian) configures stats_temp_directory inside /var/run/postgresql: $ grep stats_temp /etc/postgresql/10/main/postgresql.conf stats_temp_directory = '/var/run/postgresql/10-main.pg_stat_tmp' However, this directory is not created after reboot. In most cases this is not a problem as systemd starts postgres via pg_ctlcluster, a "multiversion/cluster aware pg_ctl wrapper", and pg_ctlcluster will create missing directories before starting postgres. But in cases where systemd is not starting postgres this is a problem. Specifically, when postgres is controlled by pacemaker (using postgres resource agent for pacemaker) it is started using pg_ctl wrapper. pg_ctl won't create missing directories and therefore postgres fails to start. The simplest solution for this issue is to have systemd recreate missing directories via /usr/lib/tmpfiles.d/postgresql.conf file. Currently only /var/run/postgresql and /var/log/postgresql are created using systemd-tmpfiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1749283/+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 1807439] Re: openvpn crashes when run with fips openssl
This bug was fixed in the package openvpn - 2.4.6-1ubuntu2.1 --- openvpn (2.4.6-1ubuntu2.1) cosmic; urgency=medium * d/p/openvpn-fips-2.4.patch: Allow MD5 in FIPS mode (openssl) for PRF. (LP: #1807439) -- Joy Latten Thu, 10 Jan 2019 13:48:21 -0600 ** Changed in: openvpn (Ubuntu Cosmic) 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/1807439 Title: openvpn crashes when run with fips openssl Status in OpenVPN: Unknown Status in openvpn package in Ubuntu: Fix Released Status in openvpn source package in Xenial: Fix Committed Status in openvpn source package in Bionic: Fix Committed Status in openvpn source package in Cosmic: Fix Released Status in openvpn source package in Disco: Fix Released Bug description: [IMPACT] openvpn segfaults when using fips-mode openssl because of MD5. xenial has version 2.3.x and subsequent releases have 2.4.x. MD5 is used in 2 places in 2.3.x and one place in 2.4.x. First place: openvpn when estabishing a tls connection will segfault when used with Ubuntu's FIPS 140-2 libcrypto.so (openssl). openvpn tls connection does TLS PRF(pseudorandom function) to produce securely generated pseudo random output that is used to generate keys. MD5 is used as the hash in this computation. FIPS 140-2 does not permit MD5 use except when used for pseudorandom function (PRF). When openvpn requests MD5 operation to FIPS-mode libcrypto.so, since it is not allowed in general, FIPS-mode libcrypto.so goes into an error state. The context flag value, EVP_MD_CTX_FLAG_NON_FIPS_ALLOW, is defined in both FIPS and non-FIPS libcrypto.so. However, the MD5 check for it is only in FIPS-mode libcrypto.so to permit MD5. In non-FIPS libcrypto.so this check does not exist since it always permits MD5. openvpn should use this flag when it makes its MD5 request. Second place (only in 2.3.x): **NOTE: The openvpn 2.3 version in xenial has the above issue and an additional one. It also use MD5 internally for configuration status verification. It is not communicated externally. However, this particular use of MD5 is not allowed by FIPS and thus when openvpn tries to use FIPS-mode libcrypto.so to compute MD5, it results in openvpn segfaulting. This 2nd issue was fixed by upstream openvpn community in subsequent versions(2.4) to not use MD5 and use SHA(256) instead and thus why bionic, cosmic, and disco do not require any change for this 2nd issue. [TEST] Test data including commands and parameters are included below. Testing comprised establishing a tls connection between an openvpn client and server. Once the connection was successfully established, a ping thru the established vpn tunnel was done from the client for assurance. Interoperability testing was done to ensure no regression. Test data reflects testing was done between openvpn server and client with and without the patch and between various releases (xenial, bionic, and disco). Test was also done with FIPS-enabled libcrypto.so to ensure everything worked in FIPS mode. [REGRESSION] The context flag value, EVP_MD_CTX_FLAG_NON_FIPS_ALLOW, is defined in both FIPS-mode openssl and non-FIPS openssl. However, the MD5-permit check against this flag-value does not occur in non-FIPS libcrypto.so, so there should be no change in behaviour. non-FIPS libcrypto.so should continue to service all MD5 requests. xenial with version 2.3.x, has additional change of using SHA256 instead of MD5 for configuration status verification. This is an internal hash that is not communicated externally. Thus it should not regress interoperability or ability to establish connections. To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/1807439/+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 1829195] Re: linux-kvm: 4.4.0-1047.53 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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 -- boot-testing-requested: true kernel-stable-master-bug: 1830941 - phase: Ready for Testing - phase-changed: Friday, 31. May 2019 12:39 UTC + phase: Holding before Release + phase-changed: Monday, 03. June 2019 08:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for release -- 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/1829195 Title: linux-kvm: 4.4.0-1047.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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 promote-to-proposed series: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: New 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: 1830941 phase: Holding before Release phase-changed: Monday, 03. June 2019 08:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829195/+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 1829193] Re: linux-aws: 4.4.0-1084.94 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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 -- boot-testing-requested: true kernel-stable-master-bug: 1830941 phase: Ready for Testing phase-changed: Wednesday, 29. May 2019 00:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - verification-testing: Ongoing -- testing 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/1829193 Title: linux-aws: 4.4.0-1084.94 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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 promote-to-proposed series: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New 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: 1830941 phase: Ready for Testing phase-changed: Wednesday, 29. May 2019 00:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829193/+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 1829198] Re: linux-raspi2: 4.4.0-1110.118 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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 -- boot-testing-requested: true kernel-stable-master-bug: 1830941 - phase: Ready for Testing - phase-changed: Wednesday, 29. May 2019 07:36 UTC + phase: Holding before Release + phase-changed: Monday, 03. June 2019 08:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - snap-release-to-candidate: 'Pending -- snap pi2-kernel not in expected channel(s): - arch=armhf:channel=latest/candidate:rev=89' - verification-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for release -- 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/1829198 Title: linux-raspi2: 4.4.0-1110.118 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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: New 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: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: New 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: 1830941 phase: Holding before Release phase-changed: Monday, 03. June 2019 08:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829198/+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 1829203] Re: linux-fips: 4.4.0-1011.14 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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 -- boot-testing-requested: true kernel-stable-master-bug: 1830941 phase: Ready for Testing phase-changed: Tuesday, 21. May 2019 22:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - verification-testing: Ongoing -- testing 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/1829203 Title: linux-fips: 4.4.0-1011.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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-signing-to-proposed 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: Fix Released 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: New 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: 1830941 phase: Ready for Testing phase-changed: Tuesday, 21. May 2019 22:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829203/+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 1829201] Re: linux-snapdragon: 4.4.0-1114.119 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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 -- boot-testing-requested: true kernel-stable-master-bug: 1830941 - phase: Ready for Testing - phase-changed: Wednesday, 29. May 2019 14:06 UTC + phase: Holding before Release + phase-changed: Monday, 03. June 2019 08:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for release -- 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/1829201 Title: linux-snapdragon: 4.4.0-1114.119 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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: New 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: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: New 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: 1830941 phase: Holding before Release phase-changed: Monday, 03. June 2019 08:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829201/+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 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
Verification tests completed successfully. ** Changed in: kernel-sru-workflow/verification-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/1830941 Title: linux: 4.4.0-150.176 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New 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 backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Friday, 31. May 2019 20:32 UTC reason: regression-testing: Ongoing -- testing in progress snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+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
