openstack team mailing list archive

[Alex Vitola <alex.vitola@xxxxxxxxx>]

reinstalled my environment this week and I have the same problem

I believe the error is in the horizon, as it only happens with

2013/2/17 Gabriel Hurley <Gabriel.Hurley@xxxxxxxxxx>:
> That particular “endpoint not found” log message is a red herring. It’s been
> removed in keystoneclient trunk because it was logging an *expected* error.
> There isn’t supposed to be a service catalog available at the point at which
> it logged that message, and it lead to confusion just like this.
>
>
>
> However, as for your actual problem, I’ve got a couple broad ideas:
>
>
>
> Since you’re able to log in that means Keystone is working. And since you’re
> not seeing any error messages indicating that the data couldn’t be retrieved
> from Nova, that means Nova is working and is truly believes that the tenant
> you’re requesting data for has no instances, etc.
>
>
>
> What that sounds like to me is that you’re creating things in Nova with one
> tenant, and then looking for them in Horizon with a different tenant. The
> easiest way to check for that would be to log into horizon with a user who
> has the “admin” role on a project, navigate to the Instances panel in the
> Admin dashboard, and see if you can see the missing instances there. The
> admin instances panel shows *all* running instances across all tenants, so
> if the instances exist and Nova is returning data then they’ll show up
> there.
>
>
>
> The other (much less likely) possibility is that you somehow have two Nova
> services running which are unaware of each other, and you’re managing to
> talk to different ones via the client vs. Horizon. I have to think you’d
> know if you were running two Nova’s, however.
>
>
>
> The last option would be that Keystone’s service catalog is misconfigured
> and you’re not actually communicating with Nova, but if that were the case
> you should be seeing errors all over the place, so I find that highly
> unlikely.
>
>
>
> Hope something there helps.
>
>
>
> -          Gabriel
>
>
>
> From: openstack-bounces+gabriel.hurley=nebula.com@xxxxxxxxxxxxxxxxxxx
> [mailto:openstack-bounces+gabriel.hurley=nebula.com@xxxxxxxxxxxxxxxxxxx] On
> Behalf Of Greg Chavez
> Sent: Saturday, February 16, 2013 11:54 PM
> To: openstack@xxxxxxxxxxxxxxxxxxx
> Subject: [Openstack] Horizon & Keystone & Nova miscommunication
>
>
>
>
>
> It seems that nova and horizon are not communicating on my controller node.
> Acces and security objects created with nova are not seen by Horizon and
> vice versa.  This includes key pairs and secgroup rules.  For example, if I
> create a keypair with the nova client, it isn't visible in horizon, and if I
> create one in horizon it is not visible via the nova client.
>
>
>
> Possibly related: VMs that I create, whether via the nova client or Horizon,
> are not shown with I run "nova list".  The nova-api.log shows a successful
> servers-detail query, but it comes back empty.
>
>
>
> Also possibly related: Although I have all my services and endpoints
> configured correctly, I can't get individual endpoint detail with
> "endpoint-get".  What's more, I see this error in Horizon's error log:
>
>
>
> [Sun Feb 17 07:02:50 2013] [error] EndpointNotFound: Endpoint not found.
>
> [Sun Feb 17 07:06:55 2013] [error] unable to retrieve service catalog with
> token
>
>
>
> This matches what I get when I run:
>
>
>
> $ keystone endpoint-get --service nova
>
> Endpoint not found.
>
>
>
> But that can't be because "endpoint-list" shows all six endpoints I created
> and all the information seems correct in the database:
>
>
>
>
>
> mysql> select * from endpoint where service_id
> ='9e40d355b49342f8ac6947c497df76d2'\G
>
> *************************** 1. row ***************************
>
>         id: 922baafde75f4cffa7dbe7f57cddb951
>
>     region: RegionOne
>
> service_id: 9e40d355b49342f8ac6947c497df76d2
>
>      extra: {"adminurl": "http://192.168.241.100:35357/v2.0";, "internalurl":
> "http://192.168.241.100:5000/v2.0";, "publicurl":
> "http://10.21.164.75:5000/v2.0"}
>
> 1 row in set (0.00 sec)
>
>
>
> mysql> select * from service where id ='9e40d355b49342f8ac6947c497df76d2'\G
>
> *************************** 1. row ***************************
>
>    id: 9e40d355b49342f8ac6947c497df76d2
>
>  type: identity
>
> extra: {"description": "OpenStack Identity", "name": "keystone"}
>
> 1 row in set (0.00 sec)
>
>
>
> Please please please help me.  My boss is giving my project the ax on Monday
> if I can't get this to work.
>
>
>
> --
> \*..+.-
> --Greg Chavez
> +//..;};
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>