19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
dagster-de
dagster-cube
gigs-freelance
dagster-wandb
dagster-machine-learning
dagster-bigquery
tools
dagster-dask
dagster-snowflake
dagster-releases
data-platform-design
events
dagster-serverless
dagster-noteable
introductions
dagster-airflow
dagster-cloud
random
dagster-dbt
faq-read-me-before-posting
dagster-airbyte
dagster-spatial
dagster-support
announcements
github-discussions
豆瓣酱帮
dagster-feedback
dagstereo
dagster-ecs
dagster-kubernetes
jobs
dagster-showcase
Title
t
Tomakhina Olha
03/27/2023, 9:53 AMHi!
When deploying dagster with helm in kuber, we have an issue which happened on Thursday and everything worked before
dagster._core.errors.DagsterInvalidConfigError: Errors whilst loading configuration for {'postgres_url': Field(<dagster._config.source.StringSourceType object at 0x7f9695861bd0>, default=@, is_required=False), 'postgres_db': Field(<dagster._config.field_utils.Shape object at 0x7f96713d6260>, default=@, is_required=False), 'should_autocreate_tables': Field(<dagster._config.config_type.Bool object at 0x7f96957e85b0>, default=True, is_required=False)}.
Error 1: Post processing at path root:postgres_db:password of original value {'env': 'DAGSTER_PG_PASSWORD'} failed:
dagster._config.errors.PostProcessingError: You have attempted to fetch the environment variable "DAGSTER_PG_PASSWORD" which is not set. In order for this execution to succeed it must be set in this environment.:dagster-bot-resolve: 1
j
johann
03/27/2023, 5:04 PMWhich pod did this occur in?
The
DAGSTER_PG_PASSWORDenv:
- name: DAGSTER_PG_PASSWORD
valueFrom:
secretKeyRef:
name: {{ include "dagster.postgresql.secretName" . | quote }}
key: postgresql-passwordMaybe
• jenkins created the pod in a different namespace that doesn’t have the secret? I think that would error on pod creation about a missing secret though
• The value of the secret is empty now?
t
Tomakhina Olha
03/27/2023, 7:54 PMThank you very much for your answers! Looking what is the problem. Will be back with the result later.
It seems the problem is in dagster daemon. Because user code and de[ployment is OK, I can run a job from launchpad, the problem is only with
• schedule - it is not run when schedule is and the error I’ve sent above is raised at that moment
• in dagit I don’t see any logs for any op. But pipeline runs well and gives the result I expect.
(((
@johann thank you for your answer. really there was an update of dagster and after this behaviour was changed. and yes, adding the DAGSTER_PG_PASSWORD to secrets helped.
Maybe you can suggest why after the update I don’t see logs in dagit at all?
j
johann
03/28/2023, 1:02 PMThere was an accidental ui change that is hiding logs by default, it will be fixed in the release tomorrow
You can still see them using the new levels drop-down
t
Tomakhina Olha
03/28/2023, 1:31 PMNice, thanks.