Adam Winberg

  • Email:
  • Registered on: 11/25/2011
  • Last connection: 12/05/2017

Projects

Activity

Reported issues: 21

12/05/2017

03:10 PM Foreman Bug #19623: Changes to vmware vm gives 'Could not find network X on VMWare compute resource'
This is closed and you reference it in the release notes for 1.16 as a fixed bug, but you do not ship a sufficiently ...

11/21/2017

07:29 AM Foreman Bug #19990: Failed to update a compute vmware (VMware) instance node.test.domain: undefined metho...
Im not using hammer, but the workaround I use when using the API is to first do a GET to get the nodes 'vm_compute_at...

07/17/2017

07:41 AM Foreman Bug #19623: Changes to vmware vm gives 'Could not find network X on VMWare compute resource'
As far as I can tell, you need the fix on the fog-vsphere side as well, which is put into 1.11.1:
https://github.com...

07/11/2017

01:07 PM Foreman Bug #20229: Virtual interface detection from facts not working unless there is an underscore in i...
Marek Hulán wrote:
> could you please paste output of facter? it might be that the way fact names are based on ident...

07/06/2017

08:05 AM Foreman Bug #20229 (New): Virtual interface detection from facts not working unless there is an underscor...
I have a server with a number of virtual interfaces, eth0:0-eth0:16. All these are detected fine in Foreman as virtua...

06/22/2017

06:02 AM Foreman Bug #19623: Changes to vmware vm gives 'Could not find network X on VMWare compute resource'
Created PR for the change in Foreman code:
https://github.com/theforeman/foreman/pull/4611

06/02/2017

03:06 AM Foreman Bug #19623: Changes to vmware vm gives 'Could not find network X on VMWare compute resource'
After a lot of debugging and digging I have finally found a way to make this work the way I need it to. Basically I w...

05/31/2017

04:41 AM Foreman Bug #19623: Changes to vmware vm gives 'Could not find network X on VMWare compute resource'
After doing some crude debugging in the 'select_nic' function in app/models/concerns/fog_extensions/vsphere/server.rb...

05/24/2017

04:05 AM Foreman Bug #19623: Changes to vmware vm gives 'Could not find network X on VMWare compute resource'
Ok, talked to VMware and according to them it is perfectly normal that a portgroup has different values in these attr...

05/23/2017

03:39 AM Foreman Bug #19623: Changes to vmware vm gives 'Could not find network X on VMWare compute resource'
Apparently there is a third portgroup attribute in vmware that may be of relevance - 'Id'. This matches the value dis...

Also available in: Atom