You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've updated the operator to the version, containing commit 7ff25c0
and was expecting that update op archive job will have new updated script, but turns out script same as was before the update.
I've localized that init script is not set directly in the job, but is set in the config map, which is not being recreated it seems.
kubectl get cm op-archive-yt-scheduler-init-job-config -oyaml | grep -A10 init-cluster.sh
init-cluster.sh: |2-
set -e
set -x
export YT_DRIVER_CONFIG_PATH=/config/client.yson
/usr/bin/init_operation_archive --force --latest --proxy http-proxies.xxx.svc.cluster.local
/usr/bin/yt set //sys/cluster_nodes/@config '{"%true" = {job_agent={enable_job_reporter=%true}}}'
kind: ConfigMap
metadata:
creationTimestamp: "2023-11-09T18:44:06Z"```
The text was updated successfully, but these errors were encountered:
I've updated the operator to the version, containing commit 7ff25c0
and was expecting that update op archive job will have new updated script, but turns out script same as was before the update.
I've localized that init script is not set directly in the job, but is set in the config map, which is not being recreated it seems.
The text was updated successfully, but these errors were encountered: