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

   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete 
the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   Console Proxy
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   
   ~~~
   4.19.1.2
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   Management server on Ubuntu 22.04 LTS
   KVM hypervisor on Ubuntu 22.04 LTS
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   We run a multiple cluster installation. After deleting console proxy vm, 
Cloudstack recreated a new system vm on antoher cluster.
   After that console access for instances running on a different cluster than 
the console proxy vm is running on, did not work anymore. But after stopping 
and starting an instance, console access was working again.
   
   ##### STEPS TO REPRODUCE
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal 
test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   1. detroy console proxy system vm
   2. let CS recreate the console proxy system vm and hope it will be created 
on another cluster
   3. try to open a console on an instance running on a different cluster as 
the console proxy is running on (not working)
   4. stop and start this instance and try again (working again)
   5. try to open the console on an instance running on the same cluster as the 
console proxy is running on (working)
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   console should work on all instances even after CS recreated it on another 
cluster
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   console is only working on instances running on the same cluster as the 
console proxy system vm. After stop and start of an instance, console is 
working again.
   ~~~
   


-- 
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: commits-unsubscr...@cloudstack.apache.org.apache.org

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

Reply via email to