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

   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   Primary storage plugin
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   
   ~~~
   main
   ~~~
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   
   Creating primary storage on StorPool is impossible because the URL needed is 
not valid. I checked that a few storage plugins could be affected as well 
(according to the code), like SolidFire, Nexenta and Cloudbyte (Elastisitor). 
   The issue is caused by this change [PR 
6699](https://github.com/apache/cloudstack/pull/6699/files#diff-cf68e132ad7711cfa9250cda5819c09f51cba9933aa595cd82ad5a02b4edbe64R783)
   
   I could fix it for StorPool but I think there is a need to be tested for 
those Storage drives mentioned above and to deliver a general fix.
   
   ##### 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.
   -->
   create primary storage from UI/CLI
   
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   successfully created a storage pool
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   SP_API_HTTP=10.2.23.1:81;SP_AUTH_TOKEN=4343423;SP_TEMPLATE=ssd2 is not a 
valid uri
   ~~~
   


-- 
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