Having troubles after connecting. stdClass::$tenant undefined.

[tjbenator]

Having some troubles doing anything after creating the initial connection.

error_reporting(E_ALL);
$TENANT_NAME="admin";
$USERNAME="admin";
$PASSWORD="password";

include('openstack.inc');

$endpoint = 'http://172.25.4.10:5000/v2.0';
setDebug('on');

$credentials = array(
        'username' => $USERNAME,
        'password' => $PASSWORD,
        'tenantName' => $TENANT_NAME
);


$conn = new OpenCloud\OpenStack($endpoint, $credentials);

print_r($conn->ServiceCatalog());
?>

Specifically it is saying that "$tenant" isn't defined. I have read over Issue #9 a number of times, but can't seem to get past it.

Debug:(OpenCloud\OpenStack)Resource [http://172.25.4.10:5000/v2.0/tokens] method [POST] body [{
  "auth": {
    "passwordCredentials": {
      "username":"admin",
      "password":"password"
    }
  }
}]
Debug:(OpenCloud\OpenStack)Headers: [Array
(
    [Content-Type] => application/json
)
]
Debug:(OpenCloud\OpenStack)HTTP STATUS [200]
PHP Notice:  Undefined property: stdClass::$tenant in /opt/php-opencloud/lib/openstack.inc on line 304
PHP Notice:  Trying to get property of non-object in /opt/php-opencloud/lib/openstack.inc on line 304
stdClass Object
(
)

[gecampbell]

I guess it's possible that OpenStack doesn't return a tenant ID? I can't seem to make that occur. Could you add this line to openstack.inc:

print_r($resp);

immediately following this line:

$resp = json_decode($json);

which, in the current version of openstack.inc, is on line 299. And then paste the results here (you can remove the token ID or anything else).

I can easily put in a check for tenant:id to get rid of the messages, but I'm not sure how things will work without the tenant ID.

[gecampbell]

See http://docs.openstack.org/developer/keystone/api_curl_examples.html#id3 - according to this, the tenant::id should be returned.

[devicenull]

I can confirm this is happening to me as well.

I started logging the json after $response->HttpBody() in OpenStack::Authenticate, and got this:

{"access": {"token": {"expires": "2013-02-02T22:56:46Z", "id": "*snip*"}, "serviceCatalog": {}, "user": {"username": "admin", "roles_links": [], "id": "*snip*", "roles": [], "name": "admin"}}}

That is the entire response (only the token and ID were removed)

[tjbenator]

Getting near identical results as @devicenull.

{"access": {"token": {"expires": "2013-02-03T02:20:28Z", "id": "SOME_ID"}, "serviceCatalog": {}, "user": {"username": "admin", "roles_links": [], "id": "SOME_ID", "roles": [], "name": "admin"}}}

[tjbenator]

NOTE: I am using Rackspace Private Cloud. http://www.rackspace.com/cloud/private/

I don't believe that changes anything but just thought that i would mention it?

[gecampbell]

I'll definitely try to find out more about this.

Sent from my iPhone; pardon the autocement

On Feb 1, 2013, at 8:34 PM, tjbenator notifications@github.com wrote:

NOTE: I am using Rackspace Private Cloud. http://www.rackspace.com/cloud/private/

I don't believe that changes anything but just thought that i would mention it?

—
Reply to this email directly or view it on GitHub.

[gecampbell]

I'm on a bus with the guy who implemented Keystone, and we determined that this occurs when a pure Keystone (not Rackspace) auth is used. This is expected behavior, so I'll push a fix shortly.