We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Run scenarios for backward compatibility test on Jenkins. See scenarios on edgex-taf-pipeline #108 Can't reproduce on my local machine so far.
This issue does not happen every time. Attached backward compose files and logs. backward-compose.zip mqtt-bus-core-data.log mqtt-broker.log
Unable to connect MessageBus: %!w(mqtt.OperationErr={Connect network Error : dial tcp 172.20.0.5:1883: connect: connection refused})"
Deployment Environment:
EdgeX Version [REQUIRED]:
Anything else relevant?
The text was updated successfully, but these errors were encountered:
Can you try setting EDGEX_STARTUP_DURATION: "120" on core data to extend bootstrapping duration? Default is 60s.
EDGEX_STARTUP_DURATION: "120"
Sorry, something went wrong.
Added the EDGEX_STARTUP_DURATION: "120" on all core-services and support-services. Still got the issue.
No branches or pull requests
🐞 Bug Report
Affected Services [REQUIRED]
The issue is located in: DataIs this a regression?
NoDescription and Minimal Reproduction [REQUIRED]
Run scenarios for backward compatibility test on Jenkins. See scenarios on edgex-taf-pipeline #108
Can't reproduce on my local machine so far.
This issue does not happen every time.
Attached backward compose files and logs.
backward-compose.zip
mqtt-bus-core-data.log
mqtt-broker.log
🔥 Exception or Error
🌍 Your Environment
Deployment Environment:
EdgeX Version [REQUIRED]:
Anything else relevant?
The text was updated successfully, but these errors were encountered: