Public bug reported:
I am trying to set up MFA for ldap users. Ldap configuration is done.
While running the below api as an admin, I get the 403 forbidden error.
PATCH "/v3/users/{user_id}"
{
"user": {
"enabled": true,
"options": {
"multi_factor_auth_enabled":
This bug is believed to be fixed in cloud-init in version 19.2-43. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-6. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-1. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-49. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-23. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-29. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-50. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-2. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-62. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-73. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-55. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-78. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-67. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-79. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-53. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-61. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-57. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-72. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-65. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-76. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-52. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-68. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-80. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.2-70. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
** Changed in: devstack
Status: In Progress => Won't Fix
** Changed in: devstack-plugin-ceph
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
** Also affects: nova
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Also affects: nova/train
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
**
Public bug reported:
In the devstack environment (master branch), stack.sh created the
private network. It has two subnets it (an IPv4 and an IPv6).
A port is created using the "private" network.
Then the port is updated using the "openstack port set --no-fixed-ip"
command. The IPv4 IP
This was fixed in neutron. We can close this in tripleo.
** Changed in: tripleo
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1844124
Title:
Not
Reviewed: https://review.opendev.org/67
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=40950f9c87681a1db0f3819530dd0b89ac5f6553
Submitter: Zuul
Branch:master
commit 40950f9c87681a1db0f3819530dd0b89ac5f6553
Author: Matt Riedemann
Date: Thu Dec 19 09:41:18 2019
Public bug reported:
In case of failing,
"test_cleanup_network_namespaces_cleans_dhcp_and_l3_namespaces" should provide
a more detailed description:
- How many processes are running.
- Print in the exception the "ps" lines of those processes.
This information can provide a better description
Reviewed: https://review.opendev.org/696600
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=258eebea71b1cac37badf429a90d5cf57e4c455c
Submitter: Zuul
Branch:master
commit 258eebea71b1cac37badf429a90d5cf57e4c455c
Author: Bence Romsics
Date: Wed Nov 27 17:59:15 2019
Public bug reported:
Node has 3 interfaces:
-enp5s0f0 - not connected
-enp5s0f1 - connected
-ib0 - an HFI port
Centos7.6 running on the node.
Openstack boots the server with two interfaces enp5s0f1 and ib0 and it
is successful but the node is not reachable. On the node, the cloud-init
Public bug reported:
Could you assist with the following ERRORs
2019-12-19 17:46:06.086 63227 INFO
networking_calico.plugins.ml2.drivers.calico.mech_calico [-] Became the master,
starting StatusWatcher
2019-12-19 17:46:06.087 63227 INFO networking_calico.etcdutils [-] Registering
path
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1857016
Title:
Possible double row.delete() call in ACL code
Status
Reviewed: https://review.opendev.org/695877
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=04a3535e184dddb8ece828b94d44f589b02a3b94
Submitter: Zuul
Branch:master
commit 04a3535e184dddb8ece828b94d44f589b02a3b94
Author: Dmitriy Rabotyagov
Date: Mon Nov 25 12:34:30
Public bug reported:
In some cases when one subnet with some CIDR is removed from router and
immediately removed and other subnet with same CIDR is created and added
to the same router in very short time, it may happen that router port
will not have IP address configured and subnet will be
What is the configuration on your compute nodes? Do you have a timeout
set for live migration? Do you have post-copy or auto-converge enabled?
What version of libvirt and qemu binaries on those nodes?
I'm going to mark this as invalid per a support request until there is
more information to help
Public bug reported:
- [x] This is a doc addition request.
In the section on configuring timeouts for live migration for kvm:
https://docs.openstack.org/nova/latest/admin/configuring-migrations.html
#advanced-configuration-for-kvm-and-qemu
It mentions live_migration_completion_timeout but not
** Changed in: devstack-plugin-ceph
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1853280
Title:
nova-live-migration job
Public bug reported:
LOG:
2019-12-17 02:25:09.269827 2019-12-17 02:25:09.269 10 INFO keystone.common.wsgi
[req-521eb002-385e-4015-8035-16bfbdcf0d33 - - - - -] POST
http://keystone.openstack.svc.region-guiyang-zyy.myinspurcloud.com/v3/auth/tokens
2019-12-17 02:25:09.270180 2019-12-17
As horizon, there is nothing to do.
** Changed in: horizon
Status: In Progress => Invalid
** Also affects: openstack-i18n
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
43 matches
Mail list logo
