Hi Team,
I was previously able to ingest the Power BI report server source into Datahub, but in the past few days, I have been receiving the following error during the refresh. I would appreciate your guidance. Could this be related to the fact that we recently upgraded Datahub to the latest version?
I’m using version 0.13.0 and UI ingestion
Hey there! 
Make sure your message includes the following information if relevant, so we can help more effectively!
- Are you using UI or CLI for ingestion?
- Which DataHub version are you using? (e.g. 0.12.0)
- What data source(s) are you integrating with DataHub? (e.g. BigQuery)
<@U06TM7M40RK> Can you help with the questions in this thread?
We’re experimenting with a new AI assistant for questions in the <#CUMUWQU66> channel to help you track down helpful resources more quickly. Keep in mind that responses may not always be spot-on; feel free to ask it follow-up questions and don’t forget to provide its responses a 
or 
so other folks in the Community know if you’re still looking for help on the topic!
Thank you for providing the details. Based on your message, it seems like you are experiencing issues with ingesting Power BI report server data into DataHub after upgrading to version 0.13.0. Here are a few steps and considerations that might help you troubleshoot and resolve the issue:
-
Check for Known Issues and Fixes:
- There have been several known issues and fixes related to Power BI ingestion. For example, handling of report names and permissions issues have been discussed in various threads (https://datahubspace.slack.com/archives/CUMUWQU66/p1721067198.573609|source, https://datahubspace.slack.com/archives/CUMUWQU66/p1700746015.437039|source).
- Ensure that the service principal used for Power BI ingestion has the appropriate permissions. Refer to the <PowerBI | DataHub Ingestion Guide> for more details on required permissions.
-
Review Recent Changes in DataHub Version 0.13.0:
- Version 0.13.0 introduced several breaking changes and updates that might affect your ingestion process. For example, changes in the
DataHubGraphclient and dbt ingestion configurations (https://github.com/datahub-project/datahub/blob/master/docs/how/updating-datahub.md|source). - Ensure that your ingestion configurations are compatible with the new version. You might need to update your ingestion recipes or configurations accordingly.
- Version 0.13.0 introduced several breaking changes and updates that might affect your ingestion process. For example, changes in the
-
Logs and Error Messages:
- Review the logs and error messages during the ingestion process. Specific warnings or errors can provide clues about what might be going wrong. For example, issues related to access tokens or report fetching (https://datahubspace.slack.com/archives/CUMUWQU66/p1718717031.499819|source, https://datahubspace.slack.com/archives/CUMUWQU66/p1676377452.280029|source).
-
Community and Support:
- Engage with the DataHub community on Slack or GitHub to see if others have faced similar issues. You can find relevant discussions and potential solutions in the <Slack Slack channels> and <https://github.com/datahub-project/datahub/issues|GitHub issues>.
Would you like more detailed steps on any of these points or additional troubleshooting tips?
Sources:
- <Slack Slack Thread 1>
- <Slack Slack Thread 2>
- <PowerBI | DataHub Ingestion Guide>
- https://github.com/datahub-project/datahub/blob/master/docs/how/updating-datahub.md|https://github.com/datahub-project/datahub/blob/master/docs/how/updating-datahub.md
- https://datahubspace.slack.com/archives/CUMUWQU66/p1718717031.499819|https://datahubspace.slack.com/archives/CUMUWQU66/p1718717031.499819
- https://datahubspace.slack.com/archives/CUMUWQU66/p1676377452.280029|https://datahubspace.slack.com/archives/CUMUWQU66/p1676377452.280029
- <Slack Slack channels>
- <https://github.com/datahub-project/datahub/issues|GitHub issues>
0 button 
0 button 
Hint: Mention @runllm in the thread for followups.
Check if below ip and port are reachable from the host you are running the ingestion
raise MaxRetryError(_pool, url, reason) from reason # type: ignore[arg-type]
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host=‘172.21.0.240’, port=80): M