Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shorten logs generate by OCP-19470 #2575

Merged
merged 1 commit into from
Dec 13, 2021
Merged

Shorten logs generate by OCP-19470 #2575

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Shorten logs generate by OCP-19470
  • Loading branch information
@liangxia
liangxia committed Dec 10, 2021
commit 7359331303c6d3951a8df0fbf4c17e23f7131f56
8 changes: 4 additions & 4 deletions features/upgrade/api_auth/upgrade.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -135,12 +135,12 @@ Feature: apiserver and auth related upgrade check
@azure-upi @aws-upi @openstack-upi @vsphere-upi @gcp-upi
Scenario: Default RBAC role, rolebinding, clusterrole and clusterrolebinding without any missing after upgraded - prepare
When I run the :get admin command with:
| resource | clusterroles.rbac |
| o | yaml |
| resource | clusterroles.rbac |
| o | jsonpath={.items[*].metadata.annotations} |
Then the output should contain:
| autoupdate: "true" |
| autoupdate":"true" |
And the output should not contain:
| autoupdate: "false" |
| autoupdate":"false" |
# Make some changes on clusterrole resources before upgrade
Given as admin I successfully patch resource "clusterrole.rbac/system:build-strategy-custom" with:
| {"rules": [{"apiGroups": ["","build.openshift.io"],"resources": ["builds/custom"],"verbs": [ "get" ]}] } |
Expand Down