Re: Errors in CSK - cloud-controller-manager

I found this on the traffic dump 2:55:28.185209 IP 10.1.1.241.49114 > 172.20.0.207.8080: Flags [P.], seq 2450:2760, ack 5513, win 502, options [nop,nop,TS val 2432471880 ecr 9133241], length 310: HTTP: GET /client/api?apiKey=Ls_XKJRp0qrtwxdtfwO0gQy9M56A24LfBdjB-JVT2IffPsadycSB6xBhLkvH_nGeHy6yjr

Errors in CSK - cloud-controller-manager

Hi team, I’m getting this error on the cloud-controller-manager pod, E0104 15:53:17.586548 1 node_controller.go:245] Error getting node addresses for node "k1-control-17e2206df94": error fetching node by provider ID: error retrieving node addresses: CloudStack API error 401 (CSExceptionE

Errors in CSK - cloud-controller-manager

Hi team, I’m getting this error on the cloud-controller-manager pod, E0104 15:53:17.586548 1 node_controller.go:245] Error getting node addresses for node "k1-control-17e2206df94": error fetching node by provider ID: error retrieving node addresses: CloudStack API error 401 (CSExceptionErr

Re: Public IP is stucked in state "released" after usage for static nat

Hi Wei, Will have to think that through as I am not sure if I could revert back an service offering without Service User data. Also do you guess It could be sufficent to only upgrade the effected network (as the error is pointing at the network id)? Why not using userdata... Well short: not neede

Re: Connecting to CSK nodes

Thanks! It's working On 2/01/22, 11:04 PM, "Harikrishna Patnala" wrote: Hi Ricardo, Please the user "core" to login to the nodes. Like "ssh -i -p core@" Regards, Harikrishna From: Ricardo Andres Pertuz de las Salas Sent:

Re: Public IP is stucked in state "released" after usage for static nat

Hi Chris, You can try to update the network/vpc tier to an offering with Userdata and then disable static nat. May I ask why you decided not to use Userdata ? -Wei On Tue, 4 Jan 2022 at 14:35, vas...@gmx.de wrote: > As i will need to fix this - i guess somewhat during the reset of the week

Re: Public IP is stucked in state "released" after usage for static nat

As i will need to fix this - i guess somewhat during the reset of the week are there any ideas on how to "remove" this from CS? (BackUP Jobs will be started for DB and i wouldn't have the chance to perform a binarylog rollback / recovery) The "clean" way i guess would be a DB Rollback to a point p

Re: Public IP is stucked in state "released" after usage for static nat

Hi Wei, of course! :-) https://github.com/apache/cloudstack/issues/5824 Regards, Chris Am Di., 4. Jan. 2022 um 11:32 Uhr schrieb Wei ZHOU : > Hi Chris, > > This seems to be a bug. Can you file an issue on > https://github.com/apache/cloudstack/issues ? > > -Wei > > On Tue, 4 Jan 2022 at 11:16,

Re: Public IP is stucked in state "released" after usage for static nat

Hi Chris, This seems to be a bug. Can you file an issue on https://github.com/apache/cloudstack/issues ? -Wei On Tue, 4 Jan 2022 at 11:16, vas...@gmx.de wrote: > Hi Dan, > > Sorry for the misunderstanding. > The VPC was created using a "custome" service offering which is not using / > offering

Re: Public IP is stucked in state "released" after usage for static nat

Hi Dan, Sorry for the misunderstanding. The VPC was created using a "custome" service offering which is not using / offering "service user data" . The same goes for the NW-Offering which is used for creation of the tiers. There is no service user data in this VPC. The default / out-of-the-box VPC

Re: Public IP is stucked in state "released" after usage for static nat

Chris, it looks to me like you should delete the VPC and then check if all IPs are available before creating a new one. As for the user data service, the message already says that user data is not supported, so why create another offering? On Tue, Jan 4, 2022 at 2:50 AM vas...@gmx.de wrote: > h