You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/07/11 08:55:14 UTC

[GitHub] [superset] Rumo99 opened a new issue, #20665: Installation with Helm fails behind proxy

Rumo99 opened a new issue, #20665:
URL: https://github.com/apache/superset/issues/20665

   Installation with Helm fails behind proxy because "values don't meet the specifications of the schema".
   
   #### How to reproduce the bug
   
   1. Kubernetes cluster behind proxy
   2. Install Superset with local (pulled) Helm chart without any additional values.
   3. Installation fails
   
   ### Expected results
   
   Superset is successfully installed in the cluster.
   
   ### Actual results
   
   Installation fails.
   
   #### Screenshots
   
   This is the full error text:
   <img width="1554" alt="Screenshot 2022-07-11 105307" src="https://user-images.githubusercontent.com/33626535/178226432-6454235f-1a22-4abe-93c6-d467e2481836.png">
   
   Proxy works correctly:
   <img width="1075" alt="Screenshot 2022-07-11 104749" src="https://user-images.githubusercontent.com/33626535/178226039-e3759e48-e58c-4750-a730-bd0195e362ac.png">
   
   ### Environment
   
   - Kubernetes: 1.23.4
   - Helm: 3.7.2
   - Superset: 0.6.4
   
   ### Checklist
   
   Make sure to follow these steps be
   fore submitting your issue - thank you!
   
   - [x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
   - [x] I have reproduced the issue with at least the latest released version of superset.
   - [x] I have checked the issue tracker for the same issue and I haven't found one similar.
   
   ### Additional context
   
   To test if the dependencies (Redis and Postgres) are somehow responsible for the issue, I have tried the same with an external installation of both. The same error occurs. I couldn't yet try installation in a cluster without a proxy, because I don't have easy access to one.
   
   
   


-- 
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-unsubscribe@superset.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] Rumo99 commented on issue #20665: Installation with Helm fails behind proxy

Posted by GitBox <gi...@apache.org>.
Rumo99 commented on issue #20665:
URL: https://github.com/apache/superset/issues/20665#issuecomment-1185458162

   Thank you, this solved the issue.
   
   Since I am on Windows, I employed this solution:[https://github.com/helm/helm/issues/9576#issuecomment-817896885] (Github Helm Issue) to enforce the proxy. 
   
   Now, why all other Charts have worked so far without this additional step, and why Helm doesn't respect the general proxy settings on Windows (which is a problem with Helm, not Superset), are still open questions. But the installation was now successful.


-- 
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-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] albertopinardi commented on issue #20665: Installation with Helm fails behind proxy

Posted by GitBox <gi...@apache.org>.
albertopinardi commented on issue #20665:
URL: https://github.com/apache/superset/issues/20665#issuecomment-1182857606

   Hey, do you still have this error ? Because I think it was a temporary error threw by your local DNS Resolver while resolving `raw.githubusercontent.com`


-- 
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-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] Rumo99 closed issue #20665: Installation with Helm fails behind proxy

Posted by GitBox <gi...@apache.org>.
Rumo99 closed issue #20665: Installation with Helm fails behind proxy
URL: https://github.com/apache/superset/issues/20665


-- 
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-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] albertopinardi commented on issue #20665: Installation with Helm fails behind proxy

Posted by GitBox <gi...@apache.org>.
albertopinardi commented on issue #20665:
URL: https://github.com/apache/superset/issues/20665#issuecomment-1185356728

   Hey, I looked it up and these URLs that's Helm is failing to call are legit (it's a schema verification process on the Chart itself). So it's Helm that does not use the Proxy to fetch those files and I found [this ](https://github.com/helm/helm/issues/10065)(a bit sketchy issue) that claim that a simple `export HTTP_PROXY=some-ip:some-port` made Helm pass through the desired proxy.
   Let me know if this works.


-- 
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-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


[GitHub] [superset] Rumo99 commented on issue #20665: Installation with Helm fails behind proxy

Posted by GitBox <gi...@apache.org>.
Rumo99 commented on issue #20665:
URL: https://github.com/apache/superset/issues/20665#issuecomment-1182882887

   Hey, sadly, the error persists. In the second image ("Proxy works correctly:"), I use wget to call and get the same address as in the error message and it works. So my assumption was, that there must be some other error. Or, conversely, that "helm install" or some other aspect of the installation doesn't respect the proxy settings. Other charts install just fine, so I am somewhat confused why this one doesn't.


-- 
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-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org