[Group.of.nepali.translators] [Bug 1846130] Re: xenial/linux-hwe: 4.15.0-66.75~16.04.1 -proposed tracker

2019-10-16 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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: 1846131
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Testing
  phase-changed: Thursday, 03. October 2019 22:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-deeplens: bug 1846128
xenial/linux-hwe-edge: bug 1846127
  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/1846130

Title:
  xenial/linux-hwe: 4.15.0-66.75~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:
  Confirmed
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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846131
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Testing
  phase-changed: Thursday, 03. October 2019 22:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-deeplens: bug 1846128
xenial/linux-hwe-edge: bug 1846127
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846130/+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 1847139] Re: [linux-azure] Request of mainline commit f73f8a504e27 in azure 16.04 and 18.04

2019-10-16 Thread Marcelo Cerri
** Also affects: linux-azure (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-azure (Ubuntu Disco)
   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/1847139

Title:
  [linux-azure] Request of mainline commit f73f8a504e27 in azure 16.04
  and 18.04

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-azure source package in Disco:
  New

Bug description:
  Microsoft would like to request the following mainline commit be added to 
linux-azure 16.04 and 18.04:
  f73f8a504e27 PCI: hv: Use bytes 4 and 5 from instance ID as the PCI domain 
numbers

  This commit was added to mainline in v5.4-rc1~63^2~8^2

  This was recommended by Azure host team, the bytes 4, 5 have more
  uniqueness(info entropy) than bytes 8, 9, so we should use them as the
  PCI domain numbers.

  This patch should be added to both 16.04 and 18.04 images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1847139/+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

2019-10-16 Thread Rafael David Tinoco
** Changed in: simplestreams (Ubuntu Xenial)
   Status: In Progress => Won't Fix

** Changed in: simplestreams (Ubuntu Bionic)
   Status: Fix Released => In Progress

** Changed in: simplestreams (Ubuntu Xenial)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: simplestreams (Ubuntu Bionic)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

-- 
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/1583276

Title:
  glance restarted during image upload, image stuck in "saving" state

Status in Glance - Simplestreams Sync Charm:
  Invalid
Status in Landscape Server:
  Fix Committed
Status in Landscape Server 16.06 series:
  Fix Released
Status in simplestreams:
  Fix Released
Status in simplestreams package in Ubuntu:
  Fix Released
Status in simplestreams source package in Xenial:
  Won't Fix
Status in simplestreams source package in Bionic:
  In Progress
Status in simplestreams source package in Disco:
  Fix Released

Bug description:
  [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)
  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

  glance/1 had its last restart later:
  2016-05-18 13:32:01 INFO ceph-relation-changed glance-api start/running, 
process 31045

  glance/2 at that time too:
  2016-05-18 13:32:00 INFO ceph-relation-changed glance-api start/running, 
process 30584

  In gs3, a few log entries later, we can see that 14.04 is in state "saving" 
in glance:
  (...)
  {"images": [{"status": "saving", "deleted_at": null, "name": 

[Group.of.nepali.translators] [Bug 1611987] Re: [SRU] glance-simplestreams-sync charm doesn't support keystone v3

2019-10-16 Thread Rafael David Tinoco
** Changed in: simplestreams (Ubuntu Xenial)
   Status: In Progress => Won't Fix

** Changed in: simplestreams (Ubuntu Xenial)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: simplestreams (Ubuntu Bionic)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

-- 
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/1611987

Title:
  [SRU] glance-simplestreams-sync charm doesn't support keystone v3

Status in OpenStack glance-simplestreams-sync charm:
  Fix Released
Status in Glance - Simplestreams Sync Charm:
  Invalid
Status in simplestreams:
  Fix Released
Status in simplestreams package in Ubuntu:
  Fix Released
Status in simplestreams source package in Xenial:
  Won't Fix
Status in simplestreams source package in Artful:
  Won't Fix
Status in simplestreams source package in Bionic:
  Fix Released
Status in glance-simplestreams-sync package in Juju Charms Collection:
  Invalid

Bug description:
  [Impact]

  simplestreams can't sync images when keystone is configured to use v3,
  keystone v2 is deprecated since mitaka[0] (the version shipped with
  xenial)

  The OpenStack Keystone charm supports v3 only since Queens and
  later[1]

  [Test Case]

  * deploy a openstack environment with keystone v3 enabled
- get a copy of the bundle available at 
http://paste.ubuntu.com/p/hkhsHKqt4h/ , this bundle deploys a minimal version 
of xenial-mitaka.

  Expected result:

  - "glance image-list" lists trusty and xenial images
  - the file glance-simplestreams-sync/0:/var/log/glance-simplestreams-sync.log 
contains details of the images pulled from cloud-images.u.c (example: 
https://pastebin.ubuntu.com/p/RWG8QrkVDz/ )

  Actual result:

  - "glance image-list" is empty
  - the file glance-simplestreams-sync/0:/var/log/glance-simplestreams-sync.log 
contains the following stacktrace
  INFO * 04-09 22:04:06 [PID:14571] * root * Calling DryRun mirror to get item 
list
  ERROR * 04-09 22:04:06 [PID:14571] * root * Exception during syncing:
  Traceback (most recent call last):
File "/usr/share/glance-simplestreams-sync/glance-simplestreams-sync.py", 
line 471, in main
  do_sync(charm_conf, status_exchange)
File "/usr/share/glance-simplestreams-sync/glance-simplestreams-sync.py", 
line 232, in do_sync
  objectstore=store)
File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/glance.py", 
line 374, in __init__
  super(ItemInfoDryRunMirror, self).__init__(config, objectstore)
File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/glance.py", 
line 126, in __init__
  self.keystone_creds = openstack.load_keystone_creds()
File "/usr/lib/python2.7/dist-packages/simplestreams/openstack.py", line 
61, in load_keystone_creds
  raise ValueError("(tenant_id or tenant_name)")
  ValueError: (tenant_id or tenant_name)

  [Regression Potential]

  * A possible regression will manifest itself figuring out if v2 or v3
  should be used, after the connection is made there are no further
  changes introduced by this SRU

  [Other Info]

  I was deploying a Mitaka Trusty 16.04 charm based Openstack cloud
  (using the cloud archives), including glance-simplestreams-sync, using
  keystone v3.

  Once I had everything deployed, the glance-simplestreams-sync service
  couldn't authenticate because it's using keystone v2, not v3, as you
  can see from the following:

  INFO  * 08-10 23:16:01 [PID:33554] * root * glance-simplestreams-sync 
started.
  DEBUG * 08-10 23:16:01 [PID:33554] * keystoneclient.session * REQ: curl 
-i -X POST http://x.y.z.240:5000/v2.0/tokens -H "Content-Type: 
application/json" -H "User-Agent: python-keystoneclient" -d '{"auth": 
{"passwordCredentials": {"username": "image-stream", "password": 
"thisisnotapassword"}, "tenantId": "blahblahtenantidblahblah"}}'
  INFO  * 08-10 23:16:01 [PID:33554] * urllib3.connectionpool * Starting 
new HTTP connection (1): x.y.z.240
  DEBUG * 08-10 23:16:01 [PID:33554] * urllib3.connectionpool * Setting 
read timeout to None
  DEBUG * 08-10 23:16:01 [PID:33554] * urllib3.connectionpool * "POST 
/v2.0/tokens HTTP/1.1" 401 114
  DEBUG * 08-10 23:16:01 [PID:33554] * keystoneclient.session * RESP: [401] 
CaseInsensitiveDict({'content-length': '114', 'vary': 'X-Auth-Token', 'server': 
'Apache/2.4.7 (Ubuntu)', 'date': 'Wed, 10 Aug 2016 23:16:01 GMT', 
'www-authenticate': 'Keystone uri="http://x.y.z.240:5000;', 
'x-openstack-request-id': 'req-f8aaf12d-01ea-46be-869a-6948ab38361b', 
'content-type': 'application/json', 'x-distribution': 'Ubuntu'})
  RESP BODY: {"error": {"message": "The request you have made requires 
authentication.", "code": 401, "title": "Unauthorized"}}

  DEBUG * 08-10 23:16:01 [PID:33554] * keystoneclient.session * Request 
returned failure status: 401
  DEBUG * 08-10 23:16:01 [PID:33554] * 

[Group.of.nepali.translators] [Bug 1584938] Re: Incomplete simplestreams metadata and failed juju bootstrap

2019-10-16 Thread Rafael David Tinoco
** Changed in: simplestreams (Ubuntu Xenial)
   Status: In Progress => Won't Fix

** Changed in: simplestreams (Ubuntu Bionic)
   Status: Fix Released => In Progress

** Changed in: simplestreams (Ubuntu Xenial)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: simplestreams (Ubuntu Bionic)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

-- 
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:
  Won't Fix
Status in simplestreams source package in Bionic:
  In Progress
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 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.

  [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/

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance-simplestreams-sync-charm/+bug/1584938/+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 1578622] Re: [SRU] glance do not require hypervisor_mapping

2019-10-16 Thread Rafael David Tinoco
** Changed in: simplestreams (Ubuntu Xenial)
   Status: In Progress => Won't Fix

** Also affects: simplestreams (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: simplestreams (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: simplestreams (Ubuntu Bionic)
   Status: Triaged => In Progress

** Changed in: simplestreams (Ubuntu Xenial)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: simplestreams (Ubuntu Bionic)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

-- 
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/1578622

Title:
  [SRU] glance do not require hypervisor_mapping

Status in simplestreams:
  Fix Released
Status in simplestreams package in Ubuntu:
  Fix Released
Status in simplestreams source package in Xenial:
  Won't Fix
Status in simplestreams source package in Yakkety:
  Fix Released
Status in simplestreams source package in Bionic:
  In Progress

Bug description:
  [Impact]
  currently the glance mirror requires hypervisor_mapping config in the api.
  Better to not required that as a library consumer would not necessarily 
provide it.

  [Test Case]

  * deploy a openstack environment with keystone v2 enabled
    - get a copy of the bundle available at 
http://paste.ubuntu.com/p/qxwSDtDZ52/ , this bundle deploys a minimal version 
of xenial-mitaka.

  Expected Result:
  - "glance image-list" lists trusty and xenial images
  - the file glance-simplestreams-sync/0:/var/log/glance-simplestreams-sync.log 
contains details of the images pulled from cloud-images.u.c (example: 
https://pastebin.ubuntu.com/p/RWG8QrkVDz/ )

  Actual result:

  - "glance image-list" is empty
  - glance-simplestreams-sync/0 is in blocked state and message "Image sync 
failed, retrying soon."

  In /var/log/glance-simplestreams-sync.log:
  ERROR * 02-14 15:46:07 [PID:1898] * root * Exception during syncing:
  Traceback (most recent call last):
File "/usr/share/glance-simplestreams-sync/glance-simplestreams-sync.py", 
line 462, in main
  do_sync(charm_conf, status_exchange)
File "/usr/share/glance-simplestreams-sync/glance-simplestreams-sync.py", 
line 273, 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 242, in insert_item
  if self.config['hypervisor_mapping'] and 'ftype' in flat:
  KeyError: 'hypervisor_mapping'

  
  [Regression Potential]

  * This patch makes an argument optional only, there is no expected
  regressions in users of this library.

  [Other Info]

  The bundle used in the test case uses a modified version of the
  glance-simplestreams-sync charm that removes the hypervisor_mapping
  parameter when using simplestreams library.
  https://pastebin.ubuntu.com/p/Ny7jFnGfnY/

To manage notifications about this bug go to:
https://bugs.launchpad.net/simplestreams/+bug/1578622/+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 1686086] Re: glance mirror and nova-lxd need support for squashfs images

2019-10-16 Thread Rafael David Tinoco
** Changed in: simplestreams (Ubuntu Xenial)
   Status: In Progress => Won't Fix

** Changed in: simplestreams (Ubuntu Bionic)
   Status: Fix Released => In Progress

** Changed in: simplestreams (Ubuntu Xenial)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: simplestreams (Ubuntu Bionic)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

-- 
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:
  Won't Fix
Status in simplestreams source package in Artful:
  Won't Fix
Status in simplestreams source package in Bionic:
  In Progress
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 1719879] Re: [SRU] swift client needs to use v1 auth prior to ocata

2019-10-16 Thread Rafael David Tinoco
** Changed in: simplestreams (Ubuntu Xenial)
   Status: In Progress => Won't Fix

** Changed in: simplestreams (Ubuntu Bionic)
   Status: Fix Released => In Progress

** Changed in: simplestreams (Ubuntu Xenial)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: simplestreams (Ubuntu Bionic)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

-- 
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:
  Won't Fix
Status in simplestreams source package in Artful:
  Won't Fix
Status in simplestreams source package in Bionic:
  In Progress
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 1686437] Re: [SRU] glance sync: need keystone v3 auth support

2019-10-16 Thread Rafael David Tinoco
** Changed in: simplestreams (Ubuntu Bionic)
   Status: Fix Released => In Progress

** Changed in: simplestreams (Ubuntu Xenial)
   Status: In Progress => Won't Fix

** Changed in: simplestreams (Ubuntu Xenial)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: simplestreams (Ubuntu Bionic)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

-- 
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/1686437

Title:
  [SRU] glance sync: need keystone v3 auth support

Status in simplestreams:
  Fix Released
Status in simplestreams package in Ubuntu:
  Fix Released
Status in simplestreams source package in Xenial:
  Won't Fix
Status in simplestreams source package in Bionic:
  In Progress
Status in simplestreams source package in Cosmic:
  Fix Released
Status in simplestreams source package in Disco:
  Fix Released

Bug description:
  [Impact]

  simplestreams can't sync images when keystone is configured to use v3,
  keystone v2 is deprecated since mitaka[0] (the version shipped with
  xenial)

  The OpenStack Keystone charm supports v3 only since Queens and
  later[1]

  [Test Case]

  * deploy a openstack environment with keystone v3 enabled
- get a copy of the bundle available at 
http://paste.ubuntu.com/p/hkhsHKqt4h/ , this bundle deploys a minimal version 
of xenial-mitaka.

  Expected result:

  - "glance image-list" lists trusty and xenial images
  - the file glance-simplestreams-sync/0:/var/log/glance-simplestreams-sync.log 
 contains details of the images pulled from cloud-images.u.c (example: 
https://pastebin.ubuntu.com/p/RWG8QrkVDz/ )

  Actual result:

  - "glance image-list" is empty
  - the file glance-simplestreams-sync/0:/var/log/glance-simplestreams-sync.log 
 contains the following stacktrace
  INFO  * 04-09 22:04:06 [PID:14571] * root * Calling DryRun mirror to get 
item list
  ERROR * 04-09 22:04:06 [PID:14571] * root * Exception during syncing:
  Traceback (most recent call last):
File "/usr/share/glance-simplestreams-sync/glance-simplestreams-sync.py", 
line 471, in main
  do_sync(charm_conf, status_exchange)
File "/usr/share/glance-simplestreams-sync/glance-simplestreams-sync.py", 
line 232, in do_sync
  objectstore=store)
File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/glance.py", 
line 374, in __init__
  super(ItemInfoDryRunMirror, self).__init__(config, objectstore)
File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/glance.py", 
line 126, in __init__
  self.keystone_creds = openstack.load_keystone_creds()
File "/usr/lib/python2.7/dist-packages/simplestreams/openstack.py", line 
61, in load_keystone_creds
  raise ValueError("(tenant_id or tenant_name)")
  ValueError: (tenant_id or tenant_name)

  
  [Regression Potential]

  * A possible regression will manifest itself figuring out if v2 or v3
  should be used, after the connection is made there are no further
  changes introduced by this SRU

  
  [Other Info]

  When trying to test my changes for bug 1686086, I was unable to auth
  to keystone, which means glance image sync just doesn't work with
  a v3 keystone.

  Related bugs:
   * bug 1719879: swift client needs to use v1 auth prior to ocata
   * bug 1728982: openstack mirror with keystone v3 always imports new images
   * bug 1611987: glance-simplestreams-sync charm doesn't support keystone v3

  [0] 
https://docs.openstack.org/releasenotes/keystone/mitaka.html#deprecation-notes
  [1] 
https://docs.openstack.org/charm-guide/latest/1802.html#keystone-support-is-v3-only-for-queens-and-later

To manage notifications about this bug go to:
https://bugs.launchpad.net/simplestreams/+bug/1686437/+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 1728982] Re: [SRU] openstack mirror with keystone v3 always imports new images

2019-10-16 Thread Rafael David Tinoco
** Changed in: simplestreams (Ubuntu Xenial)
   Status: In Progress => Won't Fix

** Changed in: simplestreams (Ubuntu Bionic)
   Status: Fix Released => In Progress

** Changed in: simplestreams (Ubuntu Xenial)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: simplestreams (Ubuntu Bionic)
 Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

-- 
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:
  Won't Fix
Status in simplestreams source package in Artful:
  Won't Fix
Status in simplestreams source package in Bionic:
  In Progress
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 1848210] Re: ghostscript: ensure update of cups-filter

2019-10-16 Thread Mauricio Faria de Oliveira
** Patch added: "lp1848210_xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1848210/+attachment/5297503/+files/lp1848210_xenial.debdiff

** Changed in: cups-filters (Ubuntu)
   Status: New => Invalid

** Changed in: cups-filters (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: cups-filters (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: cups-filters (Ubuntu Xenial)
 Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)

** Changed in: cups-filters (Ubuntu Bionic)
 Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)

** Changed in: cups-filters (Ubuntu Xenial)
   Importance: Medium => Undecided

** Changed in: cups-filters (Ubuntu Bionic)
   Importance: Medium => Undecided

-- 
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/1848210

Title:
  ghostscript: ensure update of cups-filter

Status in cups-filters package in Ubuntu:
  Invalid
Status in ghostscript package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Invalid
Status in ghostscript source package in Xenial:
  In Progress
Status in cups-filters source package in Bionic:
  Invalid
Status in ghostscript source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * After an update of ghostscript but not cups-filters
     users may hit errors printing PDF files (LP#1828401).

   * This is possible as Landscape does not consider the
 -security pocket (has both ghostscript/cups-filters)
 but rather USN notices and ghostscript had a notice [0].
 The regression on cups-filters was identified later,
 and doesn't warrant a USN notice.

   * So, to ensure that ghostscript and cups-filters are
     both updated, add a versioned 'Breaks:' relationship
     to ghostscript for older cups-filters versions which
     are not yet fixed.

     Per Debian Policy [1]:

   """
   Normally a Breaks entry will have an “earlier than” version clause;
   such a Breaks is introduced in the version ... [that] reveals a bug
   in earlier versions of the broken package ...

   This use of Breaks will inform higher-level package management tools
   that the broken package must be upgraded before the new one.
   """

   * A versioned 'Depends:' relationship is not possible
     as ghostscript doesn't depend on cups-filters, thus
     it's possible to have ghostscript installed without
     cups-filters at all.

   * This doesn't fix the current situation with Landscape
 and USNs so this same problem might still occur again,
 but at least it is already in place on future updates.

  [Test Case]

   * Install cups-filters version without fix for LP#1828401:
     1.20.2-0ubuntu3 in Bionic, and 1.8.3-2ubuntu3.4 in Xenial.

   * Update ghostscript to/later than fix for CVE-2019-3839-1/-2
     9.26~dfsg+0-0ubuntu0.18.04.9 in Bionic / .16.04.9 in Xenial.

   * Notice it does _not_ update cups-filters to version with fix:
     1.20.2-0ubuntu3.1 in Bionic, and 1.8.3-2ubuntu3.5 in Xenial.

   * $ wget -O ppd-with-pdf-support.ppd \
   
'http://www.openprinting.org/ppd-o-matic.php?driver=hl7x0=Brother-HL-1020=1'

   * $ wget -O dummy.pdf \
   https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     GPL Ghostscript 9.26: Unrecoverable error, exit code 1
     Process is dying with "Unable to determine number of pages, page count: -1
     ", exit stat 3
     ...

   * Note it's broken.

   * Install ghostscript (test) packages with the relationships
     'Breaks: cups-filters (<< 1.20.2-0ubuntu3.1)' in Bionic or
     'Breaks: ..., cups-filters (<< 1.8.3-2ubuntu3.5)' in Xenial.

   * Note it _does_ update cups-filters to version with fix.

   * $ foomatic-rip -v --ppd ppd-with-pdf-support.ppd dummy.pdf
     ...
     Filetype: PDF
     File contains 1 pages
     Starting renderer with command: <...>
     ...

   * Note it's now working.

  [Regression Potential]

   * Low.  This only causes an update to cups-filters to a version
     that fixes an already identified/resolved problem (LP#1828401),
     which is available in bionic- & xenial-updates since May 2019.

  [Other Info]

   * This is only required in Xenial and Bionic.

   * Trusty doesn't have the ghostscript update that causes the problem.

   * Disco/Eoan have the cups-filters fix that it requires (1.22.5+).

  [Links]

  [0] https://usn.ubuntu.com/3970-1/
  [1] 
https://www.debian.org/doc/debian-policy/ch-relationships.html#packages-which-break-other-packages-breaks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1848210/+subscriptions

___
Mailing list: 

[Group.of.nepali.translators] [Bug 1840686] Re: Xenial images won't reboot if disk size is > 2TB when using GPT

2019-10-16 Thread Brian Murray
This is fixed in the version of grub2 in Eoan which will become Ubuntu
19.10.

** Changed in: grub (Ubuntu)
   Status: New => Fix Released

** Changed in: grub (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: grub (Ubuntu Xenial)
   Importance: Undecided => High

-- 
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/1840686

Title:
  Xenial images won't reboot if disk size is > 2TB when using GPT

Status in cloud-init:
  Won't Fix
Status in grub package in Ubuntu:
  Fix Released
Status in grub source package in Xenial:
  Triaged

Bug description:
  CPC team has recently converted Xenial images to use GPT instead of
  MBR.  However, after booting an instance that has a disk size of 2049
  GB or higher, we hang on the next subsequent boot (Logs indicate it
  hanging on "Booting Hard Disk 0".

  This works on Bionic, but what makes it strange is that they have the
  same kernel revision - 4.15.0-1-37.

  patrick_viafore@patviafore-test-3072-xenial:~$ lsb_release -rd
  Description:Ubuntu 16.04.6 LTS
  Release:16.04
  patrick_viafore@patviafore-test-3072-xenial:~$ sudo dpkg -l | grep linux-gcp
  ii  linux-gcp4.15.0.1037.51   
 amd64Complete Google Cloud Platform (GCP) Linux kernel and headers
  ii  linux-gcp-headers-4.15.0-10374.15.0-1037.39~16.04.1   
 amd64Header files related to Linux kernel version 4.15.0

  To reproduce:

  1) Create an image with a disk size of 3072 using a serial that has GPT
  gcloud compute instances create test-3072-xenial --image 
daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel 
--boot-disk-size 3072

  Reboot the instance

  2) It will hang on reboot and you cannot connect

  3) Please note that later serials have the GPT change reverted.

  You can replace xenial with bionic in the above commands to get a
  bionic instance instead.

  To test this out in a more slower fashion:

  1) Create an image with a disk size of 2048 using a serial that has GPT
  gcloud compute instances create test-2048-xenial --image 
daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel 
--boot-disk-size 2048

  2) Resize the disk to 3072

  3) Issue growpart /dev/sda 1

  4) Issue resize2fs /dev/sda1

  5) Issue rsize2fs /dev/sda1 again

  On the second resize2fs, it tries to resize again, but on a working
  instance, it says there's nothing to resize.

  I've tried starting from a Xenial instance and doing a do-release-
  upgrade to get to bionic and then doing the growpart/resize2fs, but
  the issue still shows up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1840686/+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 1784535] Re: ubuntu_quota_smoke_test failed with KVM kernel

2019-10-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-kvm - 5.0.0-1020.21

---
linux-kvm (5.0.0-1020.21) disco; urgency=medium

  * disco/linux-kvm: 5.0.0-1020.21 -proposed tracker (LP: #1846087)

  * ubuntu_sysdig fails on kvm kernels (LP: #1841956)
- [Config] linux-kvm: CONFIG_FTRACE=y

  * ubuntu_quota_smoke_test failed with KVM kernel (LP: #1784535)
- [Config] Enable quota module support

  * please include kernel module CONFIG_NETFILTER_XT_SET (LP: #1843051)
- [Config] Enable NETFILTER_XT_SET module

  [ Ubuntu: 5.0.0-32.34 ]

  * disco/linux: 5.0.0-32.34 -proposed tracker (LP: #1846097)
  * CVE-2019-14814 // CVE-2019-14815 // CVE-2019-14816
- mwifiex: Fix three heap overflow at parsing element in 
cfg80211_ap_settings
  * CVE-2019-15505
- media: technisat-usb2: break out of loop at end of buffer
  * CVE-2019-2181
- binder: check for overflow when alloc for security context
  * Support Hi1620 zip hw accelerator (LP: #1845355)
- [Config] Enable HiSilicon QM/ZIP as modules
- crypto: hisilicon - add queue management driver for HiSilicon QM module
- crypto: hisilicon - add hardware SGL support
- crypto: hisilicon - add HiSilicon ZIP accelerator support
- crypto: hisilicon - add SRIOV support for ZIP
- Documentation: Add debugfs doc for hisi_zip
- crypto: hisilicon - add debugfs for ZIP and QM
- MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller driver
- crypto: hisilicon - fix kbuild warnings
- crypto: hisilicon - add dependency for CRYPTO_DEV_HISI_ZIP
- crypto: hisilicon - init curr_sgl_dma to fix compile warning
- crypto: hisilicon - add missing single_release
- crypto: hisilicon - fix error handle in hisi_zip_create_req_q
- crypto: hisilicon - Fix warning on printing %p with dma_addr_t
- crypto: hisilicon - Fix return value check in hisi_zip_acompress()
- crypto: hisilicon - avoid unused function warning
  * xfrm interface: several kernel panic (LP: #1836261)
- xfrm interface: fix memory leak on creation
- xfrm interface: avoid corruption on changelink
- xfrm interface: ifname may be wrong in logs
- xfrm interface: fix list corruption for x-netns
- xfrm interface: fix management of phydev
  * shiftfs: drop entries from cache on unlink (LP: #1841977)
- SAUCE: shiftfs: fix buggy unlink logic
  * shiftfs: mark kmem_cache as reclaimable (LP: #1842059)
- SAUCE: shiftfs: mark slab objects SLAB_RECLAIM_ACCOUNT
  *  Suspend to RAM(S3) does not wake up for latest megaraid and mpt3sas
adapters(SAS3.5 onwards) (LP: #1838751)
- PCI: Restore Resizable BAR size bits correctly for 1MB BARs
  * No sound inputs from the external microphone and headset on a Dell machine
(LP: #1842265)
- ALSA: hda - Expand pin_match function to match upcoming new tbls
- ALSA: hda - Define a fallback_pin_fixup_tbl for alc269 family
  * Add -fcf-protection=none when using retpoline flags (LP: #1843291)
- SAUCE: kbuild: add -fcf-protection=none when using retpoline flags
  * Disco update: upstream stable patchset 2019-09-25 (LP: #1845390)
- bridge/mdb: remove wrong use of NLM_F_MULTI
- cdc_ether: fix rndis support for Mediatek based smartphones
- ipv6: Fix the link time qualifier of 'ping_v6_proc_exit_net()'
- isdn/capi: check message length in capi_write()
- ixgbe: Fix secpath usage for IPsec TX offload.
- net: Fix null de-reference of device refcount
- net: gso: Fix skb_segment splat when splitting gso_size mangled skb having
  linear-headed frag_list
- net: phylink: Fix flow control resolution
- net: sched: fix reordering issues
- sch_hhf: ensure quantum and hhf_non_hh_weight are non-zero
- sctp: Fix the link time qualifier of 'sctp_ctrlsock_exit()'
- sctp: use transport pf_retrans in sctp_do_8_2_transport_strike
- tcp: fix tcp_ecn_withdraw_cwr() to clear TCP_ECN_QUEUE_CWR
- tipc: add NULL pointer check before calling kfree_rcu
- tun: fix use-after-free when register netdev failed
- gpiolib: acpi: Add gpiolib_acpi_run_edge_events_on_boot option and 
blacklist
- gpio: fix line flag validation in linehandle_create
- Btrfs: fix assertion failure during fsync and use of stale transaction
- ixgbe: Prevent u8 wrapping of ITR value to something less than 10us
- genirq: Prevent NULL pointer dereference in resend_irqs()
- KVM: s390: kvm_s390_vm_start_migration: check dirty_bitmap before using it
  as target for memset()
- KVM: s390: Do not leak kernel stack data in the KVM_S390_INTERRUPT ioctl
- KVM: x86: work around leak of uninitialized stack contents
- KVM: nVMX: handle page fault in vmread
- x86/purgatory: Change compiler flags from -mcmodel=kernel to 
-mcmodel=large
  to fix kexec relocation errors
- powerpc: Add barrier_nospec to raw_copy_in_user()
- drm/meson: Add support for XBGR & ABGR formats
- clk: rockchip: Don't yell about bad mmc phases when getting