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

Jump to bottom

During CI test, only node0 is started #924

Closed
JeffreyDallas opened this issue Jul 16, 2024 · 1 comment · Fixed by #925
Closed

During CI test, only node0 is started #924

JeffreyDallas opened this issue Jul 16, 2024 · 1 comment · Fixed by #925
Assignees
@JeffreyDallas
Labels
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 released
Milestone
v0.33.0

Comments

@JeffreyDallas
Copy link
Contributor

Bill of Materials or CLI Version

No response

Execution Environment

JUnit Extensions

Slf4j Logging Implementation

None

To Reproduce

Using test branch test-haproxy

run


export SCRIPT_NAME=direct-install.sh
./ci_test.sh


### Describe the bug

Node1 and node2 did not have any file upload to hedera directory


### Describe the expected behavior

All nodes should have file upload to hedera directory

### Whole JUnit/CLI Logs

```shell
N/A

Additional Context

No response
@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 Jul 16, 2024
@JeffreyDallas JeffreyDallas self-assigned this Jul 16, 2024
@JeffreyDallas JeffreyDallas added this to the v0.33.0 milestone Jul 16, 2024
@JeffreyDallas JeffreyDallas mentioned this issue Jul 16, 2024
Merged
@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.29.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JeffreyDallas JeffreyDallas

Labels
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 released
Projects
FST Suite
Status: ✅ Done
Milestone
v0.33.0
Development

Successfully merging a pull request may close this issue.

fix: incorrect NODE_NAMES hashgraph/full-stack-testing
2 participants
@JeffreyDallas @swirlds-automation