[
https://issues.apache.org/jira/browse/GUACAMOLE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821138#comment-16821138
]
Don commented on GUACAMOLE-777:
-------------------------------
> In the future it may be possible to improve the automation of the upgrade
> process, it just isn't something we've done, yet, and we've tried to document
> the require steps as best we can.
Fairy nuff. I get what you are saying about virgin installs but when you have
an existing install all the information you need to make your choices about
which SQL script to launch is already there. If there was not already a valid
DB connection you would not already have a valid install. I hope I am making
myself clear.
Either way I am pretty sure adding a few sanity checks inside the container
image should not be hard to do. As you can see I have already built some images
myself and I can see how just putting a few sanity checks in start.sh would go
a long way to solving this issue.
> Schema upgrade does not alter table permissions
> -----------------------------------------------
>
> Key: GUACAMOLE-777
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-777
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
> Affects Versions: 1.0.0
> Reporter: Don
> Priority: Minor
>
> When pulling a newer guacamole images from guacamole/guacamole:latest upon
> restart there is a critical DB error.
>
> {{18-Apr-2019 09:08:16.895 INFO [main]
> org.apache.catalina.startup.Catalina.start Server startup in 4397 ms}}
> {{09:09:04.896 [http-nio-8080-exec-4] ERROR o.a.g.rest.RESTExceptionMapper -
> Unexpected internal error: }}
> {{### Error querying database. Cause: org.postgresql.util.PSQLException:
> ERROR: relation "guacamole_entity" does not exist}}
> {{ Position: 571}}
> {{### The error may exist in
> org/apache/guacamole/auth/jdbc/user/UserMapper.xml}}
> {{### The error may involve defaultParameterMap}}
> {{### The error occurred while setting parameters}}
> {{### SQL: SELECT guacamole_user.user_id,
> guacamole_entity.entity_id, guacamole_entity.name,
> password_hash, password_salt, password_date,
> disabled, expired, access_window_start,
> access_window_end, valid_from, valid_until,
> timezone, full_name, email_address,
> organization, organizational_role, MAX(start_date) AS
> last_active FROM guacamole_user JOIN guacamole_entity ON
> guacamole_user.entity_id = guacamole_entity.entity_id LEFT JOIN
> guacamole_user_history ON guacamole_user_history.user_id =
> guacamole_user.user_id WHERE guacamole_entity.name = ?
> AND guacamole_entity.type = 'USER'::guacamole_entity_type
> GROUP BY guacamole_user.user_id, guacamole_entity.entity_id; SELECT
> guacamole_user_attribute.user_id,
> guacamole_user_attribute.attribute_name,
> guacamole_user_attribute.attribute_value FROM
> guacamole_user_attribute JOIN guacamole_user ON
> guacamole_user.user_id = guacamole_user_attribute.user_id JOIN
> guacamole_entity ON guacamole_user.entity_id = guacamole_entity.entity_id
> WHERE guacamole_entity.name = ? AND
> guacamole_entity.type = 'USER'::guacamole_entity_type}}
> {{### Cause: org.postgresql.util.PSQLException: ERROR: relation
> "guacamole_entity" does not exist}}
> {{ Position: 571}}
>
>
>
> There ought to be some sort of sanity check when upgrading the DB schema.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
