Hi everyone I m performing an update of the current release DataHub #all-things-deployment

Hi everyone, I'm performing an update of the curre...

elegant-article-21703

08/12/2022, 10:04 AM

Hi everyone, I'm performing an update of the current release (using v0.8.41) but, during the upgrade it fails. How can I extract extra information about the issue that might be triggering the failure? The

--debug

message extract the following:

Copy code

wait.go:225: [debug] Deployment is not ready: datahub/datahub-datahub-frontend. 0 out of 1 expected pods are ready
upgrade.go:360: [debug] warning: Upgrade "datahub" failed: timed out waiting for the condition
upgrade.go:378: [debug] Upgrade failed and atomic is set, rolling back to last successful release
history.go:53: [debug] getting history for release datahub
rollback.go:64: [debug] preparing rollback of datahub
rollback.go:112: [debug] rolling back datahub (current: v14, target: v13)
rollback.go:71: [debug] creating rolled back release for datahub

and the command I'm using is (I'm updating the root password):

Copy code

helm upgrade  -n datahub --atomic --debug  datahub  ./helm/datahub --values .\helm\datahub\charts\datahub-frontend\values.yaml

Thank you in advance!

orange-night-91387

08/15/2022, 3:49 PM

Have you checked the frontend pod logs?

elegant-article-21703

08/15/2022, 4:09 PM

When I check the logs I have the following

Copy code

10:26:33 [application-akka.actor.default-dispatcher-32724] WARN  o.e.j.j.spi.PropertyFileLoginModule - Exception starting propertyUserStore /etc/datahub/plugins/frontend/auth/user.props
10:26:33 [application-akka.actor.default-dispatcher-32724] ERROR application - The submitted callback is of type: class javax.security.auth.callback.NameCallback : javax.security.auth.callback.NameCallback@70a412cb
10:26:33 [application-akka.actor.default-dispatcher-32724] ERROR application - The submitted callback is of type: class org.eclipse.jetty.jaas.callback.ObjectCallback : org.eclipse.jetty.jaas.callback.ObjectCallback@5ae0a214
10:26:33 [application-akka.actor.default-dispatcher-32724] WARN  application - The submitted callback is unsupported!
10:26:33 [application-akka.actor.default-dispatcher-32724] ERROR application - The submitted callback is of type: class javax.security.auth.callback.PasswordCallback : javax.security.auth.callback.PasswordCallback@2b064d6b
10:26:33 [application-akka.actor.default-dispatcher-32724] ERROR application - The submitted callback is of type: class javax.security.auth.callback.NameCallback : javax.security.auth.callback.NameCallback@c1fc592
10:26:33 [application-akka.actor.default-dispatcher-32724] ERROR application - The submitted callback is of type: class org.eclipse.jetty.jaas.callback.ObjectCallback : org.eclipse.jetty.jaas.callback.ObjectCallback@5cfdbc90
10:26:33 [application-akka.actor.default-dispatcher-32724] WARN  application - The submitted callback is unsupported!
10:26:33 [application-akka.actor.default-dispatcher-32724] ERROR application - The submitted callback is of type: class javax.security.auth.callback.PasswordCallback : javax.security.auth.callback.PasswordCallback@3d25519

elegant-article-21703

08/15/2022, 4:19 PM

The problem comes when I added the extra volumes to the frontend values.yaml. When I add the following, the update crash:

Copy code

extraVolumes: 
  - name: datahub-users
    secret:
      defaultMode: 0444
      secretName: datahub-users-secret
extraVolumeMounts:
  - name: datahub-users
    mountPath: ./datahub-frontend/conf/user.props
    subPath: user.props

orange-night-91387

08/15/2022, 4:46 PM

Is that all of the logs?

Copy code

32724] WARN  o.e.j.j.spi.PropertyFileLoginModule - Exception starting propertyUserStore /etc/datahub/plugins/frontend/auth/user.props

This seems to be the main concerning one, double check that your props file is properly formatted

elegant-article-21703

08/15/2022, 5:30 PM

That was the issue. Thanks for your help Ryan!

71 Views

Open in Slack

Previous Next