We are using multiple keystone domains - still can't reproduce this.
Do you happen to have a customized keystone policy.json?
Worst case, I would launch a devstack of your targeted release. If you
can't reproduce the issue there, you would at least know its caused by a
nonstandard config
That all looks fine.
I believe that the "default" policy applies in place of any that's not
explicitly specified - i.e. "if there's no matching policy below, you
need to have the admin role to be able to do it". I do have that line in
my policy.json, and I cannot reproduce your problem (see
openstack user create --domain default --password --project-domain ndc
--project test mike
openstack role add --user mike --user-domain default --project test user
my admin account is in the NDC domain with a different username.
/etc/glance/policy.json
{
"context_is_admin":
I suspect that your non-admin user is not really non-admin. How did you
create it?
What you have for "context_is_admin" in glance's policy.json ?
~iain
On 10/18/2018 03:11 PM, Moore, Michael Dane (GSFC-720.0)[BUSINESS
INTEGRA, INC.] wrote:
I have replicated this unexpected behavior
Do you have a liberal/custom policy.json that perhaps is causing unexpected
behavior? Can't seem to reproduce this.
On October 18, 2018 18:13:22 "Moore, Michael Dane (GSFC-720.0)[BUSINESS
INTEGRA, INC.]" wrote:
I have replicated this unexpected behavior in a Pike test environment, in
I have replicated this unexpected behavior in a Pike test environment, in
addition to our Queens environment.
Mike Moore, M.S.S.E.
Systems Engineer, Goddard Private Cloud
michael.d.mo...@nasa.gov
Hydrogen fusion brightens my day.
On 10/18/18, 2:30 PM, "Moore, Michael Dane
It's been deprecated since Pike, and the time has come to remove it [1].
mgagne has been the most vocal CachingScheduler operator I know and he
has tested out the "nova-manage placement heal_allocations" CLI, added
in Rocky, and said it will work for migrating his deployment from the
> Wiadomość napisana przez Remo Mattei w dniu 18.10.2018, o godz.
> 19:08:
>
> Michal, that will never work it’s 11 characters long
Shorter could be Openstack Trouble ;)
>
>
>
>
>> On Oct 18, 2018, at 09:43, Eric Fried wrote:
>>
>> Sorry, I'm opposed to this idea.
>>
>> I admit I
Hi there.
I'm not sure what is happening there and I don't use kolla, so I need
to ask a few more questions.
Is that network ID being used for the VIP or the lb-mgmt-net?
Any chance you can provide a debug log paste from the API process for
this request?
Basically it is saying that network ID
Hello, sorry for late in my answer
the following is the content of my ocata repo file:
[centos-openstack-ocata]
name=CentOS-7 - OpenStack ocata
baseurl=http://mirror.centos.org/centos/7/cloud/$basearch/openstack-ocata/
gpgcheck=1
enabled=1
Sorry, I'm opposed to this idea.
I admit I don't understand the political framework, nor have I read the
governing documents beyond [1], but that document makes it clear that
this is supposed to be a community-wide vote. Is it really legal for
the TC (or whoever has merge rights on [2]) to merge
Hi guys,
I'm back to business with Octavia after a long time but I'm facing an issue
that seems a little bit tricky.
When trying to create a LB using either APIs (cURL/postman) calls or
openstack-client the request finish with an error such as:
`Network c0d40dfd-123e-4a3c-92de-eb7b57178dd3 not
On 10/18/2018 08:31 AM, Anita Kuno wrote:
On 2018-10-18 2:35 a.m., Tony Breeds wrote:
...
However I'd like to suggest we skip the CIVS poll and select 'Train' as
the release name by TC resolution[3]. My think for this is
* It's fun and celebrates a humorous moment in our community
* As
Just do a vote as usual, train is a great candidate :)
On Thu, Oct 18, 2018 at 11:44 PM Melvin Hillsman
wrote:
> I agree with Anita and wonder why Train did not meet the criteria? If
> there is no way for Train to be an option outside of killing the voting,
> than for the sake of integrity of
I agree with Anita and wonder why Train did not meet the criteria? If there
is no way for Train to be an option outside of killing the voting, than for
the sake of integrity of processes which I have heard quite a few people
hold close to we should drop Train from the list. It is an unfortunate
and any talks I give in Denver (Forum, Ops, Main) will include "sl". It's
handy in a variety of ways.
On Thu, Oct 18, 2018 at 9:39 AM David Medberry
wrote:
> I'm fine with Train but I'm also fine with just adding it to the list and
> voting on it. It will win.
>
> Also, for those not familiar
I'm fine with Train but I'm also fine with just adding it to the list and
voting on it. It will win.
Also, for those not familiar with the debian/ubuntu command "sl", now is
the time to become so.
apt install sl
sl -Flea #ftw
On Thu, Oct 18, 2018 at 12:35 AM Tony Breeds
wrote:
> Hello all,
>
On 2018-10-18 2:35 a.m., Tony Breeds wrote:
Hello all,
As per [1] the nomination period for names for the T release have
now closed (actually 3 days ago sorry). The nominated names and any
qualifying remarks can be seen at2].
Proposed Names
* Tarryall
* Teakettle
* Teller
*
On Wed, Oct 17, 2018 at 10:41:36AM -0500, Matt Riedemann wrote:
> On 10/17/2018 9:24 AM, Ivan Kolodyazhny wrote:
> >
> > As you may know, unfortunately, Horizon doesn't support all features
> > provided by APIs. That's why we created feature gaps list [1].
> >
> > I'd got a lot of great
On Wed, Oct 17, 2018 at 4:46 PM Ignazio Cassano
wrote:
> Hello, here the select you suggested:
>
> MariaDB [nova]> select * from shadow_services;
> Empty set (0,00 sec)
>
> MariaDB [nova]> select * from shadow_compute_nodes;
> Empty set (0,00 sec)
>
> As far as the upgrade tooling is concerned,
Hello all,
As per [1] the nomination period for names for the T release have
now closed (actually 3 days ago sorry). The nominated names and any
qualifying remarks can be seen at2].
Proposed Names
* Tarryall
* Teakettle
* Teller
* Telluride
* Thomas
* Thornton
* Tiger
* Tincup
*
21 matches
Mail list logo
