-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Bootloader crashes when using image tags that don't follow semantic versioning #21006
Comments
I can confirm this is still happening in Airbyte latest version as of today (0.42.1). It indeed looks like a regression |
@malikdiarra can you give your thoughts here? |
Hey @rach-r @marcosmarxm, is there a planned ETA for this? |
@SebastienN15 I'm not from the Airbyte team so I can't give you an ETA, but I've encountered the same issue and here's a workaround until this gets fixed |
Oh that's awesome, thank you! 🙇 |
@rach-r @SebastienN15 did you try to disable the |
@marcosmarxm tried it on my side with this line changed to false - name: connectors.versionOverridesEnabled
serve: false but still not working unfortunately (exact same error) |
Environment
Current Behavior
I’m trying to update Airbyte from 0.40.14 to 0.40.26, and the booloader fails because it tries to upgrade my custom connectors, which don’t follow semantic versioning for tag names. I know this issue already happened before, and was solved with this PR.
Expected Behavior
The bootloader shouldn't check for most recent versions of custom connector images, as explained in this PR
I believe (but I could be wrong) that the PR that introduced this issue is #18749
Logs
Bootloader logs
Steps to Reproduce
foo-1.2.3
)Note : the behavior is the same in Docker and in k8s deployment
Are you willing to submit a PR?
Yes, but I would definitely need some guidance on what should be changed.
The text was updated successfully, but these errors were encountered: