Public bug reported:
I am using OpenStack with a Windows Active Directory Server, such that
the [LDAP] chase referrals attribute is set to True. The LDAP search
flow reaches the convert_ldap_result(ldap_result) function inside
** Changed in: keystone
Status: Won't Fix => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1797876
Title:
Default values for registered limit
Reviewed: https://review.openstack.org/580548
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=1d98f0a7d43bc45b66260053bde76d992fd613b8
Submitter: Zuul
Branch:master
commit 1d98f0a7d43bc45b66260053bde76d992fd613b8
Author: Kailun Qin
Date: Fri Jul 6 20:20:08 2018
This is in violation of the rolling upgrade plans. Marking as "wont fix"
** Changed in: keystone
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
Marking as "invalid" now.
** Changed in: keystone
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1660603
Title:
Difference in
Marking as wont fix, the -1 is correct behavior for "no limit".
** Changed in: keystone
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
** Changed in: neutron
Status: New => Won't Fix
** Tags removed: rfe
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1797140
Title:
[RFE] create port by providing parameters
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Changed in: nova/pike
Status: New => Triaged
** Changed in: nova/queens
Status: New => Triaged
** Changed in: nova/pike
Importance: Undecided => Medium
** Changed in: nova/rocky
Status: New =>
Reviewed: https://review.openstack.org/584750
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=71cac4a145d6726703d76ce66e1787df80c3f3cf
Submitter: Zuul
Branch:master
commit 71cac4a145d6726703d76ce66e1787df80c3f3cf
Author: mareklycka
Date: Mon Jul 23 09:45:55 2018
Hi,
I *do* want to fix cloud-init to accept your specific configuration
of openstack datasource. The plan is to fix that under bug 1788487.
I think you're suggesting that you are running nova-lxd as your
platform. Is that correct?
We have a couple options then to fix this:
a.) cloud-init fix
marking this as 'fix-released' on xenial, it is not a problem there as
there is a 'zfs' (virtual) package
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status: New => Confirmed
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
** Tags added: api
** Changed in: nova
Importance: Undecided => Medium
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
**
I disagree that this is too hard to fix. In fact I'm fairly sure I found
it already:
http://git.openstack.org/cgit/openstack/keystone/tree/keystone/auth/plugins/core.py?h=stable/pike#n174
We do a user lookup long before bothering to try to validate the
password. The fix is to continue to go
Public bug reported:
Hi,
I'm using openstack (2:13.1.3-0ubuntu1) in a on-premise cloud to
manage, among other types, LXD ubuntu bionic virtual instances
(that run cloud-init version 18.3-9-g2e62cb8a-0ubuntu1~18.04.2),
and unfortunately the DataSourceOpenStack.py module fails to detect
Public bug reported:
Similar to bug 1491148, growpart does not support growing a lvm device.
It would be good if growpart in conjunction with cloud-init could
recognize that the filesystem was on a volume and grow the underlying
partition or volume group.
Related bugs:
bug 1491148: growpart
Morgan, that's not true, we've switched to managing our own
requirements:
http://lists.openstack.org/pipermail/openstack-
dev/2018-March/128352.html
Looking at stable/rocky we still refer to 3.36.0 so we do need to fix
that ourselves
Public bug reported:
Description
===
For the cases where an error occur inside the box of a component
(nova-conductor, nova-compute, nova-scheduler), the system seems to handle the
error putting the VM instance in the error state. But, earlier errors in the
exchange between each
You need to install the mod_wsgi package, which is mentioned here:
https://docs.openstack.org/keystone/latest/install/keystone-install-
rdo.html#install-and-configure-components
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member
Public bug reported:
Trying to install Keystone version13.0.0 on Intel RedHat platform.
Before we need to start Keystone service, we need to start apache service.
While executing command /usr/bin/httpd following error occurred:
```$ sudo /usr/sbin/httpd
AH00526: Syntax error on line 5 of
** Also affects: keystone
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1793389
Title:
Upgrade to Ocata: Keystone
Public bug reported:
When creating IPv6 firewall rule, the network protocol that can be
selected is ICMP TCP UDP or null，but in fact, ICMPv6 is the message
control protocol we actually need for the firewall rule whose ip-version
= 6.
I tried to create a firewall rule whose "ip-version=6
Public bug reported:
1. Click Create Subnet.
2. In the Create Subnet page, enter a special symbol for the gateway address,
for example *., check Disable Gateway and click Next.
Result: Clicking the "Next" button has no effect.
** Affects: horizon
Importance: Undecided
Status: New
Public bug reported:
I ran into this upgrading another environment into Rocky, deleted the
problematic resource provider, but just ran into it again in another
upgrade of another environment so there's something wonky. Here's the
traceback:
=
2018-10-25 09:18:29.853 7431 ERROR
Public bug reported:
Bug description:
When we write a firewall group rule which limit fip's DNAT traffic, for example
we want to accept the traffic into a VM binding a fip, the rule's destination
address should be VM's intranet IP address (not fip IP address) currently.
However if we associate
24 matches
Mail list logo
