Bug #107326 <cluster>.status() requires print to output the status
Submitted: 18 May 11:10 Modified: 7 Jul 22:24
Reporter: Andy Dublin Email Updates:
Status: Closed Impact on me:
None 
Category:Shell VSCode Extension Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[18 May 11:10] Andy Dublin
Description:
cluster.status() is hanging and not outputting anything but hanging with the following message:

{ "type": "PENDING", "msg": "Executing..." }

with the output

11:37:55.847429 DEBUG2: <- {"request_id": "c07f59c6-beca-4c1a-06d7-1959760ac16f", "request": "execute", "command": "gui.shell.execute", "args": {"command": "cluster.status()", "module_session_id": "0f72824c-d693-11ec-b366-086ac548402b"}}

11:37:55.861530 DEBUG2: -> {"request_state": {"type": "PENDING", "msg": "Execution started..."}, "request_id": "c07f59c6-beca-4c1a-06d7-1959760ac16f"}

11:37:56.6474 DEBUG2: -> {"request_state": {"type": "PENDING", "msg": "Executing..."}, "request_id": "c07f59c6-beca-4c1a-06d7-1959760ac16f", "result": {"clusterName": "devCluster", "defaultReplicaSet": {"name": "default", "primary": "127.0.0.1:3310", "ssl": "REQUIRED", "status": "OK", "statusText": "Cluster is ONLINE and can tolerate up to ONE failure.", "topology": {"127.0.0.1:3310": {"address": "127.0.0.1:3310", "memberRole": "PRIMARY", "mode": "R/W", "readReplicas": {}, "replicationLag": null, "role": "HA", "status": "ONLINE", "version": "8.0.28"}, "127.0.0.1:3320": {"address": "127.0.0.1:3320", "memberRole": "SECONDARY", "mode": "R/O", "readReplicas": {}, "replicationLag": null, "role": "HA", "status": "ONLINE", "version": "8.0.28"}, "127.0.0.1:3330": {"address": "127.0.0.1:3330", "memberRole": "SECONDARY", "mode": "R/O", "readReplicas": {}, "replicationLag": null, "role": "HA", "status": "ONLINE", "version": "8.0.28"}}, "topologyMode": "Single-Primary"}, "groupInformationSourceMember": "127.0.0.1:3310"}}

11:37:56.11736 DEBUG2: -> {"request_state": {"type": "OK", "msg": ""}, "request_id": "c07f59c6-beca-4c1a-06d7-1959760ac16f"}

How to repeat:
run <cluster>.status()

returns nothing

run print (<cluster.status()) to see the output
[19 May 12:20] MySQL Verification Team
HI Mr. Dublin,

Thank you for your bug report.

Please, supply us with a full test case, including the description of your InnoDB Cluster operation and also on how have you connected MySQL Shell to the cluster.

We are waiting on your feedback.
[19 May 12:57] Andy Dublin
Hi

I note you ask: "Please, supply us with a full test case, including the description of your InnoDB Cluster operation and also on how have you connected MySQL Shell to the cluster."

Your question is not relevant:

- The status() method does work in Shell itself
- The status() method does not work when using the embedded shell in VS Code extension, unless you use the print function to output the status. 

This is why I opened the ticket under Shell VS Code extension, not under Shell. :)

I think you need to send it to the MySQL Shell for VS Code team
[19 May 13:49] MySQL Verification Team
Hi Mr. Dublin,

This turns out to be a real bug.

Verified as reported.

Thank you for your contribution.
[7 Jul 22:24] Christine Cole
Posted by developer:
 
No user documentation required.