https://linen.dev logo
Join Slack
Powered by
<@U04S8PLJWMT> getting this error while trying to ...
# replication-ask-ai
r
@kapa.ai getting this error while trying to install newest airbyte version:
Copy code
INFO    Starting Helm Chart installation of 'airbyte/airbyte' (version: 2.1.0)                                                                                                                     
  DEBUG   helm: creating 1 resource(s)                                                                                                                                                               
  DEBUG   helm: Starting delete for "airbyte-admin" ServiceAccount                                                                                                                                   
  DEBUG   helm: Ignoring delete failure for "airbyte-admin" /v1, Kind=ServiceAccount: serviceaccounts "airbyte-admin" not found                                                                      
  DEBUG   helm: beginning wait for 1 resources to be deleted with timeout of 1h0m0s                                                                                                                  
  DEBUG   helm: creating 1 resource(s)                                                                                                                                                               
  DEBUG   helm: Starting delete for "airbyte-admin-role" Role                                                                                                                                        
  DEBUG   helm: Ignoring delete failure for "airbyte-admin-role" <http://rbac.authorization.k8s.io/v1|rbac.authorization.k8s.io/v1>, Kind=Role: <http://roles.rbac.authorization.k8s.io|roles.rbac.authorization.k8s.io> "airbyte-admin-role" not found                             
  DEBUG   helm: beginning wait for 1 resources to be deleted with timeout of 1h0m0s                                                                                                                  
  DEBUG   helm: creating 1 resource(s)                                                                                                                                                               
  DEBUG   helm: Starting delete for "airbyte-admin-binding" RoleBinding                                                                                                                              
  DEBUG   helm: Ignoring delete failure for "airbyte-admin-binding" <http://rbac.authorization.k8s.io/v1|rbac.authorization.k8s.io/v1>, Kind=RoleBinding: <http://rolebindings.rbac.authorization.k8s.io|rolebindings.rbac.authorization.k8s.io> "airbyte-admin-binding" not found         
  DEBUG   helm: beginning wait for 1 resources to be deleted with timeout of 1h0m0s                                                                                                                  
  DEBUG   helm: creating 1 resource(s)                                                                                                                                                               
  DEBUG   helm: Starting delete for "airbyte-abctl-airbyte-env" ConfigMap                                                                                                                            
  DEBUG   helm: Ignoring delete failure for "airbyte-abctl-airbyte-env" /v1, Kind=ConfigMap: configmaps "airbyte-abctl-airbyte-env" not found                                                        
  DEBUG   helm: beginning wait for 1 resources to be deleted with timeout of 1h0m0s                                                                                                                  
  DEBUG   helm: creating 1 resource(s)                                                                                                                                                               
  DEBUG   helm: Starting delete for "airbyte-abctl-airbyte-secrets" Secret                                                                                                                           
  DEBUG   helm: Ignoring delete failure for "airbyte-abctl-airbyte-secrets" /v1, Kind=Secret: secrets "airbyte-abctl-airbyte-secrets" not found                                                      
  DEBUG   helm: beginning wait for 1 resources to be deleted with timeout of 1h0m0s                                                                                                                  
  DEBUG   helm: creating 1 resource(s)                                                                                                                                                               
  DEBUG   helm: Starting delete for "airbyte-abctl-airbyte-telemetry-env" ConfigMap                                                                                                                  
  DEBUG   helm: Ignoring delete failure for "airbyte-abctl-airbyte-telemetry-env" /v1, Kind=ConfigMap: configmaps "airbyte-abctl-airbyte-telemetry-env" not found                                    
  DEBUG   helm: beginning wait for 1 resources to be deleted with timeout of 1h0m0s                                                                                                                  
  DEBUG   helm: creating 1 resource(s)                                                                                                                                                               
  DEBUG   helm: Starting delete for "airbyte-abctl-bootloader" Pod                                                                                                                                   
  DEBUG   helm: Ignoring delete failure for "airbyte-abctl-bootloader" /v1, Kind=Pod: pods "airbyte-abctl-bootloader" not found                                                                      
  DEBUG   helm: beginning wait for 1 resources to be deleted with timeout of 1h0m0s                                                                                                                  
  DEBUG   helm: creating 1 resource(s)                                                                                                                                                               
  DEBUG   helm: Watching for changes to Pod airbyte-abctl-bootloader with timeout of 1h0m0s                                                                                                          
  DEBUG   helm: Add/Modify event for airbyte-abctl-bootloader: ADDED                                                                                                                                 
  DEBUG   helm: Pod airbyte-abctl-bootloader pending                                                                                                                                                 
  DEBUG   helm: Add/Modify event for airbyte-abctl-bootloader: MODIFIED                                                                                                                              
  DEBUG   helm: Pod airbyte-abctl-bootloader pending                                                                                                                                                 
  DEBUG   Successfully assigned airbyte-abctl/airbyte-abctl-bootloader to airbyte-abctl-control-plane                                                                                                
  DEBUG   helm: Add/Modify event for airbyte-abctl-bootloader: MODIFIED                                                                                                                              
  DEBUG   helm: Pod airbyte-abctl-bootloader pending                                                                                                                                                 
  DEBUG   Container image "airbyte/bootloader:2.1.0" already present on machine                                                                                                                      
  DEBUG   Created container: airbyte-bootloader-container                                                                                                                                            
  DEBUG   Started container airbyte-bootloader-container                                                                                                                                             
  DEBUG   helm: Add/Modify event for airbyte-abctl-bootloader: MODIFIED                                                                                                                              
  DEBUG   helm: Pod airbyte-abctl-bootloader running                                                                                                                                                 
  DEBUG   helm: Add/Modify event for airbyte-abctl-bootloader: MODIFIED                                                                                                                              
  DEBUG   helm: Pod airbyte-abctl-bootloader running                                                                                                                                                 
  DEBUG   helm: Add/Modify event for airbyte-abctl-bootloader: MODIFIED                                                                                                                              
  ERROR   Failed to install airbyte/airbyte Helm Chart                                                                                                                                               
  DEBUG   looking at airbyte-abctl-bootloader                                                                                                                                                        
            Failed()
  DEBUG   found logs:  Unsetting empty environment variable 'DD_TRACE_SAM                                                                                                                            
  ERROR   Unable to install Airbyte locally                                                                                                                                                          
  DEBUG   Received unexpected event: *v1.Status
  DEBUG   Event watcher completed.
  ERROR   unable to install airbyte chart: unable to install helm: failed pre-install: 1 error occurred:
          	* pod airbyte-abctl-bootloader failed
