Uploaded image for project: 'A-MQ Messaging-as-a-Service'
  1. A-MQ Messaging-as-a-Service
  2. ENTMQMAAS-1180

Existing messaging users lost when upgrading from AMQ Online 1.0 to 1.1 (Ansible)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 1.1
    • None
    • None

      If I have deployed AMQ Online 1.0 with a standard authentication service with Keycloak backed with Postgres and upgrade to AMQ Online 1.1 using Ansible, the existing messaging users are lost and keycloak is reconfigured to no longer use postgres for backing. The postgres does still deployment still exists and the users unharmed - it is just no longer attached to AMQ Online.

      The issue can be worked around by adding the following to the authenticationservice standard-authservice:

          datasource:
            credentialsSecret:
              name: postgresql
            database: amqonline
            host: postgresql
            port: 5432
            type: postgresql 
      

            Unassigned Unassigned
            keithbwall Keith Wall
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: