Jayd603 opened a new issue, #12107:
URL: https://github.com/apache/cloudstack/issues/12107

   
   Existing templates no longer work with password reset or initial password 
set.
   
   VPC Router log
   ```Nov 19 17:46:54 systemvm passwd_server_ip.py: serve_password: password 
saved for VM IP 10.207.2.196```
   
   ok great, but then on the VM
   ```2025-11-19 17:47:23,185 - subp.py[DEBUG]: Running command ['wget', 
'--quiet', '--tries', '3', '--timeout', '20', '--output-document', '-', 
'--header', 'DomU_Request: send_my_password', '10.207.5.244:8080'] with allowed 
return codes [0] (shell=False, capture=True)
   2025-11-19 17:47:23,191 - performance.py[DEBUG]: Getting password took 0.007 
seconds
   2025-11-19 17:47:23,191 - log_util.py[DEBUG]: Failed to fetch password from 
virtual router 10.207.5.244
   ```
   
   ```
   root@pw-test:/var/log# wget --header 'DomU_Request: send_my_password' 
10.207.5.244:8080
   --2025-11-19 18:41:52--  http://10.207.5.244:8080/
   Connecting to 10.207.5.244:8080... failed: Connection refused.
   ```
   
   However: using the gateway IP works!
   ```
   wget --header 'DomU_Request: send_my_password' 10.207.0.1:8080
   ```
   
   NOTES:
   This is with a redundant VPC network with source NAT and it appears to make 
it so cloud-init cannot fetch from the router interface IPs, only the gateway 
IP of the VPC.  
   
   In the VPC router:
   ```tcp        0      0 10.207.0.1:8080         0.0.0.0:*               
LISTEN```
   
   so it is not listening on .244 at all - the iptables rules look correct 
however.
   
   ```[email protected]\x2c10.207.11.141.service                 
                loaded active running   Cloud password server```
   
   Looks like it is trying to start it with multiple addresses but it's only 
accepting the first argument.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to