k
The error 
pod airbyte-abctl-bootloader failed
during Helm pre-install is a known issue affecting 
abctl
installations. The bootloader pod starts but fails before Airbyte can complete its initialization or migration checks. [Troubleshooting abctl] What's likely happening The 
airbyte-bootloader
is the first component to start during installation. Failures are generally related to the bootloader not being able to connect to the 
airbyte-db
service, or issues with image loading/disk space. [Troubleshooting abctl] Recommended troubleshooting steps 1. Get the full bootloader logs ā€” re-run with verbose mode to see the actual error:abctl local install --verbose 2. Check disk space ā€” image import failures often indicate insufficient disk:df -h docker system df 3. Check pod status and logs directly:kubectl get pods -n airbyte-abctl --kubeconfig ~/.airbyte/abctl/abctl.kubeconfig kubectl logs airbyte-abctl-bootloader -n airbyte-abctl --kubeconfig ~/.airbyte/abctl/abctl.kubeconfig 4. Try a clean reinstall:abctl local uninstall abctl local install -v 5. Try pinning to a known-working chart version ā€” some users have resolved similar issues by downgrading:abctl local install --chart-version=1.7.2[Helm chart broken with abctl] Note on the truncated log Your logs show 
found logs: Unsetting empty environment variable 'DD_TRACE_SAM...
which is cut off. The full bootloader output (via 
--verbose
) will likely reveal the root cause, such as a database connectivity issue or a failed migration. [Migration failing with abctl] šŸ‘ 0 button šŸ‘Ž 0 button ā„¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
r
for point 2:
Copy code
Filesystem        Size  Used Avail Use% Mounted on
devtmpfs          4.0M     0  4.0M   0% /dev
tmpfs             7.8G     0  7.8G   0% /dev/shm
tmpfs             3.1G  592K  3.1G   1% /run
/dev/nvme0n1p1    100G   40G   61G  40% /
tmpfs             7.8G     0  7.8G   0% /tmp
/dev/nvme0n1p128   10M  1.3M  8.7M  13% /boot/efi
tmpfs             1.6G     0  1.6G   0% /run/user/1000
TYPE            TOTAL     ACTIVE    SIZE      RECLAIMABLE
Images          61        1         23.64GB   22.61GB (95%)
Containers      1         1         2.971MB   0B (0%)
Local Volumes   1         1         10.67GB   0B (0%)
Build Cache     0         0         0B        0B
@kapa.ai for point 2:
Copy code
Filesystem        Size  Used Avail Use% Mounted on
devtmpfs          4.0M     0  4.0M   0% /dev
tmpfs             7.8G     0  7.8G   0% /dev/shm
tmpfs             3.1G  592K  3.1G   1% /run
/dev/nvme0n1p1    100G   40G   61G  40% /
tmpfs             7.8G     0  7.8G   0% /tmp
/dev/nvme0n1p128   10M  1.3M  8.7M  13% /boot/efi
tmpfs             1.6G     0  1.6G   0% /run/user/1000
TYPE            TOTAL     ACTIVE    SIZE      RECLAIMABLE
Images          61        1         23.64GB   22.61GB (95%)
Containers      1         1         2.971MB   0B (0%)
Local Volumes   1         1         10.67GB   0B (0%)
Build Cache     0         0         0B        0B
k
Your disk space looks fine (61GB free on the main partition, plenty of 
/tmp
space), so disk space is not the cause of your bootloader failure. However, the Docker output is worth noting: ā€¢ 23.64GB of images, with 22.61GB reclaimable ā€” this means almost all images are unused/dangling. This is not necessarily a problem, but it suggests previous failed install attempts left a lot of debris. ā€¢ 10.67GB in a local volume ā€” this is your Airbyte data volume, and it's fully in use (0B reclaimable). Recommended next steps: 1. Do a clean uninstall first to clear out any leftover state from previous attempts:abctl local uninstall 2. Optionally prune unused Docker images to free up space and avoid conflicts:docker image prune -a 3. Check the full bootloader logs to find the actual root cause ā€” the logs in your original error were truncated (
DD_TRACE_SAM...
). Run:kubectl logs airbyte-abctl-bootloader -n airbyte-abctl --kubeconfig ~/.airbyte/abctl/abctl.kubeconfig 4. Reinstall with verbose mode:abctl local install --verbose Based on similar cases in the GitHub issues, one known root cause is a duplicate key in the remote connector registry (e.g., 
java.lang.IllegalStateException: Duplicate key ...
), which blocks all new installations until resolved upstream. [bootloader failed issue] The full bootloader logs will confirm whether this or a database connectivity issue is the actual cause in your case. šŸ‘ 0 button šŸ‘Ž 0 button ā„¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
r
@kapa.ai here are the bootloader error:
Copy code
2026-04-22 05:13:05,615 [main]	ERROR	o.f.c.i.l.s.Slf4jLog(error):49 - Migration of schema "public" to version "2.1.0.005 - AddLockedStatusAndStatusReason" failed! Changes successfully rolled back.
2026-04-22 05:13:05,620 [main]	ERROR	i.a.b.ApplicationKt(main):28 - Unable to bootstrap Airbyte environment.
org.flywaydb.core.internal.exception.FlywayMigrateException: Migration failed !
	at org.flywaydb.core.internal.command.DbMigrate.doMigrateGroup(DbMigrate.java:399)
	at org.flywaydb.core.internal.command.DbMigrate.lambda$applyMigrations$1(DbMigrate.java:283)
	at org.flywaydb.core.internal.jdbc.TransactionalExecutionTemplate.execute(TransactionalExecutionTemplate.java:59)
	at org.flywaydb.core.internal.command.DbMigrate.applyMigrations(DbMigrate.java:282)
	at org.flywaydb.core.internal.command.DbMigrate.migrateGroup(DbMigrate.java:255)
	at org.flywaydb.core.internal.command.DbMigrate.lambda$migrateAll$0(DbMigrate.java:153)
	at org.flywaydb.database.postgresql.PostgreSQLAdvisoryLockTemplate.execute(PostgreSQLAdvisoryLockTemplate.java:77)
	at org.flywaydb.database.postgresql.PostgreSQLAdvisoryLockTemplate.execute(PostgreSQLAdvisoryLockTemplate.java:64)
	at org.flywaydb.database.postgresql.PostgreSQLConnection.lock(PostgreSQLConnection.java:105)
	at org.flywaydb.core.internal.schemahistory.JdbcTableSchemaHistory.lock(JdbcTableSchemaHistory.java:149)
	at org.flywaydb.core.internal.command.DbMigrate.migrateAll(DbMigrate.java:153)
	at org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:104)
	at org.flywaydb.core.Flyway.lambda$migrate$1(Flyway.java:231)
	at org.flywaydb.core.FlywayExecutor.execute(FlywayExecutor.java:213)
	at org.flywaydb.core.Flyway.migrate(Flyway.java:177)
	at io.airbyte.db.instance.FlywayDatabaseMigrator.migrate(FlywayDatabaseMigrator.kt:35)
	at io.airbyte.bootloader.Bootloader.runFlywayMigration(Bootloader.kt:276)
	at io.airbyte.bootloader.Bootloader.load(Bootloader.kt:86)
	at io.airbyte.bootloader.ApplicationKt.main(Application.kt:25)
Caused by: org.flywaydb.core.api.FlywayException: Migration failed !
	at org.flywaydb.core.internal.resolver.java.JavaMigrationExecutor.executeOnce(JavaMigrationExecutor.java:85)
	at org.flywaydb.core.internal.resolver.java.JavaMigrationExecutor.lambda$execute$0(JavaMigrationExecutor.java:61)
	at org.flywaydb.core.internal.database.DefaultExecutionStrategy.execute(DefaultExecutionStrategy.java:31)
	at org.flywaydb.core.internal.resolver.java.JavaMigrationExecutor.execute(JavaMigrationExecutor.java:60)
	at org.flywaydb.core.internal.command.DbMigrate.doMigrateGroup(DbMigrate.java:391)
	... 18 common frames omitted
Caused by: org.jooq.exception.DataAccessException: SQL [ALTER TYPE status_type ADD VALUE 'locked']; ERROR: must be owner of type status_type
	at org.jooq_3.19.18.POSTGRES.debug(Unknown Source)
	at org.jooq.impl.Tools.translate(Tools.java:3621)
	at org.jooq.impl.Tools.translate(Tools.java:3609)
	at org.jooq.impl.DefaultExecuteContext.sqlException(DefaultExecuteContext.java:827)
	at org.jooq.impl.AbstractQuery.execute(AbstractQuery.java:362)
	at org.jooq.impl.DefaultDSLContext.execute(DefaultDSLContext.java:1110)
	at io.airbyte.db.instance.configs.migrations.V2_1_0_005__AddLockedStatusAndStatusReason$Companion.addLockedValueToStatusType(V2_1_0_005__AddLockedStatusAndStatusReason.kt:29)
	at io.airbyte.db.instance.configs.migrations.V2_1_0_005__AddLockedStatusAndStatusReason.migrate(V2_1_0_005__AddLockedStatusAndStatusReason.kt:23)
	at org.flywaydb.core.internal.resolver.java.JavaMigrationExecutor.executeOnce(JavaMigrationExecutor.java:71)
	... 22 common frames omitted
