Xen Orchestra proxies - Test Feedback


  • Admin

    Note: XO proxies will be available in public beta very soon.

    This thread is dedicated to feedback and bug report from users participating in the tests.

    Thank you to all the testers!



  • Fallen at the first hurdle. 😞

    Proxies > Deploy a proxy. Selected storage repository. I see the VM appear in the list, then the VM starts. Then the VM gets deleted, and the "Deploy a proxy" button stays yellow.

    Tried it on two machines. One in a pool, one not.


  • XCP-ng Team

    Ping @julien-f


  • XO Team

    Hi @markhewitt1978,

    Thank you for your report.

    The deployed VM is deleted when an error occurs during the deployment.

    Please check settings/logs and post the error linked to the deployment.

    Thank you 🙂



  • Thanks. Unfortunately the error isn't so helpful

    proxy.deploy
    {
      "sr": "5bf47c46-7287-c8cd-4bd8-39df70228ee1"
    }
    {
      "message": "operation timed out",
      "name": "TimeoutError",
      "stack": "TimeoutError: operation timed out
        at Promise.call (/usr/local/lib/node_modules/xo-server/node_modules/promise-toolbox/timeout.js:13:16)
        at Proxy.deployProxy (/usr/local/lib/node_modules/xo-server/src/xo-mixins/proxies.js:193:19)
        at <anonymous>"
    }
    

  • XCP-ng Team

    Thanks for the feedback, it's helpful 🙂


  • XO Team

    Thank you for your response.

    Apparently, the VM is unable to get an IP address. Have you any network configuration which can conflicts with the start of a new VM?



  • @badrAZ said in Xen Orchestra proxies - Test Feedback:

    Thank you for your response.

    Apparently, the VM is unable to get an IP address. Have you any network configuration which can conflicts with the start of a new VM?

    The xcp-ng server is on a public IP but all my VMs are on a private network through NIC1. I would never expect to start a VM and have networking auto configured. I would have to give it an IP address.


  • XO Team

    Indeed, in your case you need to give the VM an IP address.

    To make this possible, we'll improve our solution to let users be able to select the VM's network and to choose the network configuration.



  • @badrAZ said in Xen Orchestra proxies - Test Feedback:

    Indeed, in your case you need to give the VM an IP address.

    To make this possible, we'll improve our solution to let users be able to select the VM's network and to choose the network configuration.

    Sounds good. I'll give it another go then!


  • XO Team

    Unfortunately, it will not be possible to give an IP address to the deployed VM during the deployment process because the VM is started quickly.


  • XCP-ng Team

    So we'll need to leave the choice before actual proxy deploy (eg when you select the SR) 🙂


  • XO Team

    Indeed,

    On selecting a SR, the user should be able to select the associated network and to choose its configuration.



  • I just tried this out for the first time. With XOA (latest channel, freshly updated), I received the same timeout error --

    proxy.deploy
    {
      "sr": "fed313ad-68ac-8ce8-0ced-25f861c3c17f"
    }
    {
      "message": "operation timed out",
      "name": "TimeoutError",
      "stack": "TimeoutError: operation timed out
        at Promise.call (/usr/local/lib/node_modules/xo-server/node_modules/promise-toolbox/timeout.js:13:16)
        at Proxy.deployProxy (/usr/local/lib/node_modules/xo-server/src/xo-mixins/proxies.js:195:19)
        at <anonymous>"
    }
    

    With XO built from source, I received the following error --

    proxy.deploy
    {
      "sr": "fed313ad-68ac-8ce8-0ced-25f861c3c17f"
    }
    {
      "message": "app.getResourceCatalog is not a function",
      "name": "TypeError",
      "stack": "TypeError: app.getResourceCatalog is not a function
        at Proxy.apply (/opt/xen-orchestra/packages/xo-server/src/xo-mixins/proxies.js:143:19)
        at Proxy.<anonymous> (/opt/xen-orchestra/node_modules/golike-defer/src/index.js:57:17)
        at Object.deployProxy (/opt/xen-orchestra/node_modules/lodash/_createBind.js:23:15)
        at Object.call (/opt/xen-orchestra/packages/xo-server/src/api/proxy.js:100:15)
        at Api.callApiMethod (/opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:292:33)
        at <anonymous>"
    }
    

  • XCP-ng Team

    Ping @julien-f



  • Hi,

    No problem for me to create and configure a proxy but when I start a backup I have this error :

    backupNg.runJob
    {
      "id": "fad774b1-79ac-485d-9e7d-f3f9de02f486",
      "schedule": "0c9fffd2-8a42-4d87-8098-217dbd2feabc"
    }
    {
      "code": -32601,
      "data": "backup.run",
      "message": "method not found: backup.run"
    } 
    

  • XCP-ng Team

    Your proxy was deployed in a DHCP enabled env, right?



  • @olivierlambert

    Yes the DHCP server give an IP to the proxy


  • XCP-ng Team

    Good thanks 🙂 I think we got a patch coming very soon, done by @julien-f fixing this error



  • Okay, thanks. I'm waiting for the patch.
    If I'm not in DHCP I have the same problem as the other users, a timeout and the proxy is deleted.


  • XO Team

    Hey everyone!

    The patch is finally here 🎉

    Sorry for the delay 😐

    How to test?

    1. Select the latest channel on your XO appliance
    2. Upgrade to Xen Orchestra 5.43.2
    3. Go to the Proxies page and either Deploy a proxy or upgrade the appliance of your existing ones

    What's here?

    • Full Backup
    • Disaster Recovery

    Known limitations/issues

    Scheduled for Step 2 at the end of the month.

    • Network configuration for the proxy appliance
    • Delta Backup
    • Continuous Replication
    • Detailed logs, they are currently empty
    • Restoring backups
      Work-around: create a normal remote (not linked to the proxy) connected to the same storage and import via the XO appliance

    Thank you for your feedbacks


Log in to reply
 

XCP-ng Pro Support

XCP-ng Pro Support