And what about existing images? E.g. resize fails on old images after
upgrading libvirt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864020
Title:
libvirt.libvirtError: Requested operation is
The problem was that I didn't work on the master branch. Re-based and
re-submitted the merge request.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893661
Title:
Support for Intel VROC (Virtual
At the end I was able to do a successful reinstall, using
mdadm_query_detail to investigate if it's a member array of a container,
and skip zeroing in this case.
I've sent a merge request. I didn't add size_kb yet, because I'm lazy
and we don't really need it. Can be added later of course.
--
Only one blocker remaining for a successful reinstall in shutdown_mdadm:
LOG.debug('Wiping mdadm member devices: %s' % md_devs)
for mddev in md_devs:
mdadm.zero_device(mddev, force=True)
As the devices in an array are held by the container, the zero_device
above fail (as it
On 9/2/20 4:51 PM, Ryan Harper wrote:
>> I think your suggestion is a good YAML scheme. I think size_kb:
>> should be optional to fill the whole array with one volume if
>> it's omitted.
>
> Well, it's not that simple. What do we do if it's omitted and
> the config includes multiple volumes from
On 9/2/20 4:54 PM, Ryan Harper wrote:
>> This commit adds VROC container and array creation (on clean disks)
>> https://github.com/gyurco/curtin/commit/fd72c17665c071cde3eb5e047662b04ab993a0dd
>
> Nice!
>
> Now here's the not so fun part. We've not yet moved curtin to github, so code
>
This commit adds VROC container and array creation (on clean disks)
https://github.com/gyurco/curtin/commit/fd72c17665c071cde3eb5e047662b04ab993a0dd
Stopping and destroying existing one is to be done (+specifying a size to be
able to create more than one array in one container).
This config
And the weird behavior of --examine of one disk: the current parser
errors out because of State is duplicated (quadruplicated actually)
mdadm --query --examine /dev/nvme0n1
/dev/nvme0n1:
Magic : Intel Raid ISM Cfg Sig.
Version : 1.3.00
Orig Family : 2b2b3bbf
Family
Hmm, just realized the one has to create dummy disk: entries for the devices
- type: disk
id: /dev/nvme0n1
path: /dev/nvme0n1
- type: disk
id: /dev/nvme1n1
path: /dev/nvme1n1
then they'll be usable for devices in type: raid
Another buglet: metadata is not passed to mdadm_create() in
I suggest to add a level: container to the top-level, as it would imply
to use the -e switch to mdadm, and also would be consistent to the query
output.
- type: raid
id: disk_raid_container0
level: container
metadata: imsm
name: /dev/md/imsm0
devices:
- /dev/nvme0n1p1
-
I think your suggestion is a good YAML scheme. I think size_kb: should
be optional to fill the whole array with one volume if it's omitted. The
number of devices can be looked up by pairing 'container' with 'id'.
The EFI firmware can handle the EFI partition on this kind of RAID, and
for this
Maybe it would be possible to abstract out the container, like:
- type: raid
metadata: imsm
container: /dev/md/imsm0
name: imsm0
devices:
- /dev/nvme0n1p1
- /dev/nvme1n1p1
- type: raid
devices:
- /dev/md/imsm0 # but need to get the number of real devices for -n
name:
1-2) No, only the md-device, the container, raid level and number of devices
(it's possible to create different RAID volumes with different levels in one
container, however the number of devices must be the same in all).
3) AFAIK after stopping and removing all arrays from the container, mdamd
It would be interesting, I'll try to "borrow" a VROC-enabled server for some
days. I think it will be not too hard to add this to curtin. I'll have
questions about the preferred method how to present this to the user, e.g.
maybe an external_metadata: , where could be imsm for now could
The VROC is only for NVMes where the storage directly connected to the
CPU PCIe lanes. Its probable that they're using the same metadata
format, and according to the docs, it requires the same steps to create
the array (first the container, then the array itself), thus I think
both can be
Public bug reported:
MaaS and curtin currently doesn't support creating RAID arrays with NVMe
devices using the Intel Virtual RAID On CPU technology. Even worse, when
it encounters one, it tries to destroy it, but fail to do it also.
Creating a VROC array requires creating an external container
Just to note: since one of the kernel upgrades, this issue is not
present anymore. I'm not sure which version fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773184
Title:
Starting a KVM
My workaround is to not install gnocchi-api, only python-gnocchi, and
create the apache site config manually (which is the only relevant thing
in the gnocchi-api package).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In the above, the middle one that crashes (so the 1st level of guests).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773184
Title:
Starting a KVM guest in a guest (nested VM) crash the kernel
To
It started right after I tried to run our OpenStack CI (so the nested
operation) on Bionic (with OpenStack Queens). Previously I used Xenial (with
kernel 4.4.0), that still works.
The host kernel is still from Xenial.
So:
Host with KVM->Guest with KVM->Nested Guest
Xenial (4.4) -> Bionic
The problem is there with 4.17-rc6
ompute2 login: [ 5290.132368] general protection fault: [#1] SMP PTI
[ 5290.133501] Modules linked in: vxlan ip6_udp_tunnel udp_tunnel ebt_arp
ebt_among ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 xt_CT xt_mac xt_comment
xt_physdev vhost_net vhost tap
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1773184/+attachment/5143883/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773184
apport information
** Tags added: apport-collected ec2-images
** Description changed:
linux-image-4.15.0.22 (20, and probably earlier, too) panics when
starting a guest VM in a nested manner.
compute1 login: [ 4847.733004] general protection fault: [#1] SMP PTI
[ 4847.736595]
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1773184/+attachment/5143885/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1773184/+attachment/5143888/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773184
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1773184/+attachment/5143887/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773184
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1773184/+attachment/5143882/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773184
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1773184/+attachment/5143886/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773184
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1773184/+attachment/5143884/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
linux-image-4.15.0.22 (20, and probably earlier, too) panics when
starting a guest VM in a nested manner.
compute1 login: [ 4847.733004] general protection fault: [#1] SMP PTI
[ 4847.736595] Modules linked in: vxlan ip6_udp_tunnel udp_tunnel ebt_arp
ebt_among
** Changed in: nova/ocata
Assignee: György Szombathelyi (gyurco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607313
Title:
Inconsistency in data stored in libvirt.xml f
Yes, it conflicts only with keystone, cinder, the placement-api (the ones which
runs under Apache with mod_wsgi, the Python2 version). However, not installing
gnocchi-api solves the issue, since python-gnocchi contains all things which
needed to run with mod_wsgi (Python 2), just had to install
...or uwsgi can run gnocchi with Python3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746992
Title:
gnocchi-api in Bionic uses python3, and libapache2-mod-wsgi-py3
conflicts with the python 2
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734788
Title:
serial message ack is slow
To manage notifications about
Seems it is broken in Pike.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659620
Title:
Panels get broken with COMPRESS_OFFLINE = True
To manage notifications about this bug go to:
Public bug reported:
Since the two wsgi modules are conflicting, installing gnocchi-api
breaks other OpenStack services.
** Affects: gnocchi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: python-oslo.messaging (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734788
Title:
serial message ack is slow
To manage
Well, I had something in my long-term memory about the prefetch count and the
bug #1551667, and that was it:
https://review.openstack.org/#/c/385079/
So it seems, it is no longer necessary to set the prefetch count. This code is
still in oslo.messaging.
--
You received this bug notification
No, I did not set rabbit_qos_prefetch_count = 256, good to know about it :)
But it became 1 consumer/queue, since the queues was fully consumed after a
while (during experimenting with the bug #1729865).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: ceilometer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729617
Title:
notification agent does not refresh
To manage
Yepp, it works!
qemu-img info --force-share disk
It is easy to add this into Nova. Just need to care of older qemu-img
versions somehow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718133
Title:
Seems there was a patchset submitted, but I don't see --no-lock or -L options
in qemu-img:
https://lists.gnu.org/archive/html/qemu-block/2016-04/msg00349.html
If it would be there, then nova could call qemu-img --no-lock ...
--
You received this bug notification because you are a member of
Maybe this is the problem (from Qemu 2.10 changelog):
- Image locking is added and enabled by default. Multiple QEMU processes
cannot write to the same image as long as the host supports OFD or posix
locking, unless options are specified otherwise.
But 'qemu-img info' should not require a write
Public bug reported:
In Pike from Cloud Archive, Live Block Migrations fail:
Error updating resources for node compute1.: InvalidDiskInfo: Disk info file is
invalid: qemu-img failed to execute on
/var/lib/nova/instances/ccca487b-d5db-4324-81fb-2665e60da038/disk : Unexpected
error while running
Public bug reported:
>From Pike, the vpnaas and fwaas UIs are in a separate package, neutron-
vpnaas-dashboard and neutron-fwaas-dashboard. They're now missing from
Ubuntu.
** Affects: openstack-dashboard (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
The affected package is murano-cfapi 1:3.2.0-0ubuntu1~cloud0 (Ocata)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671031
Title:
murano-cfapi refers to the config file murano-cfapi-cfapi.conf
To
Public bug reported:
The murano-cfapi init script has these lines:
NAME=${PROJECT_NAME}-cfapi
CONFIG_FILE=/etc/${PROJECT_NAME}/${NAME}-cfapi.conf
which ends in CONFIG_FILE=/etc/murano/murano-cfapi-cfapi.conf
The correct file would be just /etc/murano/murano-cfapi.conf
** Affects: murano
Public bug reported:
There's no logrotate script in gnocchi-common, and also the log
directory is not present in the package.
** Affects: gnocchi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry, didn't update the bug report. It is already fixed:
https://review.openstack.org/#/c/335421/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583524
Title:
nova-lxd doesn't create the VLAN
Sorry, not Mitaka, Newton
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1635131
Title:
Value for option url is not valid: invalid URI (inappropriate
validation of rfc3986)
To manage
And I think requirements.txt in Mitaka needs an update for python-
rfc3986
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1635131
Title:
Value for option url is not valid: invalid URI (inappropriate
Yepp, please upgrade python-rfc3986
** Also affects: python-rfc3986 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1635131
Title:
Value for
Public bug reported:
The directory /usr/lib/python2.7/dist-packages/magnum/db/sqlalchemy
misses alembic.ini and the whole alembic subdirectory, so magnum-db-
manage upgrade head fails with the error 'There must be at least one
plugin active.'
** Affects: magnum (Ubuntu)
Importance:
Public bug reported:
Ceph packages miss the ceph-{osd,mon,mds}.target files, so (re)starting
all ceph services in one step is impossible with systemd, the
ceph.target (which is installed) is useless.
The missing files are in the ceph repo:
https://github.com/ceph/ceph/tree/master/systemd
In what version of python-designate-dashboard? I see 2.0.0-1 is still in
Xenial, no newer version available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579670
Title:
Designate dashboard 2.0.0-1
Ok, seems the problem is that Heat with the CloudWatch user_data_format
tries to inject a python script with user-data.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577787
Title:
User-data
Even a
'''
#!/bin/bash
echo "hello world"
'''
doesn't run.
But will retest with recent images.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577787
Title:
User-data scripts are not executing in
Thanks for looking into this, there are packages for Xenial (with a
small bug), only Trusty/cloud archive misses them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570358
Title:
Mitaka dashboard
After some debugging, it seems that the linuxbridge agent scans only for
tap devices in get_all_devices, but lxd creates veth interfaces. Maybe
LXD with the LinuxBridge agent will never work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Seems I was wrong, it is the job of the neutron agent to create the VLAN
interface, but it is not notified to do it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583524
Title:
nova-lxd doesn't
Public bug reported:
Using nova-lxd with LinuxBridge/VLAN segmentation doesn't create the
VLAN tagged interface on the compute.
Seems in vif.py, function plug_bridge() checks for the 'should_create_vlan'
meta tag on the network, but it is never set.
Browsing nova code, it is set only in
Public bug reported:
After installing python-manila-ui, Horizon throws an exception:
TemplateDoesNotExist at /project/shares/
project/shares/index.html
Seems the templates are missing from the package.
** Affects: manila-ui (Ubuntu)
Importance: Undecided
Status: New
--
You
Public bug reported:
Murano-dashboard throws the following exception:
[Mon May 09 09:14:25.963149 2016] [wsgi:error] [pid 30479:tid 140252105045760]
Internal Server Error: /horizon/murano/environments/
[Mon May 09 09:14:25.963236 2016] [wsgi:error] [pid 30479:tid 140252105045760]
Traceback
Workaround (Fix?): remove traces of pbr from /usr/lib/python2.7/dist-
packages/designatedashboard/__init__.py, and execute collectstatic and
compress in openstack_dashboard/manage.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After installing python-designate-dashboard, Horizon throws an
exception:
[Mon May 09 10:52:52.113798 2016] [wsgi:error] [pid 6783:tid 140263154734848]
[remote 192.168.122.101:9112] mod_wsgi (pid=6783): Exception occurred
processing WSGI script
** Changed in: python-oslo.log (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1520543
Title:
syslog logging is broken in neutron-server
To manage
Public bug reported:
In the Xenial cloud image (xenial-server-cloudimg-amd64-disk1.img), scripts
embedded into user-data don't run.
After installing python-minimal, and the python-pkg-resources package, it
works, even it is a bash script.
Seems cloud-init requires /usr/bin/python and the
Public bug reported:
Installing python-sahara-dashboard results in:
rm: cannot remove '/var/lib/openstack-dashboard/secret-key/.secret_key_store':
No such file or directory
openstack-dashboard doesn't create this directory, I think the postinstall
script should not do this 'rm'.
** Affects:
Even better to set state_path to /var/lib/nova in nova.conf. The default
setting is /usr/lib/python2.7/dist-packages, which is sub-optimal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498344
Public bug reported:
>From Mitaka, openstack-dashboard trove and sahara dashboards are in
their own repository, so now they're missing from Ubuntu.
** Affects: horizon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
/usr/share/openstack-dashboard/static/{auth, bootstrap, custom,
framework, scss, themes} should be deleted
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568971
Title:
Ubuntu Mitaka package fails
Public bug reported:
Upgrading Mitaka from Liberty fails with:
Unpacking openstack-dashboard (2:9.0.0-0ubuntu1~cloud0) over
(2:8.0.1-0ubuntu1~cloud0) ...
.
.
.
Collecting and compressing static assets...
CommandError: An error occurred during rendering
*** This bug is a duplicate of bug 1498344 ***
https://bugs.launchpad.net/bugs/1498344
** This bug has been marked a duplicate of bug 1498344
package nova-common 1:2014.1.5-0ubuntu1.2 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
--
*** This bug is a duplicate of bug 1498344 ***
https://bugs.launchpad.net/bugs/1498344
** This bug has been marked a duplicate of bug 1498344
package nova-common 1:2014.1.5-0ubuntu1.2 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
--
Current workaround: run nova-manage db sync as root, then apt-get install -f
But it is not very convenient (also a nova.sqlite in the python base dir is
weird).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Current workaround: run nova-manage db sync as root, then apt-get install -f
But it is not very convenient (also a nova.sqlite in the python base dir is
weird).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The problem here is when nova-compute updated, and no connection= string in
nova.conf, the postinst script will start nova-manage db sync with the nova
user. But without the connection string, the default path points to
/usr/lib/python2.7/dist-packages, so nova user cannot write the sqlite db
The problem here is when nova-compute updated, and no connection= string in
nova.conf, the postinst script will start nova-manage db sync with the nova
user. But without the connection string, the default path points to
/usr/lib/python2.7/dist-packages, so nova user cannot write the sqlite db
I think this can be closed as FIXED.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1520543
Title:
syslog logging is broken in neutron-server
To manage notifications about this bug go to:
I think this can be closed as FIXED.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-oslo.log in Ubuntu.
https://bugs.launchpad.net/bugs/1520543
Title:
syslog logging is broken in neutron-server
To manage notifications about
** Also affects: ubuntu
Importance: Undecided
Status: New
** Package changed: ubuntu => murano (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500200
Title:
Any component in
Seems it is fixed in python-oslo.log 1.11.0-1ubuntu0~cloud0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1520543
Title:
syslog logging is broken in neutron-server
To manage notifications about
Seems it is fixed in python-oslo.log 1.11.0-1ubuntu0~cloud0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-oslo.log in Ubuntu.
https://bugs.launchpad.net/bugs/1520543
Title:
syslog logging is broken in neutron-server
To
It is also wrong in Wily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445616
Title:
crmsh in vivid is not compatible with pacemaker
To manage notifications about this bug go to:
It is also wrong in Wily.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to crmsh in Ubuntu.
https://bugs.launchpad.net/bugs/1445616
Title:
crmsh in vivid is not compatible with pacemaker
To manage notifications about this bug go to:
Public bug reported:
Starting neutron-server with syslog on causes the following exception:
Traceback (most recent call last):
File "/usr/bin/neutron-server", line 10, in
sys.exit(main_wsgi_eventlet())
File
"/usr/lib/python2.7/dist-packages/neutron/cmd/eventlet/server/__init__.py",
Public bug reported:
Starting neutron-server with syslog on causes the following exception:
Traceback (most recent call last):
File "/usr/bin/neutron-server", line 10, in
sys.exit(main_wsgi_eventlet())
File
"/usr/lib/python2.7/dist-packages/neutron/cmd/eventlet/server/__init__.py",
Public bug reported:
Keystone v3 returns the token expiration date with microseconds, e.g.
'2015-11-03T18:30:59.99Z'. The parse_iso8601 function cannot deal with
this, so using Keystone authentication always ends with "Failed to parse
ISO8601 expiration date from Keystone response." in the
Public bug reported:
Keystone v3 returns the token expiration date with microseconds, e.g.
'2015-11-03T18:30:59.99Z'. The parse_iso8601 function cannot deal with
this, so using Keystone authentication always ends with "Failed to parse
ISO8601 expiration date from Keystone response." in the
89 matches
Mail list logo
