Skip to content

Flag node-aliases-unparsed did not work for solo node logs command #847

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

Closed
JeffreyDallas opened this issue Nov 19, 2024 · 1 comment · Fixed by #848
Closed

Flag node-aliases-unparsed did not work for solo node logs command #847

JeffreyDallas opened this issue Nov 19, 2024 · 1 comment · Fixed by #848
Assignees
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs P1 High priority issue. Required to be completed in the assigned milestone. released

Comments

@JeffreyDallas
Copy link
Contributor

JeffreyDallas commented Nov 19, 2024

Bill of Materials or CLI Version

No response

Execution Environment

Local Node CLI

Slf4j Logging Implementation

None

To Reproduce

npm run solo-test -- node logs -i node1,node2,node3

> @hashgraph/solo@0.99.0 solo-test
> node --no-deprecation --no-warnings --loader ts-node/esm solo.ts node logs -i node1,node2,node3


******************************* Solo *********************************************
Version			: 0.99.0
Kubernetes Context	: kind-solo-cluster
Kubernetes Cluster	: kind-solo-cluster
**********************************************************************************
✖ No value set for required flag: node-aliases-unparsed
◼ Get node logs and configs
*********************************** ERROR *****************************************
Error in downloading log from nodes: No value set for required flag: node-aliases-unparsed
***********************************************************************************

Also the download log command did not work, there were errors in the solo.log

"copyFrom[network-node2-0,8b81721b-11a3-4dc6-9254-6f86a9d5264a]: [srcPath=/opt/hgcapp/services-hedera/HapiApp2.0/network-node2-0.zip, destDir=/Users/jeffrey/.solo/logs/solo-e2e/2024-11-19T16-17-39-049Z]"
"execContainer[network-node1-0,194defb8-e603-425b-b18e-d96ff63f3c1e]: Failure occurred"
"failed to download logs from pod network-node1-0 unable to check path in 'network-node1-0':root-container' - /opt/hgcapp/services-hedera/HapiApp2.0/network-node1-0.zip: ls: cannot access '/opt/hgcapp/services-hedera/HapiApp2.0/network-node1-0.zip': No such file or directory\n:execContainer[network-node1-0,194defb8-e603-425b-b18e-d96ff63f3c1e]: Failure occurred"
"getNodeLogs(network-node1-0): ...end"
"execContainer[network-node1-0,194defb8-e603-425b-b18e-d96ff63f3c1e]: connection closed"
"execContainer[network-node2-0,b22d4417-2b68-4fe4-9f62-b12fbb524082]: begin... command=[ls -la /opt/hgcapp/services-hedera/HapiApp2.0/network-node2-0.zip]"
"execContainer[network-node2-0,b22d4417-2b68-4fe4-9f62-b12fbb524082]: running..."
"execContainer[network-node2-0,b22d4417-2b68-4fe4-9f62-b12fbb524082]: connection established"
"execContainer[network-node2-0,b22d4417-2b68-4fe4-9f62-b12fbb524082]: received message"
"execContainer[network-node2-0,b22d4417-2b68-4fe4-9f62-b12fbb524082]: Failure occurred"
"failed to download logs from pod network-node2-0 unable to check path in 'network-node2-0':root-container' - /opt/hgcapp/services-hedera/HapiApp2.0/network-node2-0.zip: ls: cannot access '/opt/hgcapp/services-hedera/HapiApp2.0/network-node2-0.zip': No such file or directory\n:execContainer[network-node2-0,b22d4417-2b68-4fe4-9f62-b12fbb524082]: Failure occurred"
"getNodeLogs(network-node2-0): ...end"
"\u001b[32m✔\u001b[39m Initialize"
@JeffreyDallas JeffreyDallas added Bug A error that causes the feature to behave differently than what was expected based on design docs Pending Triage New issue that needs to be triaged by the team labels Nov 19, 2024
@JeffreyDallas JeffreyDallas self-assigned this Nov 19, 2024
@jeromy-cannon jeromy-cannon added P1 High priority issue. Required to be completed in the assigned milestone. and removed Pending Triage New issue that needs to be triaged by the team labels Nov 19, 2024
@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.32.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs P1 High priority issue. Required to be completed in the assigned milestone. released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants