stestr 2.3.1 doesnt work well with ostestr 1.0.0

[Reedip]

After [1] merged into stestr 2.3.1, concurrency is expected to be an int but ostestr defaults to None resulting the below error:

Traceback (most recent call last):
  File ".../bin/ostestr", line 10, in <module>
    sys.exit(main())
  File ".../os_testr/ostestr.py", line 263, in main
    exit(ostestr(sys.argv[1:]))
  File ".../os_testr/ostestr.py", line 259, in ostestr
    return _select_and_call_runner(opts, regex, others)
  File ".../os_testr/ostestr.py", line 212, in _select_and_call_runner
    black_regex=opts.black_regex)
  File ".../os_testr/ostestr.py", line 167, in call_testr
    black_regex=black_regex)
  File ".../stestr/commands/run.py", line 334, in run_command
    concurrency = _to_int(concurrency)
  File ".../stestr/commands/run.py", line 39, in _to_int
    i = int(possible)
TypeError: int() argument must be a string or a number, not 'NoneType'

This issue seems to be fixed in [2], but the gate would be broken for networking-ovn till that is not released

[1]https://github.com/mtreinish/stestr/commit/c93bc81
[2]https://github.com/mtreinish/stestr/commit/ac8dac0

[Reedip (reedip-banerjee-deactivatedaccount)]

patch proposed : https://review.opendev.org/#/c/657223/

[Jakub Libosvar (libosvar)]

This should have been reported against os-testr as networking-ovn doesn't do anything wrong.

[Tim Burke (1-tim-z)]

Fixed in https://review.opendev.org/#/c/651275/

Still needs a release from either os-testr or stestr, though; until then `pip install os-testr` is going to continue to pull down bad versions.

[Takashi Kajinami (kajinamit)]

The fix was relased in os-testr 1.1.0.

https://github.com/openstack/os-testr/commit/595c06c5bc662ec945e728933df6ac5d6ab116c6