Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    phaniraja
    @phanirockzz_twitter
    the above issue resolved by placing the plugins in the ~/.rally/plugins path in the container too
    sandeepvtalekar-cpu
    @sandeepvtalekar-cpu
    Hi Team,
    i am getting below error after running rally deployment check, can any one help to fix ?rally deployment show
    2020-10-19 00:02:09.110 12848 WARNING rally.common.plugin.discover [-] Failed to load plugins from module 'rally_openstack' (package: 'rally-openstack 2.0.0'): (setuptools 39.2.0 (/usr/lib/python3.6/site-packages), Requirement.parse('setuptools>=40.3.0'), {'google-auth'}): pkg_resources.ContextualVersionConflict: (setuptools 39.2.0 (/usr/lib/python3.6/site-packages), Requirement.parse('setuptools>=40.3.0'), {'google-auth'})
    2020-10-19 00:02:09.111 12848 INFO rally.common.plugin.discover [-] Loading plugins from directories /root/.rally/plugins/
    Command failed, please check log for more info
    2020-10-19 00:02:09.139 12848 CRITICAL rally [-] Unhandled error: KeyError: 'openstack'
    2020-10-19 00:02:09.139 12848 ERROR rally Traceback (most recent call last):
    2020-10-19 00:02:09.139 12848 ERROR rally File "/usr/local/bin/rally", line 10, in <module>
    2020-10-19 00:02:09.139 12848 ERROR rally sys.exit(main())
    2020-10-19 00:02:09.139 12848 ERROR rally File "/usr/local/lib/python3.6/site-packages/rally/cli/main.py", line 40, in main
    2020-10-19 00:02:09.139 12848 ERROR rally return cliutils.run(sys.argv, categories)
    2020-10-19 00:02:09.139 12848 ERROR rally File "/usr/local/lib/python3.6/site-packages/rally/cli/cliutils.py", line 657, in run
    2020-10-19 00:02:09.139 12848 ERROR rally ret = fn(
    fn_args, fn_kwargs)
    2020-10-19 00:02:09.139 12848 ERROR rally File "<decorator-gen-21>", line 2, in show
    2020-10-19 00:02:09.139 12848 ERROR rally File "/usr/local/lib/python3.6/site-packages/rally/cli/envutils.py", line 135, in default_from_global
    2020-10-19 00:02:09.139 12848 ERROR rally return f(*args,
    kwargs)
    2020-10-19 00:02:09.139 12848 ERROR rally File "<decorator-gen-20>", line 2, in show
    2020-10-19 00:02:09.139 12848 ERROR rally File "/usr/local/lib/python3.6/site-packages/rally/plugins/init.py", line 59, in ensure_plugins_are_loaded
    2020-10-19 00:02:09.139 12848 ERROR rally return f(args, *kwargs)
    2020-10-19 00:02:09.139 12848 ERROR rally File "/usr/local/lib/python3.6/site-packages/rally/cli/commands/deployment.py", line 205, in show
    xRally-Bot
    @xRally-bot
    [From IRC] JamesBenson : Hi & good morning. I have a question. I'm trying to run tempest through rally, but it seems like it only runs 154 tests and not 223 that refstack runs. Any idea's on why that is?
    xRally-Bot
    @xRally-bot
    [From IRC] andreykurilin : JamesBenson: hi! If you run rally in debug mode, does it throw any errors?
    [From IRC] JamesBenson : debug mode is --detailed, or debug=true in the config or something else?
    [From IRC] andreykurilin : JamesBenson: try rally --debug verify ...
    xRally-Bot
    @xRally-bot
    [From IRC] JamesBenson : Nothing obvious to me, https://pastebin.com/NHUV9Pm0
    xRally-Bot
    @xRally-bot
    [From IRC] andreykurilin : JamesBenson: so you are using the list of tests. Can you verify that all items from your list exists in rally verify list-verifier-tests output? As far as I remember, the full name of the test (including tags order) is strict..
    Jukka Nousiainen
    @junousi

    Hello! I'm trying to understand requirements of the tempest bundled into rally-openstack. It seems that admin credentials are required as a mandatory thing:

    https://github.com/openstack/rally-openstack/blob/master/rally_openstack/verification/tempest/config.py#L46

    Thus I'm hitting this error message when trying to configure verifiers without providing admin credentials. Is there any way to work around this requirement, so one could run tempest verifiers as non-admin?

    I was also looking at upstream tempest, where there seems to be various flags for not running tasks requiring admin ( https://github.com/openstack/tempest/blob/master/tempest/config.py#L57 ), but maybe I'm comparing apples and oranges there.
    Andrey Kurilin
    @andreykurilin
    @junousi hi! As far as I remember tempest supports specifying a list of users to use instead of using admin credentials. I do not have experience in using this feature, so cannot assist in doing this. As for Rally part of configuring tempest - we are lacking maintainers&contributors for this part of Rally. It should not be hard (prepare an yaml list https://github.com/openstack/tempest/blob/master/tempest/config.py#L48 ), but someone should implement this (for rally side I'm ready to assist).
    Jukka Nousiainen
    @junousi

    @andreykurilin Hi, and many thanks for the swift reply :)

    So IIUC

    • rally core: no problem supporting non-admin use-cases
    • tempest: can support non-admin use-cases if parameterized properly
    • rally-openstack tempest - would need code changes to support non-admin use-cases

    (since no matter what I seem to always hit that TempestConfigfileManager() from my first link which has the hardcoded check for the presence of admin credentials)

    Andrey Kurilin
    @andreykurilin
    yes, rally-openstack part should be modified
    Jukka Nousiainen
    @junousi
    Alright, I'll put this in the backburner to see if I could contribute something, might also pop back here to ask stuff and things if getting stuck
    Jukka Nousiainen
    @junousi

    Right, yes I can see this is nontrivial but should be doable if the suitable time appears. Maybe can't neutronclient search for the shared networks either and stuff like that.

    Would a good point to control the "adminity" of a verifier be the verifier specific conf.CONF, or something a bit more external to that?

    If one were to implement this, is it best to strive for the same granularity as in tempest side (isolated networks, dynamic credentials)? In other words, is it too coarse to just have a "non-admin vs. admin" like boolean on the rally-openstack side

    Andrey Kurilin
    @andreykurilin

    @junousi

    in other words, is it too coarse to just have a "non-admin vs. admin" like boolean on the rally-openstack side.

    I like this option. First of all, it doesn't sound too complicated to implement. An of corse, even if we decide to go deeper, this option sounds like a good start.

    Would a good point to control the "adminity" of a verifier be the verifier specific conf.CONF, or something a bit more external to that?

    I'm not a big fan of config options(rally.conf). Imo, there are 2 better options:
    1) setup "non-admin" tempest.conf if there is no admin at rally env and setup "admin" tempest.conf if there is only admin
    2) use --extra-settings arg - https://github.com/openstack/rally/blob/master/rally/cli/commands/verify.py#L127 that should be stored in the database and should be available as self.verifier.extra_settings (or something like that, need to check) at both TempestConfigManager and TempestContext. This argument sounds better than conf.CONF, since rally users will able to configure different type verifiers and use them without modifying config file

    Siavash Sardari
    @siavashsardari
    Hello guys, I was a rally user when the rally version was 1.0.0 . yesterday I wanted to try rally again, and a lot has changed since last time I used rally, unfortunately, docs on readthedocs are not updated. I managed to install and run some scenarios through googling, but is there any documentation or something that can help me use rally? (I need details like I used to on version 1.0.0) Thanks in advanced
    Andrey Kurilin
    @andreykurilin
    @siavashsardari hi! Unfortunately, we do not have constant maintainers that have time to update docs...
    I start working on PR to update some pages, but it still "work in progress".
    The only thing that can help you now to understand what is changed from your last experience are:
    https://github.com/openstack/rally/blob/master/CHANGELOG.rst and https://github.com/openstack/rally-openstack/blob/master/CHANGELOG.rst
    Siavash Sardari
    @siavashsardari
    Thank you.
    Siavash Sardari
    @siavashsardari
    I have an issue with context, is it completely removed?
      NeutronNetworks.create_and_list_subnets:
        -
          args:
            network_create_args: {}
            subnet_create_args: {}
            subnet_cidr_start: "1.1.0.0/30"
            subnets_per_network: 2
          runner:
            type: "constant"
            times: 1
            concurrency: 1
          context:
            network: {}
            users:
              tenants: 1
              users_per_tenant: 1
            quotas:
              neutron:
                network: -1
                subnet: -1
          sla:
            failure_rate:
              max: 0
    Andrey Kurilin
    @andreykurilin
    what issue do you have?
    please, proide more details
    Siavash Sardari
    @siavashsardari
    when I run the above scenario, I get this error:
    Context plugin 'quotas' doesn't pass required_platform@default validation. Details: No admin credentials for openstack
    I think my question is does rally changed it's behavior? if I recall correctly rally used to create new user and tenant and create the subnet in the new tenant.
    Andrey Kurilin
    @andreykurilin
    @siavashsardari read the error message carefully, it doesn't say anything abouyt new users. there is no admin user configured in the rally environment. Can you share output of rally env show --only-spec ?
    Siavash Sardari
    @siavashsardari
    I provided the admin credentials for rally
    # rally env show --only-spec
    {
      "existing@openstack": {
        "auth_url": "http://172.16.140.20:5000/v3",
        "region_name": "RegionOne",
        "https_insecure": false,
        "users": [
          {
            "username": "admin",
            "password": "**********",
            "project_name": "admin"
          }
        ]
      }
    }
    if I remove the context section, the scenario works fine.
    Andrey Kurilin
    @andreykurilin
    there are two sections in the environment - admin and users. first one is for credentials related to admin users. the seocd one(you used) for specifying existing users (to use instead of creating a new one)
    Siavash Sardari
    @siavashsardari
    oh ok thanks
    I have another question regarding the credentials. I updated our oslo.policies for our openstack services. I need to be able to add domain and system scoped credentials in rally, but when I tried that, I got an error which said project_name is a mandatory field.
    did I do somthing wrong there?
    Andrey Kurilin
    @andreykurilin
    I guess we do not support system scoped keystone users yet
    Siavash Sardari
    @siavashsardari
    ok, well I'll be happy if I can contribute to this project, other than basics (gerrit and launchpad) do you have any other advice for me?
    xRally-Bot
    @xRally-bot
    [From IRC] nikparasyr : hello. question reagarding using tempest via rally verify. we've been using rally verify with tempest for quite a while and it is working just fine. we added octavia on one of our test clusters and i want to add the octavia-tempest-plugin. based on the octavia-tempest-plugin docs and tempest docs just installing the plugin is sufficient. When i do install i dont see any new scenarios added in a verify execution by checking `rall
    [From IRC] nikparasyr : y verify list-verifier-tests. with tempest commands i can see it has picked up the octavia plugn viatempest list-plugins`. So the question is basically can i get rally to see the new tempest plugins etc and if yes how? Thanks :)
    [From IRC] nikparasyr : same for the magnum and barbican plugins btw
    xRally-Bot
    @xRally-bot
    [From IRC] andreykurilin : nikparasyr: hi! just had a change to check your question. everything works fine to me. After installing barbican plugin, rally verify list-tests shows 21 new tests. Can you share details of how you are installing tempest plugins?
    xRally-Bot
    @xRally-bot
    [From IRC] nikparasyr : andreykurilin: Hello. thanks for answering :). here is a pastebin of the steps i took: http://paste.openstack.org/show/800625/
    [From IRC] andreykurilin : nikparasyr: ok, it is simple. you are using rally for installing and configuring tempest, but do not use rally for installing the plugin. the issue is that rally installs tempest in virtual environment and your installed tempest plugins are not there :)
    [From IRC] andreykurilin : you should use rally verify add-verifier-ext command
    [From IRC] nikparasyr : ok! i'll have a look. thanks a lot :)
    xRally-Bot
    @xRally-bot
    [From IRC] nikparasyr : yep. got it. thanks a lot :)
    iliyofksy
    @iliyofksy

    Hi everyone, rally env check shows me:

    openstack | Failed to authenticate to http://172.16.7.45:5000/v3 for user 'admin' in project 'admin': The request you have made requires authentication
    #rally env show --only-spec
    {
      "existing@openstack": {
        "auth_url": "http://172.16.7.45:5000/v3",
        "region_name": "RegionOne",
        "https_insecure": false,
        "users": [
          {
            "username": "admin",
            "password": "password",
            "project_name": "admin"
          }
        ]
      }
    };

    any Idea why this happens?

    Andrey Kurilin
    @andreykurilin
    @iliyofksy hi! admin user should be specified at "admin" section instead of users
    iliyofksy
    @iliyofksy
    @andreykurilin Thanks for response.
    I changed the users: section to admin: and create a new env but the error still exist
    I read the keyston.log it shows:
    WARNING Could not find user: admin. WARNING Authorization failed. The request you have made requires authentication;
    iliyofksy
    @iliyofksy
    this problem solved when I defined user_domain_name and project_domain_namein env.yaml