An error occurred while fetching databases: {"allow_cvas":["Field may not be null."]}

After migrating to 1.2.0-rc1, editing Databases configuration rasies this error

Migration path was : 0.38 -> 1.1.0 -> 1.2.0-rc1

I’m not sure if it was working in 1.1.0, and it’s pretty hard to reproduce the situation.

An error occurred while fetching databases: {"allow_cvas":["Field may not be null."]}

For instance when unticking or ticking “allow data upload”, which has nothing to do with CVAS

Expected results

No error raised, databse configuration updated

Actual results

Configuration unchanged, aforementioned “Toast” error appears when saving

Screenshots

Two examples : click edit on an existing DB, go in this tab and click ‘save’ button :

How to reproduce the bug

1. Go to ‘Databases’
2. Click on ‘Edit’ then “Advanced”
3. Scroll down and click ‘Save’
4. See error

Environment

Running in docker

• superset version: superset version

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Superset 1.2.0
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

• python version: python --version

Python 3.7.9

• node.js version: node -v -> no node in runtime PATH, node 14 used in docker build process

Checklist

Make sure to follow these steps before submitting your issue - thank you!

• I have checked the superset logs for python stacktraces and included it here as text if there are any.
• I have reproduced the issue with at least the latest released version of superset.
• I have checked the issue tracker for the same issue and I haven’t found one similar.

Additional context

Add any other context about the problem here.

[squalou]

Possible workaround

In configuration / SQL Lab :

• tick “Allow CREATE VIEW AS”
• fill in an existing schema
• SAVE
• then remove the schema, untick
• SAVE again

I suspect it’s a migration issue somewhere, a missing field for some reason.

[eschutho]

Thanks @junlincc. cc @yousoph. Do you think this is a large enough bug to block the 1.2 release? We plan to do a bug bash tomorrow, so we’ll fit this in.