Github action fiware connection error #150324
Replies: 2 comments
-
![]() logs screenshot |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello
I’m trying to set up my GitHub Actions runner for CI/CD, but I’m encountering connection errors when running unit tests. Here’s a summary of my setup and the issue:
What I’m Doing:
Error Details:
• The tests are failing with:
ConnectionRefusedError: [Errno 111] Connection refused
• Logs show errors like:
HTTP <img width="1678" alt="Screenshot 2025-01-30 at 1 07 46 PM" src="https://github.com/user-attachments/assets/543f60f3-61a9-46e9-815d-ef325c2b2fab" /> ConnectionPool(host='localhost', port=1026): Max retries exceeded...
indicating that the test script cannot communicate with Orion and other FIWARE services.
Debugging Steps Taken:
• Verified that containers are up and healthy using docker ps -a.
• Ensured ports are correctly exposed (1026, 4041, 8668, 1883, etc.).
• Checked logs of FIWARE services (docker compose logs), and everything seems fine.
• Ensured that .env variables point to the correct service names inside Docker (e.g., CB_URL=http://orion:1026).
• Used a sleep/wait loop to ensure services are fully up before running tests.
• Tried running tests inside the running orion container (docker exec -it orion bash) to check if internal networking is the issue, but still got connection refused errors.
Possible Issue & Questions:
• Could it be that the GitHub Actions runner is running the tests in a separate network from the Docker containers?
• Do I need to explicitly connect the test runner to the fiware Docker network?
• Has anyone successfully integrated FIWARE with GitHub Actions and can share a working setup?
I’ve attached screenshots showing my container status and error logs. Any help would be greatly appreciated!
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions