I believe there is a ksv2 regression in the dev ppa of simplestreams,
but I can also confirm that the ksv3 scenario is resolved with the dev
ppa.

#### PASS:
ksv2 + 0.1.0~bzr426-0ubuntu1.2 (distro) + xenial-pike

ksv3 + 0.1.0~bzr459~trunk-0ubuntu1~ubuntu16.04.1 (dev ppa) + xenial-
queens


#### FAIL:
ksv2 + 0.1.0~bzr459~trunk-0ubuntu1~ubuntu16.04.1 (dev ppa) + xenial-pike

ksv3 + 0.1.0~bzr426-0ubuntu1.2 (distro) + xenial-queens

https://paste.ubuntu.com/p/HxttSNpfc8/

-- 
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1686437

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

Status in simplestreams:
  Fix Committed
Status in simplestreams package in Ubuntu:
  Fix Released
Status in simplestreams source package in Xenial:
  Confirmed
Status in simplestreams source package in Zesty:
  Won't Fix

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/~sts-sponsors
Post to     : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More help   : https://help.launchpad.net/ListHelp

Reply via email to