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

tenants: internal error when selecting from crdb_internal.node_runtime_info #55701

Closed
andy-kimball opened this issue Oct 19, 2020 · 3 comments · Fixed by #55738
Closed

tenants: internal error when selecting from crdb_internal.node_runtime_info #55701

andy-kimball opened this issue Oct 19, 2020 · 3 comments · Fixed by #55738
Assignees
Labels
A-multitenancy Related to multi-tenancy C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.

Comments

@andy-kimball
Copy link
Contributor

Repro Steps:

  1. Create a tenant cluster.
  2. Run the following SQL in the tenant cluster:
SELECT * FROM crdb_internal.node_runtime_info

EXPECTED: Empty results?
ACTUAL: Internal error

ERROR: internal error: column node_runtime_info.node_id not nullable, but found NULL value
SQLSTATE: XX000
DETAIL: stack trace:
/go/src/github.com/cockroachdb/cockroach/pkg/sql/virtual_schema.go:427: validateRow()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/virtual_schema.go:493: 1()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/crdb_internal.go:210: func45()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/virtual_schema.go:492: 1()
/go/src/github.com/cockroachdb/cockroach/pkg/sql/virtual_table.go:115: func2()
/usr/local/go/src/runtime/asm_amd64.s:1357: goexit()
@andy-kimball andy-kimball added the A-multitenancy Related to multi-tenancy label Oct 19, 2020
@blathers-crl
Copy link

blathers-crl bot commented Oct 19, 2020

Hi @andy-kimball, please add a C-ategory label to your issue. Check out the label system docs.

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.

@andy-kimball
Copy link
Contributor Author

@asubiotto, @nvanbenschoten, @tbg, I'm not quite sure who this issue should be assigned to. My thinking is one of the SQL teams, since it falls within SQL code? But which SQL Team owns internal functions like this? Execution?

@andy-kimball andy-kimball added the C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. label Oct 19, 2020
@andy-kimball
Copy link
Contributor Author

I think there are a number of internal tables that give internal errors. For example, crdb_internal.leases does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-multitenancy Related to multi-tenancy C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants