[GitHub] [cloudstack] rajujith opened a new issue, #7771: Failed to deploy SystemVM resources are not removed from Tungsten Fabric

["rajujith (via GitHub)" <gi...@apache.org>]

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

   <!--
   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.
   -->
   ~~~
   Tungsten Fabric, SystemVMs
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main branch.
   -->
   
   ~~~
   4.18.0
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, advanced networking, etc.  N/A otherwise
   -->
   CloudStack advanced zone with Tungsten Fabric integration. 
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   
   If the systemVMs fails to get deployed due to any reason the resources such as IP addresses and corresponding objects created by CloudStack at the Tungsten Fabric are not deleted when the SystemVMs are deleted from CloudStack. This results in subsequent deployment failure with the error `Failure message: IP address already in use`. 
   
   
   ##### 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. Create a zone with Tungsten Fabric isolation. 
   2. Skip enabling the Tungsten Fabric plugin in the global settings: `tungsten.plugin.enable`
   3. SystemVMs fail to deploy.
   4. Enable the plugin above and restart cloudstack-management service.
   5. Delete the existing SystemVMs
   6. New SystemVMs fail to deploy with the error `Failure message: IP address already in use`. 
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   CloudStack should remove the failed-to-deploy SystemVMs IP addresses from Tungsten Fabric.
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   CloudStack is not removing the failed-to-deploy SystemVMs IP addresses from Tungsten Fabric.
   ~~~
   
   ##### WORKAROUND
   ~~~
   Disable the zone
   Delete the existing SystemVMs
   
   Login to the Tungsten controller and click on configure. 
   Networking -> ports.
   
   Select all and delete all. 
   ~~~
   
   
   


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

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