KIINGOFKEBAB opened a new issue, #28125:
URL: https://github.com/apache/superset/issues/28125
### Bug description
After days of trying to install superset on windows server I decided to
create this issue.
The problem I'm having is at step 4 of installing superset on kubernetes
documentation when I'm suppose to run the command helm upgrade --install
--values my-values.yaml superset superset/superset
I downloaded the values template and changed only the secret_key line and I
also changed the command little bit because my company have a self-sign
certificate and I used to have problem for downloading this with npm/pip. So
here's my command
helm upgrade --install --values my-values.yaml superset superset/superset
--insecure-skip-tls-verify --debug --timeout 10m0s
with the --debug parameter that's what I have
history.go:56: [debug] getting history for release superset
upgrade.go:155: [debug] preparing upgrade for superset
upgrade.go:163: [debug] performing update for superset
upgrade.go:356: [debug] creating upgraded release for superset
client.go:393: [debug] checking 16 resources for changes
client.go:684: [debug] Looks like there are no changes for ServiceAccount
"superset-redis"
client.go:684: [debug] Looks like there are no changes for Secret
"superset-postgresql"
client.go:693: [debug] Patch Secret "superset-env" in namespace default
client.go:693: [debug] Patch Secret "superset-config" in namespace default
client.go:684: [debug] Looks like there are no changes for ConfigMap
"superset-redis-configuration"
client.go:684: [debug] Looks like there are no changes for ConfigMap
"superset-redis-health"
client.go:684: [debug] Looks like there are no changes for ConfigMap
"superset-redis-scripts"
client.go:684: [debug] Looks like there are no changes for Service
"superset-postgresql-hl"
client.go:693: [debug] Patch Service "superset-postgresql" in namespace
default
client.go:684: [debug] Looks like there are no changes for Service
"superset-redis-headless"
client.go:693: [debug] Patch Service "superset-redis-master" in namespace
default
client.go:684: [debug] Looks like there are no changes for Service "superset"
client.go:693: [debug] Patch Deployment "superset-worker" in namespace
default
client.go:693: [debug] Patch Deployment "superset" in namespace default
client.go:693: [debug] Patch StatefulSet "superset-postgresql" in namespace
default
client.go:693: [debug] Patch StatefulSet "superset-redis-master" in
namespace default
client.go:486: [debug] Starting delete for "superset-init-db" Job
wait.go:66: [debug] beginning wait for 1 resources to be deleted with
timeout of 10m0s
client.go:142: [debug] creating 1 resource(s)
client.go:712: [debug] Watching for changes to Job superset-init-db with
timeout of 10m0s
client.go:740: [debug] Add/Modify event for superset-init-db: ADDED
client.go:779: [debug] superset-init-db: Jobs active: 0, jobs failed: 0,
jobs succeeded: 0
client.go:740: [debug] Add/Modify event for superset-init-db: MODIFIED
client.go:779: [debug] superset-init-db: Jobs active: 1, jobs failed: 0,
jobs succeeded: 0
upgrade.go:468: [debug] warning: Upgrade "superset" failed: post-upgrade
hooks failed: 1 error occurred:
* timed out waiting for the condition
Error: UPGRADE FAILED: post-upgrade hooks failed: 1 error occurred:
* timed out waiting for the condition
helm.go:84: [debug] post-upgrade hooks failed: 1 error occurred:
* timed out waiting for the condition
UPGRADE FAILED
main.newUpgradeCmd.func2
helm.sh/helm/v3/cmd/helm/upgrade.go:229
github.com/spf13/cobra.(*Command).execute
github.com/spf13/cobra@v1.8.0/command.go:983
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/cobra@v1.8.0/command.go:1115
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/cobra@v1.8.0/command.go:1039
main.main
helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
runtime/proc.go:267
runtime.goexit
runtime/asm_amd64.s:1650
I saw that people had the same probleme because of a recognized bug
depending of the version of apache superset but I could not find a solution to
the problem
Can someone help ?
And also is Apache Superset more stable on linux and I should ask my company
for a Ubuntu server instead of windows server ?
Thank you
### How to reproduce the bug
1. working on Windows Server 2019
2. installing docker version 4.11.1 with chocolatey(newer version isn't
compatible)
3. install kubernetes with minikube with chocolatey
4. install kubectl with chocolatey
5. install helm with chocolatey
6. follow apache superset official documentation ("Installing on kubernetes")
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [X] I have searched Superset docs and Slack and didn't find a solution to
my problem.
- [X] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [X] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org
