-
Notifications
You must be signed in to change notification settings - Fork 758
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Archival does not show list of archived workflows #5624
Comments
Some more information about this issue: The call to {
"code": 3,
"message": "Cluster is not configured for reading archived visibility records."
} This error message is defined here: errClusterIsNotConfiguredForReadingArchivalVisibility = serviceerror.NewInvalidArgument("Cluster is not configured for reading archived visibility records.") https://github.com/temporalio/temporal/blob/main/service/frontend/errors.go#L62 And seems to be only used here: if !wh.archivalMetadata.GetVisibilityConfig().ReadEnabled() {
return nil, errClusterIsNotConfiguredForReadingArchivalVisibility
} https://github.com/temporalio/temporal/blob/main/service/frontend/workflow_handler.go#L2131 It looks like ultimately the value of func ArchivalMetadataProvider(dc *dynamicconfig.Collection, cfg *config.Config) archiver.ArchivalMetadata {
return archiver.NewArchivalMetadata(
dc,
cfg.Archival.History.State,
cfg.Archival.History.EnableRead,
cfg.Archival.Visibility.State,
cfg.Archival.Visibility.EnableRead,
&cfg.NamespaceDefaults.Archival,
)
} https://github.com/temporalio/temporal/blob/main/common/resource/fx.go#L350 However, I can see from the temporal-frontend Pod's logs that it's loading config/docker.yaml:
And if I shell into the container, I can see the config file does have the correct configuration:
So why is temporal-frontend acting like this is not configured? |
Expected Behavior
Viewing the Archival tab for a namespace which has archived workflows should display them.
Actual Behavior
The Archival tab is displaying the message "No Workflows running in this Namespace" even though there are archived workflows present in the configured archival S3 bucket. The GET call to
api/v1/namespaces/<namespace>/archived-workflows?query=
is failing with an HTTP 400.Steps to Reproduce the Problem
api/v1/namespaces/<namespace>/archived-workflows?query=
.Specifications
The text was updated successfully, but these errors were encountered: