I believe that the table you have created have a schema that is different from what is needed by your ETL job.

I am not sure but it seems that glue tries to find a table capable of receiving the output of the ETL pipeline with the correct name and schemas. If it doesn't exist (because the schema is wrong), then glue tries to create the table but a table with that name already exists.

Removing the table then rerunning the job worked in my case.