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.

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

IT role failed #27570

Closed
jingshanglu opened this issue Aug 25, 2021 · 8 comments
Closed

IT role failed #27570

jingshanglu opened this issue Aug 25, 2021 · 8 comments
Assignees
Labels
component/test severity/major type/bug The issue is confirmed as a bug.

Comments

@jingshanglu
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

[2021-08-24T19:10:35.580Z] time="2021-08-25T03:10:35+08:00" level=fatal msg="run test [role] err: sql:SHOW GRANTS FOR current_user() USING `replication`;: failed to run query \n\"SHOW GRANTS FOR current_user() USING `replication`;\" \n around line 216, \nwe need(231):\nSHOW GRANTS FOR current_user() USING `replication`;\nGrants for joe@localhost\nGRANT USAGE ON *.* TO 'joe'@'localhost'\nGRANT UPDATE ON role.* TO 'joe'@'localhost'\nGRANT SELECT,DELETE ON role.t_external TO 'joe'@'localhost'\nGRANT 'rep\nbut got(231):\nSHOW GRANTS FOR current_user() USING `replication`;\nGrants for joe@localhost\nGRANT USAGE ON *.* TO 'joe'@'localhost'\nGRANT SELECT ON role.* TO 'joe'@'localhost'\nGRANT 'replication'@'%', 'wp_administrators'@'%' TO 'joe'@'localhost'\n\n"

[2021-08-24T19:10:35.580Z] + echo 'tidb-server(PID: 434) stopped'

[2021-08-24T19:10:35.580Z] tidb-server(PID: 434) stopped

[2021-08-24T19:10:35.580Z] + kill -9 434

script returned exit code 1

ci:https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_integration_common_test/detail/tidb_ghpr_integration_common_test/6362/pipeline
pr: #27218

2. What did you expect to see? (Required)

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

@jingshanglu jingshanglu added type/bug The issue is confirmed as a bug. component/test severity/major labels Aug 25, 2021
@jingshanglu
Copy link
Contributor Author

@morgo

@zhouqiang-cl
Copy link
Contributor

/cc @bb7133

@morgo morgo self-assigned this Aug 26, 2021
@ti-srebot
Copy link
Contributor

Please edit this comment or add a new comment to complete the following information

Not a bug

  1. Remove the 'type/bug' label
  2. Add notes to indicate why it is not a bug

Duplicate bug

  1. Add the 'type/duplicate' label
  2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions

@zhouqiang-cl
Copy link
Contributor

still have the error @morgo @jingshanglu

run test [role] err: sql:SHOW GRANTS FOR current_user() USING `replication`;: failed to run query \n\"SHOW GRANTS FOR current_user() USING `replication`;\" \n around line 216, \nwe need(231):\nSHOW GRANTS FOR current_user() USING `replication`;\nGrants for joe@localhost\nGRANT USAGE ON *.* TO 'joe'@'localhost'\nGRANT UPDATE ON role.* TO 'joe'@'localhost'\nGRANT SELECT,DELETE ON role.t_external TO 'joe'@'localhost'\nGRANT 'rep\nbut got(231):\nSHOW GRANTS FOR current_user() USING `replication`;\nGrants for joe@localhost\nGRANT USAGE ON *.* TO 'joe'@'localhost'\nGRANT SELECT ON role.* TO 'joe'@'localhost'\nGRANT 'replication'@'%', 'wp_administrators'@'%' TO 'joe'@'localhost'\n\n"

@zhouqiang-cl zhouqiang-cl reopened this Aug 27, 2021
@morgo
Copy link
Contributor

morgo commented Aug 31, 2021

@zhouqiang-cl can you confirm this still exists? Is it possible a failure a few days ago could have been because a branch had not rebased on master?

@zhouqiang-cl
Copy link
Contributor

@zhouqiang-cl can you confirm this still exists? Is it possible a failure a few days ago could have been because a branch had not rebased on master?

thank you @morgo , it not exist now

@github-actions
Copy link

Please check whether the issue should be labeled with 'affects-x.y' or 'backport-x.y.z',
and then remove 'needs-more-info' label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/test severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

6 participants