juju with RackSpace configuration

Bug #1480616 reported by Khairul Aizat Kamarudzzaman on 2015-08-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
Medium
Sergey Matyukevich

Bug Description

fenris@macbuntu:~$ juju status
ERROR Unable to connect to environment "rackspace".
Please check your credentials or use 'juju bootstrap' to create a new environment.

Error details:
tenant-name: expected string, got int(58xxxx)

my environments.yaml :

rackspace:
        type: openstack
        admin-secret: xxxxxxxxxxxxx

        auth-url: https://identity.api.rackspacecloud.com/v2.0/
        tenant-name: 58xxxx
        #tenant-name: characterstringusername
        region: HKG
        # auth-mode: keypair
        # access-key: <secret>
        # secret-key: <secret>
        auth-mode: userpass
        username: characterstringusername
        password: XxXxX123

Curtis Hovey (sinzui) on 2015-08-03
tags: added: openstack-provider rackspace
Changed in juju-core:
importance: Undecided → Medium
status: New → Triaged
Richard Harding (rharding) wrote :

I think this should be a 2.0 blocker. We need to handle these ints internally and accept both string/int fields here.

Changed in juju-core:
assignee: nobody → Sergey Matyukevich (s-matyukevich)
assignee: Sergey Matyukevich (s-matyukevich) → nobody
assignee: nobody → Sergey Matyukevich (s-matyukevich)

 don't think this is actually a bug, at least a bug of rackspace provider. Here you can see, that in the configuration file the field that expects string (tenant-name) is initialized with integer value. And this is exactly what error says

  Error details:
  tenant-name: expected string, got int(58xxxx)

I see 3 possible solutions:
1. Don't do anything, just tell user to put his tenant name in quotes.
2. Inside rackspace provider try to cast tenant name to string, if it is initialized with integer value. This is a kind of a hack, because it will not solve the general issue. If user, for example, will have password that consist only from digits and don't put it inside quotes - he will get exactly the same error.
3. Try to solve this issue in general, and for all fields, that expect string values also accept integer values.

Changed in juju-core:
milestone: none → 2.0-alpha2
tags: added: juju-release-support
Changed in juju-core:
milestone: 2.0-alpha2 → 2.0-alpha3
Changed in juju-core:
milestone: 2.0-alpha3 → 2.0-beta4
Changed in juju-core:
milestone: 2.0-beta4 → 2.0.1
tags: added: usability
affects: juju-core → juju
Changed in juju:
milestone: 2.0.1 → none
milestone: none → 2.0.1
Curtis Hovey (sinzui) on 2016-11-01
Changed in juju:
milestone: 2.0.1 → none
Anastasia (anastasia-macmood) wrote :

I actually do not think that we can do anything here except to advise that this property needs to be quoted.
Just as we'd advise to have an empty password string specified as "" rather than .

Changed in juju:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers