Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Schema creation failed with permission error in preparedDatabases #1130

Closed
neelasha-09 opened this issue Sep 2, 2020 · 7 comments · Fixed by #1139
Closed

Schema creation failed with permission error in preparedDatabases #1130

neelasha-09 opened this issue Sep 2, 2020 · 7 comments · Fixed by #1139
Labels
bug

Comments

@neelasha-09
Copy link
Contributor

neelasha-09 commented Sep 2, 2020 •
edited
Loading

Hi team,

We are trying to create multiple databases using the 'preparedDatabases'.
There is no issue while creating only 1 database and schema. But the issue occurs when we start adding the second database& schema and more.

With the below configuration, the first database & schema passed is created successfully, but the second and other databases and schema creates error.

Below is the configuration of the "cluster values.yaml"

spec:
  additionalVolumes:
  - mountPath: /var/run/postgresql
    name: empty
    targetContainers:
    - all
    volumeSource:
      emptyDir: {}
  numberOfInstances: 1
  patroni:
    pg_hba:
    - hostssl a3s      a3s_a3s_owner_user      all md5
    - hostssl all      postgres                all md5
    - host    all      all                     all md5
  postgresql:
    version: "12"
  preparedDatabases:
    a3sdb:
      schemas:
        a3sschema:
          defaultRoles: true
          defaultUsers: true
    a3s:
      schemas:
        a3s:
          defaultRoles: true
          defaultUsers: true
    a3seb:
      schemas:
        a3seb:
          defaultRoles: true
          defaultUsers: true

The database is getting created but the schema creation failed with permission error:

time="2020-09-02T14:39:15Z" level=info msg="creating database schema \"a3s\" owner \"a3s_a3s_owner\"" cluster-name=pg-testing/postgres-test-interval pkg=cluster
time="2020-09-02T14:39:15Z" level=info msg="creating database schema \"a3sschema\" owner \"a3sdb_a3sschema_owner\"" cluster-name=pg-testing/postgres-test-interval pkg=cluster
time="2020-09-02T14:39:15Z" level=debug msg="closing database connection" cluster-name=pg-testing/postgres-test-interval pkg=cluster
time="2020-09-02T14:39:15Z" level=warning msg="attempted to close an empty db connection object" cluster-name=pg-testing/postgres-test-interval pkg=cluster
**time="2020-09-02T14:39:15Z" level=error msg="could not sync prepared databases: could not execute create database schema: pq: permission denied for database a3s" cluster-name=pg-testing/postgres-test-interval pkg=cluster**
time="2020-09-02T14:39:15Z" level=info msg="cluster has been updated" cluster-name=pg-testing/postgres-test-interval pkg=controller worker=1

The above log shows , the "a3s" schema is created successfully but the "a3sschema" schema creation failed with permission error.

Could you please suggest how do we create multiple databases using "preparedDatabases"

Thanks
@FxKu
Copy link
Member

FxKu commented Sep 3, 2020

Which operator version do you use? 1.5.0 or latest? Schemas are created by the db owner which has the privileges to do so. Maybe you can check also Posrgres logs for more errors. That would help us. Not sure if having the same name for schema and database can lead to troubles.

@neelasha-09
Copy link
Contributor Author

neelasha-09 commented Sep 3, 2020 •
edited
Loading

Hi,

We are using the operator version: v1.5.0-35-g3ddc56e-dirty.
Please find the logs attached.
[
logs.txt
]

Regarding the same name for schema and database - We are able to create it successfully for the first input passed under preparedDatabases but it doesn't allow to create the schema passed after first input.

In conclusion, it allows to create only one schema one and database using preparedDatabses.
While trying to create multiple schemas and databases, the schema creation fails for rest.

The above example i tried by providing the different schema name and database name , is failing with permission denied error in creating the schema

Please check

@Jan-M
Copy link
Member

Jan-M commented Sep 7, 2020 

