[qa] dynamic credentials with the tempest swift client
Udi Kalifon
ukalifon at redhat.com
Tue Jan 22 17:30:50 UTC 2019
Thanks to everyone who helped! I was able to disable dynamic credentials
like this:
1) Add a reference to an accounts file in tempest.conf, and disable the use
of dynamic credentials:
[auth]
test_accounts_file = /home/ukalifon/src/tempest/cloud-01/accounts.yaml
use_dynamic_credentials = False
2) The accounts.yaml file must contain at least 2 uses, one admin and one
regular. Mine looks like this:
- username: 'admin'
tenant_name: 'admin'
password: 'cYsJrqtj7IvC581DxsLZkXlku'
roles:
- 'admin'
- username: 'johndoe'
tenant_name: 'admin'
password: 'johndoe'
roles:
- '_member_'
3) I needed to create the regular user that I placed in my accounts.yaml:
openstack user create --project admin --password johndoe johndoe
openstack role add --project admin --user johndoe _member_
Regards,
Udi Kalifon; Senior QE; RHOS-UI Automation
On Sun, Jan 20, 2019 at 1:06 PM Ghanshyam Mann <gmann at ghanshyammann.com>
wrote:
> Pre-provisioned account is the way to use the existing cred to run the
> Tempest. Can you check in tempest log about the reason
> of test skip? You can take ref of gate job for pre-provisioned accounts [1]
>
> [1]
> http://logs.openstack.org/50/628250/3/check/tempest-full-test-account-py3
>
> -gmann
>
>
> ---- On Sat, 19 Jan 2019 01:01:22 +0900 Udi Kalifon <ukalifon at redhat.com>
> wrote ----
> > When I try this it just skips the tests, and doesn't say anywhere why.
> I added this to my tempest.conf:
> > [auth]
> > test_accounts_file = /home/ukalifon/src/tempest/cloud-01/accounts.yaml
> > use_dynamic_credentials = False
> >
> > And my accounts.yaml looks like this:- username: 'admin'
> > tenant_name: 'admin'
> > password: 'cYsJrqtj7IvC581DxsLZkXlku'
> >
> > Regards,
> > Udi Kalifon; Senior QE; RHOS-UI Automation
> >
> >
> >
> > On Fri, Jan 18, 2019 at 11:08 AM Masayuki Igawa <
> masayuki.igawa at gmail.com> wrote:
> > Hi,
> >
> > On Thu, Jan 17, 2019, at 17:58, Udi Kalifon wrote:
> > :
> > > So I'm looking for a way to utilize the client without it
> automatically
> > > creating itself dynamic credentials; it has to use the
> already-existing
> > > admin credentials on the admin project in order to see the container
> > > with the plans. What's the right way to do that, please? Thanks a
> lot
> > > in advance!
> >
> > Does this pre-provisioned credentials help you?
> >
> https://docs.openstack.org/tempest/latest/configuration.html#pre-provisioned-credentials
> >
> > -- Masayuki Igawa
> > Key fingerprint = C27C 2F00 3A2A 999A 903A 753D 290F 53ED C899 BF89
> >
> >
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190122/5fe23f90/attachment-0001.html>
More information about the openstack-discuss
mailing list