Caused by: org.postgresql.util.PSQLException: ERROR: must be owner of type status_type
	at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2736)
	at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2421)
	at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:372)
	at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:525)
	at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:435)
	at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:357)
	at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:342)
	at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:318)
	at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:313)
	at com.zaxxer.hikari.pool.ProxyStatement.execute(ProxyStatement.java:95)
	at com.zaxxer.hikari.pool.HikariProxyStatement.execute(HikariProxyStatement.java)
	at org.jooq.tools.jdbc.DefaultStatement.execute(DefaultStatement.java:102)
	at org.jooq.impl.SettingsEnabledPreparedStatement.execute(SettingsEnabledPreparedStatement.java:227)
	at org.jooq.impl.AbstractQuery.execute(AbstractQuery.java:458)
	at org.jooq.impl.AbstractQuery.execute(AbstractQuery.java:348)
	... 26 common frames omitted
k
The root cause is clear from your logs:
Copy code
ERROR: must be owner of type status_type
The Flyway migration 
V2_1_0_005__AddLockedStatusAndStatusReason
is trying to run 
ALTER TYPE status_type ADD VALUE 'locked'
, but the PostgreSQL user Airbyte is connecting with does not own the 
status_type
type in the database. This is a known pattern with external/managed PostgreSQL databases (e.g., RDS, Azure Database for PostgreSQL, etc.). [Migration failing with abctl] What's happening This is a PostgreSQL permissions issue ā€” the database user Airbyte uses must be the owner of the enum type to alter it. This commonly occurs when: ā€¢ You're using an external managed PostgreSQL (e.g., AWS RDS, Azure Flexible Server) ā€¢ The database was previously set up by a different user/role ā€¢ The type was created under a different owner than the current connection user How to fix it You need to reassign ownership of the 
status_type
enum to the PostgreSQL user Airbyte connects with. Connect to your PostgreSQL database as a superuser and run:
Copy code
ALTER TYPE status_type OWNER TO <your_airbyte_db_user>;
Replace 
<your_airbyte_db_user>
with the actual username Airbyte uses to connect to the database. Similar ownership issues have been reported and resolved this way for other enum types (e.g., 
operator_type
, 
permission_type
) in previous Airbyte versions. [Upgrade migration failing; Migration failing with abctl] After fixing the ownership, retry the installation:
Copy code
abctl local install --verbose
šŸ‘ 0 button šŸ‘Ž 0 button ā„¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
2 Views
Open in Slack
PreviousNext
Powered by