The info and warning need to be debug level to avoid spamming the install log.

There is still the error:

[(OperationalError) no such table: openid_extensions u'SELECT openid_extensions.name, openid_extensions.option, openid_extensions.value \nFROM openid_extensions \nWHERE openid_extensions.name = ?' ('global',)]

ipsilon-upgrade-database needs to do the logging as well so there can be output. Logging at the error level is probably sufficient. This really needs a manpage too though that is probably out-of-scope for this work.

There is no logger defined by default. I think you need something like this:

logger = logging.getLogger()
ch = logging.StreamHandler(sys.stdout)
ch.setLevel(logging.ERROR)
logger.addHandler(ch)

Run on an existing system will spit out the error but since it doesn't raise an exception the rv is 0. At least you can see what is going on though.

One final inquiry. Should the commit message refer to upgrades or specifically db upgrades? This isn't a blocker, just a suggestion.

I reviewed the patch, ran the in-tree tests, created an IdP and tested SAML and OpenID (using the flask example) and AFAICT everything looks good.

ACK