Proxmox VE 3.0 RC2 released!

[ebiss]

Re: 3.0 RC2 update cause WebGUI login problem ?!

I guess something cleared the cache on the squid proxy.

But why pve-api-daemon/3.0 thought it must response via squid ?
Notice the responses header "Via"

 

[ebiss]

Re: 3.0 RC2 update cause WebGUI login problem ?!

I can reproduce the WEBGUI login problem again.

export http_proxy=http://172.xxx.xxx.xxx:8888/
aptitude update && aptitude full-upgrade

Then Login https://pvehost:8006/


Solved by unset http_proxy ENV and restart pveproxy.



What commands were runned after aptitude upgrade "pve-cluster pve-manager qemu-server" ?
So I can reproduce this problem.

thanks for your patience

 

[dietmar]

Re: 3.0 RC2 update cause WebGUI login problem ?!

I can reproduce the WEBGUI login problem again.

IMHO this is simply a caching problem on the proxy. I assume it works if you clear the cache on the proxy?

 

[ebiss]

Re: 3.0 RC2 update cause WebGUI login problem ?!

IMHO this is simply a caching problem on the proxy. I assume it works if you clear the cache on the proxy?

I don't think so.
Maybe the pveproxy should ignore ENV like "http_proxy" ?


2.3 use apache never has this kind problem.

 

[dietmar]

Re: 3.0 RC2 update cause WebGUI login problem ?!

Maybe the pveproxy should ignore ENV like "http_proxy" ?

Oh, you set http_proxy on the CLI - will assemble a patch to ignore it

 

[ebiss]

Re: 3.0 RC2 update cause WebGUI login problem ?!

Oh, you set http_proxy on the CLI - will assemble a patch to ignore it

My poor english finally make you got it

 

[dietmar]

Re: 3.0 RC2 update cause WebGUI login problem ?!

Oh, you set http_proxy on the CLI - will assemble a patch to ignore it

Just uploaded a fixed version to the pve repository. Please can you test if it works now? (fixed in pve-manager 3.0-20)

 

[ebiss]

Re: 3.0 RC2 update cause WebGUI login problem ?!

Just uploaded a fixed version to the pve repository. Please can you test if it works now? (fixed in pve-manager 3.0-20)

Have tested, works. Login with no problem.
Thanks.

 

[eislon]

Re: Another unresolved bug?!

mixing is not a good idea, this should be avoided. test without joining to a 2.x cluster.

Ok thanks, then I test it and will upgrade the cluster to 3.0 when the final is tested ok!