Support #9374
closedForeman-xen and XenServer Pool
Description
Hi.
All seems work well. But only if XenServer is StandAlone server. If i have server pool then i cant see what VM on what XenServer run.
All VM seeem like running on PoolMaster host.
Also if i try add to Compute Resouce servers other than Poll Master i give error "Fog::XenServer::InvalidLogin"
/var/log/foreman/production.log
---
Started PUT "/compute_resources/test_connection" for 192.168.0.108 at 2015-02-13 15:18:28 +0000
Processing by ComputeResourcesController#test_connection as */*
Parameters: {"utf8"=>"✓", "authenticity_token"=>"XkEILrD5L+m7uzRhiLGfKYmHptOnHbo09m9QnxTCDuc=", "compute_resource"=>{"name"=>"vhost001.vps", "provider"=>"Xenserver", "description"=>"", "url"=>"192.168.0.7", "user"=>"root", "password"=>"[FILTERED]"}, "fakepassword"=>"[FILTERED]", "cr_id"=>"null"}
CR_ID IS null
String does not start with the prefix 'encrypted-', so ForemanXen::Xenserver vhost001.vps was not decrypted
String does not start with the prefix 'encrypted-', so ForemanXen::Xenserver vhost001.vps was not decrypted
String does not start with the prefix 'encrypted-', so ForemanXen::Xenserver vhost001.vps was not decrypted
String does not start with the prefix 'encrypted-', so ForemanXen::Xenserver vhost001.vps was not decrypted
String does not start with the prefix 'encrypted-', so ForemanXen::Xenserver vhost001.vps was not decrypted
Rendered /opt/rh/ruby193/root/usr/share/gems/gems/foreman_xen-0.0.5.1/app/views/compute_resources/form/_xenserver.html.erb (3.0ms)
Rendered compute_resources/_form.html.erb (7.0ms)
Completed 200 OK in 14ms (Views: 7.4ms | ActiveRecord: 0.5ms)
---
Files
Updated by Operations ooVoo almost 10 years ago
- File Capture.PNG Capture.PNG added
Aleksei Yamschikov where you wanna see that information? Is that ok if I will add this info under VM properties?
Updated by Operations ooVoo almost 10 years ago
For only support to connect to Master server which is single in POOL, so it is correct behavior
Updated by Operations ooVoo almost 10 years ago
- Status changed from New to Feedback
- Priority changed from Normal to Low
Updated by Operations ooVoo almost 10 years ago
- Assignee set to Aleksei Yamschikov
Updated by Sergio Mira almost 10 years ago
Same problem here!
I don't think this is a low priority issue, it's a serious one!
Any concerns about this?
Aleksei Yamschikov wrote:
Hi.
All seems work well. But only if XenServer is StandAlone server. If i have server pool then i cant see what VM on what XenServer run.
All VM seeem like running on PoolMaster host.Also if i try add to Compute Resouce servers other than Poll Master i give error "Fog::XenServer::InvalidLogin"
/var/log/foreman/production.log
---
Started PUT "/compute_resources/test_connection" for 192.168.0.108 at 2015-02-13 15:18:28 +0000
Processing by ComputeResourcesController#test_connection as */*
Parameters: {"utf8"=>"✓", "authenticity_token"=>"XkEILrD5L+m7uzRhiLGfKYmHptOnHbo09m9QnxTCDuc=", "compute_resource"=>{"name"=>"vhost001.vps", "provider"=>"Xenserver", "description"=>"", "url"=>"192.168.0.7", "user"=>"root", "password"=>"[FILTERED]"}, "fakepassword"=>"[FILTERED]", "cr_id"=>"null"}
CR_ID IS null
String does not start with the prefix 'encrypted-', so ForemanXen::Xenserver vhost001.vps was not decrypted
String does not start with the prefix 'encrypted-', so ForemanXen::Xenserver vhost001.vps was not decrypted
String does not start with the prefix 'encrypted-', so ForemanXen::Xenserver vhost001.vps was not decrypted
String does not start with the prefix 'encrypted-', so ForemanXen::Xenserver vhost001.vps was not decrypted
String does not start with the prefix 'encrypted-', so ForemanXen::Xenserver vhost001.vps was not decrypted
Rendered /opt/rh/ruby193/root/usr/share/gems/gems/foreman_xen-0.0.5.1/app/views/compute_resources/form/_xenserver.html.erb (3.0ms)
Rendered compute_resources/_form.html.erb (7.0ms)
Completed 200 OK in 14ms (Views: 7.4ms | ActiveRecord: 0.5ms)
---
Updated by Alejandro Falcon over 9 years ago
I just found a solution to this issue by applying https://github.com/fog/fog/commit/5dfaded56cbcb2676d91abbb2cb6b193a23aa36b to the fog gem code. Then change foreman_xen gem file app/models/foreman_xen/xenserver.rb line 296 to this @client ||= ::Fog::Compute.new({ :provider => 'XenServer', :xenserver_url => url, :xenserver_username => user, :xenserver_password => password, :xenserver_redirect_to_master => true } )
Hope it helps.
Updated by Anonymous over 9 years ago
- Blocked by Refactor #10997: Update fog to 1.33.0 added
Updated by Alejandro Falcon over 9 years ago
No problem.
Note: The VM consoles are still broken with my fix when the master changes. It's still trying to use the IP set in the compute resource instead.
Updated by Anonymous over 9 years ago
- Status changed from Feedback to Assigned
- Assignee changed from Aleksei Yamschikov to Anonymous
let's see where we can get this...
Updated by Operations ooVoo over 9 years ago
Guys, using fog 1.30 works good with XenServer 6.2 and 6.5 as well.
Updated by Anonymous over 9 years ago
- Assignee changed from Anonymous to Operations ooVoo
Updated by Anonymous over 9 years ago
- Status changed from Assigned to Resolved
PR got merged, foreman-xen 0.2.x will require Foreman 1.10 because of the underlying fog change.
Created #12050 for the VNC connection.