Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-12178

zync-db-svc initContainer on zync pod needs to have extra env vars

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • 3scale Operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      In the latest alpha build, the zync-db-svc initContainer can't execute the rake task, because it fails with the following error:

      rake aborted!
      ArgumentError: Missing `secret_key_base` for 'production' environment, set this string with `bin/rails credentials:edit` (ArgumentError)
      
              raise ArgumentError, "Missing `secret_key_base` for '#{Rails.env}' environment, set this string with `bin/rails credentials:edit`"
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      /opt/zync/vendor/bundle/ruby/3.3.0/gems/railties-7.1.6/lib/rails/application.rb:661:in `validate_secret_key_base'
      /opt/zync/vendor/bundle/ruby/3.3.0/gems/railties-7.1.6/lib/rails/application.rb:483:in `secret_key_base'
      /opt/zync/vendor/bundle/ruby/3.3.0/gems/railties-7.1.6/lib/rails/application.rb:199:in `block in message_verifiers'
      

      This is caused by upgrading to Rails 7.1, where

      {SECRET_KEY_BASE}

      is required. The request is to add SECRET_KEY_BASES environment to zync-db-svc init container on zync pod, in the same way that the zync container and zync-que pod add them - from the zync secret.

              Unassigned Unassigned
              rhn-support-dmayorov Daria Mayorova
              An Tran An Tran
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: