In the test_qos_dscp_create_and_update API test, qos policy was made as
admin user (which is correct) but was also owned by admin project. And
later, to check if DSCP marking rule was created in that policy
properly, regular client is used instead.
The problem is that with new S-RBAC API policies, rules are visible to
owners of the policy, not to all users. And due to that this test is
failing with new S-RBAC policies enforced.
This patch fixes it by changing owner of the qos policy to the regular
client's project.
Reviewed: https:/ /review. opendev. org/c/openstack /neutron- tempest- plugin/ +/882818 /opendev. org/openstack/ neutron- tempest- plugin/ commit/ fdfb4741f60a030 9939f82f7aa44a1 1c5f2bbd31
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit fdfb4741f60a030 9939f82f7aa44a1 1c5f2bbd31
Author: Slawek Kaplonski <email address hidden>
Date: Wed May 10 12:48:49 2023 +0200
[S-RBAC] Update DSCP marking rule create API test
In the test_qos_ dscp_create_ and_update API test, qos policy was made as
admin user (which is correct) but was also owned by admin project. And
later, to check if DSCP marking rule was created in that policy
properly, regular client is used instead.
The problem is that with new S-RBAC API policies, rules are visible to
owners of the policy, not to all users. And due to that this test is
failing with new S-RBAC policies enforced.
This patch fixes it by changing owner of the qos policy to the regular
client's project.
Related-Bug: #2018727 017084e482a5811 6520a1ea80f
Change-Id: Iadf69c167cdda0