So the target 1.3 means - we will focus on that and try to get it into 1.3 I guess. Okay.

Dominic Cleal wrote:

Regression from 1.2 I think.

Thank you Dominic for raising the importance of this bug.
Maybe it's a 'fog' regression from 1.2?

Find this one searching for Katello nighly bugs:
https://github.com/Katello/katello/issues/2936

Probably a regression due to us improving the power state support, maybe the vSphere provider doesn't expose the same methods.

I'm getting this too and happy to test when fixes available. I'm running against the katello-foreman repo though, so may be behind your efforts?

Applied patch(es) manually. Error is gone, but I only get 1 vGuest reporting back out of 232. Possibly my configuration?

The patch works and i'm able to connect to our Vsphere infrastructure but I still can't see all the deployed vm's. I noticed that all the vms which are located in a 'vmware directory' are not visible.
Maybe it's another bug?

The folders issue is tracked in #2093, possibly that's what's causing Duncan's issue too.

Yes - the server I'm listing is the only one not in a folder. Great. Will wait the resolution of #2093

Actually, is there any way of poking #2093 up the priority list a bit? I've commented on it, but it looks unloved for a while. I've not worked on a site where VM folders are not used in some way, so this is a bigger issue than perhaps perceived at present.

If you can complete the attached patch and submit it, we can get it included in a future release. There's more information available on the website on getting started in the project (-dev IRC and mailing lists are also useful resources).