Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
Jenkins ver 2.220
Description
After updating to new jenkins version, the clouds configuration page has moved.
When accessing the new config page, the "Credentials" dropddown for my existing vSphere Cloud is "none". Before the update, I had configured credentails for that cloud. Also if I open the drop-down, the list only contains "-none". Also if I click "Add" and add new Global credentials, the DropDown keeps empty.
Attachments
Issue Links
- duplicates
-
-
- Resolved
-
Activity
Guy Rawsthorn
added a comment - Hi pjdarton, thanks for the update. We are experiencing this issue where credentials are not shown in the dropdown, therefore, cannot be certain of our connection to vSphere. Is there an ETA on the next release?
Rdgs
Guy Rawsthorn
added a comment - Hi pjdarton , thanks for the update. We are experiencing this issue where credentials are not shown in the dropdown, therefore, cannot be certain of our connection to vSphere. Is there an ETA on the next release?
Rdgs 
pjdarton
added a comment - No ETA; vSphere plugin maintenance (i.e. building, testing and releasing new versions) is something I do in my "spare" time at work (and there's precious little of that at present).
There is, however, something you (or anyone else watching this) can do to speed things up:
- download the .hpi file from the URL above and install it using the "advanced" tab on the manage plugins page.
- test it
- let me know if it fixes the problem for you
If you can do that then it'll give me confidence that the fix works and is worth releasing officially, meaning I can get a release out much sooner.
If you can't help with that then you'll have to wait until I have the time to do all that myself unaided ... and that might be a while.
pjdarton
added a comment - No ETA; vSphere plugin maintenance (i.e. building, testing and releasing new versions) is something I do in my "spare" time at work (and there's precious little of that at present).
There is, however, something you (or anyone else watching this) can do to speed things up:
download the .hpi file from the URL above and install it using the "advanced" tab on the manage plugins page.
test it
let me know if it fixes the problem for you
If you can do that then it'll give me confidence that the fix works and is worth releasing officially, meaning I can get a release out much sooner.
If you can't help with that then you'll have to wait until I have the time to do all that myself unaided ... and that might be a while. 
Daniel Hoerner
added a comment - Thank you, with the downloaded hpi file the issue is solved. Guy Rawsthorn
added a comment - Can confirm the upgrade works on my system too. Successfully shows the connection state to vSphere and the availability of the template.
Guy Rawsthorn
added a comment - Can confirm the upgrade works on my system too. Successfully shows the connection state to vSphere and the availability of the template. pjdarton
added a comment - Thanks for that folks - much appreciated.
On the basis of 2 confirmed "it works" reports, I've kicked off a release; it's uploaded and should start showing up within the next few hours.
i.e. This is fixed in the 2.23 release which went out just now.
pjdarton
added a comment - Thanks for that folks - much appreciated.
On the basis of 2 confirmed "it works" reports, I've kicked off a release; it's uploaded and should start showing up within the next few hours.
i.e. This is fixed in the 2.23 release which went out just now. 
FAO anyone watching: this will be fixed in the next release.
In the meantime, anyone affected by this issue can grab an as-yet-unreleased build from https://ci.jenkins.io/job/Plugins/job/vsphere-cloud-plugin/job/master/lastSuccessfulBuild/