The issue was not reproducible on the env described above.
I am not sure why MOS Keystone was assigned, because we figured out that the issue is in tempest. I am moving the bugreport back to QA.
The issue was not reproducible on the env described above.
I am not sure why MOS Keystone was assigned, because we figured out that the issue is in tempest. I am moving the bugreport back to QA.