2020-09-03 07:04:36.086 UTC,"postgres","postgres",265,"10.254.33.215:54186",5f509584.109,4,"CREATE ROLE",2020-09-03 07:04:36 UTC,6/295,739,ERROR,42704,"role ""camundadb_camundaschema_writer"" does not exist",,,,,,"SET LOCAL synchronous_commit = 'local'; CREATE ROLE ""camundadb_camundaschema_writer_user"" LOGIN IN ROLE ""camundadb_camundaschema_writer"" ADMIN camundadb_camundaschema_owner ENCRYPTED PASSWORD 'md5f200d2c1d968b97f68643ad003317198';",,,""
2020-09-03 07:04:36.114 UTC,"postgres","postgres",266,"10.254.33.215:54188",5f509584.10a,3,"DO",2020-09-03 07:04:36 UTC,6/297,0,ERROR,42704,"role ""camundadb_camundaschema_writer_user"" does not exist",,,,,"SQL statement ""ALTER ROLE ""camundadb_camundaschema_writer_user"" RESET ALL""
2020-09-03 07:04:36.139 UTC,"postgres","postgres",267,"10.254.33.215:54190",5f509584.10b,4,"CREATE ROLE",2020-09-03 07:04:36 UTC,6/299,740,ERROR,42704,"role ""camundadb_camundaschema_owner"" does not exist",,,,,,"SET LOCAL synchronous_commit = 'local'; CREATE ROLE ""camundadb_camundaschema_owner_user"" LOGIN IN ROLE ""camundadb_camundaschema_owner"" ADMIN camundadb_owner ENCRYPTED PASSWORD 'md505af3113113bf552696cde1c6879b764';",,,""
2020-09-03 07:04:36.169 UTC,"postgres","postgres",268,"10.254.33.215:54192",5f509584.10c,3,"DO",2020-09-03 07:04:36 UTC,6/301,0,ERROR,42704,"role ""camundadb_camundaschema_owner_user"" does not exist",,,,,"SQL statement ""ALTER ROLE ""camundadb_camundaschema_owner_user"" RESET ALL""
2020-09-03 07:04:36.195 UTC,"postgres","postgres",269,"10.254.33.215:54194",5f509584.10d,4,"CREATE ROLE",2020-09-03 07:04:36 UTC,6/303,741,ERROR,42704,"role ""asmdb_asmschema_owner"" does not exist",,,,,,"SET LOCAL synchronous_commit = 'local'; CREATE ROLE ""asmdb_asmschema_owner_user"" LOGIN IN ROLE ""asmdb_asmschema_owner"" ADMIN asmdb_owner ENCRYPTED PASSWORD 'md5876384d988334cb2d52dd16aab8c5aab';",,,""
2020-09-03 07:04:36.220 UTC,"postgres","postgres",270,"10.254.33.215:54196",5f509584.10e,3,"DO",2020-09-03 07:04:36 UTC,6/305,0,ERROR,42704,"role ""asmdb_asmschema_owner_user"" does not exist",,,,,"SQL statement ""ALTER ROLE ""asmdb_asmschema_owner_user"" RESET ALL""
2020-09-03 07:04:36.252 UTC,"postgres","postgres",271,"10.254.33.215:54198",5f509584.10f,4,"CREATE ROLE",2020-09-03 07:04:36 UTC,6/307,742,ERROR,42704,"role ""asmdb_asmschema_writer"" does not exist",,,,,,"SET LOCAL synchronous_commit = 'local'; CREATE ROLE ""asmdb_asmschema_writer_user"" LOGIN IN ROLE ""asmdb_asmschema_writer"" ADMIN asmdb_asmschema_owner ENCRYPTED PASSWORD 'md59b5e948ebf980222191ebe9f8d13ee66';",,,""
2020-09-03 07:04:36.283 UTC,"postgres","postgres",272,"10.254.33.215:54200",5f509584.110,3,"DO",2020-09-03 07:04:36 UTC,6/309,0,ERROR,42704,"role ""asmdb_asmschema_writer_user"" does not exist",,,,,"SQL statement ""ALTER ROLE ""asmdb_asmschema_writer_user"" RESET ALL""
2020-09-03 07:04:36.578 UTC,"postgres","postgres",282,"10.254.33.215:54226",5f509584.11a,4,"CREATE ROLE",2020-09-03 07:04:36 UTC,6/329,752,ERROR,42704,"role ""asmdb_asmschema_reader"" does not exist",,,,,,"SET LOCAL synchronous_commit = 'local'; CREATE ROLE ""asmdb_asmschema_writer"" NOLOGIN IN ROLE ""asmdb_asmschema_reader"" ADMIN asmdb_asmschema_owner ENCRYPTED PASSWORD 'md57f56cb12ec9500ff19e277191bc9a6ef';",,,""
2020-09-03 07:04:36.606 UTC,"postgres","postgres",283,"10.254.33.215:54228",5f509584.11b,3,"DO",2020-09-03 07:04:36 UTC,6/331,0,ERROR,42704,"role ""asmdb_asmschema_writer"" does not exist",,,,,"SQL statement ""ALTER ROLE ""asmdb_asmschema_writer"" RESET ALL""
2020-09-03 07:04:36.629 UTC,"postgres","postgres",284,"10.254.33.215:54230",5f509584.11c,4,"CREATE ROLE",2020-09-03 07:04:36 UTC,6/333,753,ERROR,42704,"role ""a3s_a3s_reader"" does not exist",,,,,,"SET LOCAL synchronous_commit = 'local'; CREATE ROLE ""a3s_a3s_writer"" NOLOGIN IN ROLE ""a3s_a3s_reader"" ADMIN a3s_a3s_owner ENCRYPTED PASSWORD 'md5b3c864a7e89114d0d3a72b6edc8e37c6';",,,""
2020-09-03 07:04:36.657 UTC,"postgres","postgres",285,"10.254.33.215:54234",5f509584.11d,3,"DO",2020-09-03 07:04:36 UTC,6/335,0,ERROR,42704,"role ""a3s_a3s_writer"" does not exist",,,,,"SQL statement ""ALTER ROLE ""a3s_a3s_writer"" RESET ALL""
2020-09-03 07:04:36.795 UTC,"postgres","postgres",289,"10.254.33.215:54246",5f509584.121,4,"CREATE ROLE",2020-09-03 07:04:36 UTC,6/343,757,ERROR,42704,"role ""a3s_a3s_reader"" does not exist",,,,,,"SET LOCAL synchronous_commit = 'local'; CREATE ROLE ""a3s_a3s_reader_user"" LOGIN IN ROLE ""a3s_a3s_reader"" ADMIN a3s_a3s_owner ENCRYPTED PASSWORD 'md5b060926fc536cd91c9ed420dd101ef5b';",,,""
2020-09-03 07:04:36.822 UTC,"postgres","postgres",290,"10.254.33.215:54248",5f509584.122,3,"DO",2020-09-03 07:04:36 UTC,6/345,0,ERROR,42704,"role ""a3s_a3s_reader_user"" does not exist",,,,,"SQL statement ""ALTER ROLE ""a3s_a3s_reader_user"" RESET ALL""
2020-09-03 07:04:36.853 UTC,"postgres","postgres",291,"10.254.33.215:54250",5f509584.123,4,"CREATE ROLE",2020-09-03 07:04:36 UTC,6/347,758,ERROR,42704,"role ""a3s_a3s_writer"" does not exist",,,,,,"SET LOCAL synchronous_commit = 'local'; CREATE ROLE ""a3s_a3s_writer_user"" LOGIN IN ROLE ""a3s_a3s_writer"" ADMIN a3s_a3s_owner ENCRYPTED PASSWORD 'md51491fb86d811149f843944c8a769c284';",,,""
2020-09-03 07:04:36.878 UTC,"postgres","postgres",292,"10.254.33.215:54252",5f509584.124,3,"DO",2020-09-03 07:04:36 UTC,6/349,0,ERROR,42704,"role ""a3s_a3s_writer_user"" does not exist",,,,,"SQL statement ""ALTER ROLE ""a3s_a3s_writer_user"" RESET ALL""
2020-09-03 07:04:36.904 UTC,"postgres","postgres",293,"10.254.33.215:54254",5f509584.125,4,"CREATE ROLE",2020-09-03 07:04:36 UTC,6/351,759,ERROR,42704,"role ""a3s_reader"" does not exist",,,,,,"SET LOCAL synchronous_commit = 'local'; CREATE ROLE ""a3s_writer"" NOLOGIN IN ROLE ""a3s_reader"" ADMIN a3s_owner ENCRYPTED PASSWORD 'md5f50bc8b407daed6307efc6ed3939c74d';",,,""
2020-09-03 07:04:36.935 UTC,"postgres","postgres",294,"10.254.33.215:54256",5f509584.126,3,"DO",2020-09-03 07:04:36 UTC,6/353,0,ERROR,42704,"role ""a3s_writer"" does not exist",,,,,"SQL statement ""ALTER ROLE ""a3s_writer"" RESET ALL""
2020-09-03 07:04:37.060 UTC,"postgres","postgres",298,"10.254.33.215:54264",5f509585.12a,4,"CREATE ROLE",2020-09-03 07:04:37 UTC,6/361,763,ERROR,42704,"role ""camundadb_camundaschema_reader"" does not exist",,,,,,"SET LOCAL synchronous_commit = 'local'; CREATE ROLE ""camundadb_camundaschema_reader_user"" LOGIN IN ROLE ""camundadb_camundaschema_reader"" ADMIN camundadb_camundaschema_owner ENCRYPTED PASSWORD 'md5c6db25bddb69f7ccb9027c4d3bae8159';",,,""
2020-09-03 07:04:37.085 UTC,"postgres","postgres",299,"10.254.33.215:54266",5f509585.12b,3,"DO",2020-09-03 07:04:37 UTC,6/363,0,ERROR,42704,"role ""camundadb_camundaschema_reader_user"" does not exist",,,,,"SQL statement ""ALTER ROLE ""camundadb_camundaschema_reader_user"" RESET ALL""
2020-09-03 07:04:37.210 UTC,"postgres","postgres",303,"10.254.33.215:54276",5f509585.12f,4,"CREATE ROLE",2020-09-03 07:04:37 UTC,6/371,767,ERROR,42704,"role ""asmdb_asmschema_reader"" does not exist",,,,,,"SET LOCAL synchronous_commit = 'local'; CREATE ROLE ""asmdb_asmschema_reader_user"" LOGIN IN ROLE ""asmdb_asmschema_reader"" ADMIN asmdb_asmschema_owner ENCRYPTED PASSWORD 'md5b736e252e1f99800f75823f350c5447c';",,,""
2020-09-03 07:04:37.240 UTC,"postgres","postgres",304,"10.254.33.215:54278",5f509585.130,3,"DO",2020-09-03 07:04:37 UTC,6/373,0,ERROR,42704,"role ""asmdb_asmschema_reader_user"" does not exist",,,,,"SQL statement ""ALTER ROLE ""asmdb_asmschema_reader_user"" RESET ALL""
2020-09-03 07:04:37.266 UTC,"postgres","postgres",305,"10.254.33.215:54280",5f509585.131,4,"CREATE ROLE",2020-09-03 07:04:37 UTC,6/375,768,ERROR,42704,"role ""camundadb_camundaschema_reader"" does not exist",,,,,,"SET LOCAL synchronous_commit = 'local'; CREATE ROLE ""camundadb_camundaschema_writer"" NOLOGIN IN ROLE ""camundadb_camundaschema_reader"" ADMIN camundadb_camundaschema_owner ENCRYPTED PASSWORD 'md5d97cf13b68dea0fd329e6d8c3349ff0a';",,,""
2020-09-03 07:04:37.300 UTC,"postgres","postgres",306,"10.254.33.215:54282",5f509585.132,3,"DO",2020-09-03 07:04:37 UTC,6/377,0,ERROR,42704,"role ""camundadb_camundaschema_writer"" does not exist",,,,,"SQL statement ""ALTER ROLE ""camundadb_camundaschema_writer"" RESET ALL""
2020-09-03 07:04:37.695 UTC,"postgres","postgres",319,"10.254.33.215:54322",5f509585.13f,4,"CREATE ROLE",2020-09-03 07:04:37 UTC,6/403,781,ERROR,42704,"role ""camundadb_camundaschema_writer"" does not exist",,,,,,"SET LOCAL synchronous_commit = 'local'; CREATE ROLE ""camundadb_camundaschema_writer_user"" LOGIN IN ROLE ""camundadb_camundaschema_writer"" ADMIN camundadb_camundaschema_owner ENCRYPTED PASSWORD 'md5f200d2c1d968b97f68643ad003317198';",,,""
2020-09-03 07:04:37.733 UTC,"postgres","postgres",320,"10.254.33.215:54324",5f509585.140,3,"DO",2020-09-03 07:04:37 UTC,6/405,0,ERROR,42704,"role ""camundadb_camundaschema_writer_user"" does not exist",,,,,"SQL statement ""ALTER ROLE ""camundadb_camundaschema_writer_user"" RESET ALL""
2020-09-03 07:04:37.944 UTC,"postgres","postgres",327,"10.254.33.215:54342",5f509585.147,4,"CREATE ROLE",2020-09-03 07:04:37 UTC,6/419,788,ERROR,42704,"role ""asmdb_asmschema_writer"" does not exist",,,,,,"SET LOCAL synchronous_commit = 'local'; CREATE ROLE ""asmdb_asmschema_writer_user"" LOGIN IN ROLE ""asmdb_asmschema_writer"" ADMIN asmdb_asmschema_owner ENCRYPTED PASSWORD 'md59b5e948ebf980222191ebe9f8d13ee66';",,,""
2020-09-03 07:04:37.971 UTC,"postgres","postgres",328,"10.254.33.215:54344",5f509585.148,3,"DO",2020-09-03 07:04:37 UTC,6/421,0,ERROR,42704,"role ""asmdb_asmschema_writer_user"" does not exist",,,,,"SQL statement ""ALTER ROLE ""asmdb_asmschema_writer_user"" RESET ALL""
2020-09-03 07:04:40.460 UTC,"postgres","camundadb",375,"10.254.33.215:54474",5f509588.177,4,"CREATE SCHEMA",2020-09-03 07:04:40 UTC,6/515,0,ERROR,42501,"permission denied for database camundadb",,,,,,"SET ROLE TO ""a3s_owner""; CREATE SCHEMA IF NOT EXISTS ""a3s"" AUTHORIZATION ""a3s_a3s_owner""",,,""

Will take a few days to look into though.

1 database works? 2 fails?

@Jan-M Jan-M added the bug label Sep 7, 2020
@neelasha-09
Copy link
Contributor Author

neelasha-09 commented Sep 8, 2020 •
edited
Loading

Hi Jan,

Yes only the first input for database and schema is created.
The next inputs doesn't allow to create schema due to permission issues ( but the database is created ) as per the error logs.

Thanks

@neelasha-09
Copy link
Contributor Author

Hi,

Problem was: defer should not be used in for loops.
Link: https://stackoverflow.com/questions/45617758/defer-in-the-loop-what-will-be-better

time="2020-09-11T13:08:11Z" level=debug msg="syncing roles" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:16Z" level=debug msg="closing database connection" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:16Z" level=info msg="syncing databases" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:16Z" level=info msg="creating database \"a3db\" owner \"a3db_owner\"" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:16Z" level=info msg="creating database \"a4db\" owner \"a4db_owner\"" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:16Z" level=debug msg="closing database connection" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:16Z" level=info msg="syncing prepared databases" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:16Z" level=info msg="Opened preparedDbName: a2db" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:16Z" level=info msg="Working on preparedDbName: a2db" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:16Z" level=info msg="doing:creating database schema schemaName:\"a2schema2\" schemaOwner:\"a2db_a2schema2_owner\" dnOwner:\"a2db_owner\" databaseName:\"a2db\" statement:\"SET ROLE TO \\\"%s\\\"; CREATE SCHEMA IF NOT EXISTS \\\"%s\\\" AUTHORIZATION \\\"%s\\\"\" operation:\"create database schema\"" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=info msg="doing:creating database schema schemaName:\"a2schema1\" schemaOwner:\"a2db_a2schema1_owner\" dnOwner:\"a2db_owner\" databaseName:\"a2db\" statement:\"SET ROLE TO \\\"%s\\\"; CREATE SCHEMA IF NOT EXISTS \\\"%s\\\" AUTHORIZATION \\\"%s\\\"\" operation:\"create database schema\"" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=info msg="Opened preparedDbName: a3db" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=info msg="Working on preparedDbName: a3db" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=info msg="Opened preparedDbName: a4db" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=info msg="Working on preparedDbName: a4db" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=info msg="Opened preparedDbName: a1db" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=info msg="Working on preparedDbName: a1db" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=info msg="doing:creating database schema schemaName:\"a1schema1\" schemaOwner:\"a1db_a1schema1_owner\" dnOwner:\"a1db_owner\" databaseName:\"a1db\" statement:\"SET ROLE TO \\\"%s\\\"; CREATE SCHEMA IF NOT EXISTS \\\"%s\\\" AUTHORIZATION \\\"%s\\\"\" operation:\"create database schema\"" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=debug msg="closing database connection" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=info msg="Closed preparedDbName: a1db" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=warning msg="attempted to close an empty db connection object" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=info msg="Closed preparedDbName: a1db" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=warning msg="attempted to close an empty db connection object" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=info msg="Closed preparedDbName: a1db" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=warning msg="attempted to close an empty db connection object" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=info msg="Closed preparedDbName: a1db" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=error msg="could not sync prepared databases: could not execute create database schema: pq: permission denied for database a2db" cluster-name=kafka-fix/postgres-sebpg3 pkg=cluster
time="2020-09-11T13:08:17Z" level=info msg="cluster has been updated" cluster-name=kafka-fix/postgres-sebpg3 pkg=controller worker=3

This was referenced Sep 11, 2020
Merged
Closed
sdudoladov pushed a commit that referenced this issue Sep 22, 2020
@neelasha-09 @FxKu
Fixes #1130 (#1139)
ab95eaa 
* Fixes #1130

Co-authored-by: Felix Kunde <felix-kunde@gmx.de>
@FxKu FxKu mentioned this issue Oct 1, 2020
Closed
@dmayle
Copy link

dmayle commented Nov 13, 2020

Hi @sdudoladov , is there a release planned soon which includes this fix? I'm hitting the same problem on 1.5.0

@marcoslarsen
Copy link

Hello! I'm having this same issue. Which 1.5.0 image version should we use?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixes #1130
5 participants
@dmayle @Jan-M @FxKu @marcoslarsen @neelasha-09