XO 4.0



  • From this poing of view there is version misconfiguration of modules

    Here it is, but it looks like doesn't provide many information 😞

    root@xoa:~# journalctl -u xoa-updater.service
    -- Logs begin at Fri 2015-06-05 14:40:19 CEST, end at Fri 2015-06-05 14:55:16 CEST. --
    Jun 05 14:40:33 xoa xoa-updater[1172]: Server listening on 9001
    Jun 05 14:46:45 xoa xoa-updater[1172]: [55B blob data]
    Jun 05 14:46:45 xoa xoa-updater[1172]: All up to date

    More detailed:
    Jun 5 13:59:31 xoa xoa-updater[2312]: xo-server#015 xo-server <E2><9C><94>
    Jun 5 13:59:35 xoa xo-server[2133]: Fri, 05 Jun 2015 11:59:35 GMT xo:api acl.getCurrent(...)
    Jun 5 13:59:35 xoa xo-server[2133]: Fri, 05 Jun 2015 11:59:35 GMT xo:api acl.getCurrent(...) <E2><86><92> object
    Jun 5 13:59:45 xoa xoa-updater[2312]: xo-server-auth-ldap-enterprise#015 xo-server-auth-ldap-enterprise
    <E2><9C><94>
    Jun 5 13:59:45 xoa xoa-updater[2312]: xo-server will be restarted...
    Jun 5 13:59:45 xoa systemd[1]: Stopping XO Server...
    Jun 5 13:59:45 xoa systemd[1]: Starting XO Server...
    Jun 5 13:59:45 xoa systemd[1]: Started XO Server.
    Jun 5 13:59:45 xoa xoa-updater[2312]: Restarting xo-server <E2><9C><94>
    Jun 5 13:59:45 xoa xoa-updater[2312]: Could not notify client: not opened
    Jun 5 13:59:45 xoa xoa-updater[2312]: Your XOA has been successfully upgraded.
    Jun 5 13:59:45 xoa xoa-updater[2312]: Could not notify client: not opened
    Jun 5 13:59:46 xoa xo-server[2832]: Fri, 05 Jun 2015 11:59:46 GMT xo:main Configuration loaded.
    Jun 5 13:59:46 xoa xo-server[2832]: <E2><9C><96> Cannot read property 'http' of undefined
    Jun 5 13:59:46 xoa xo-server[2832]: TypeError: Cannot read property 'http' of undefined
    Jun 5 13:59:46 xoa xo-server[2832]: at main$ (/source/index.js:391:27)
    Jun 5 13:59:46 xoa xo-server[2832]: at tryCatch (/usr/local/lib/node_modules/xo-server/node_modules/babel-runtime/regenerator/runtime.js:67:40)
    Jun 5 13:59:46 xoa xo-server[2832]: at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/local/lib/node_modules/xo-server/node_modules/babel-runtime/regenerator/runtime.js:294:22)
    Jun 5 13:59:46 xoa xo-server[2832]: at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/usr/local/lib/node_modules/xo-server/node_modules/babel-runtime/regenerator/runtime.js💯21)
    Jun 5 13:59:46 xoa xo-server[2832]: at invoke (/usr/local/lib/node_modules/xo-server/node_modules/babel-runtime/regenerator/runtime.js:136:37)



  • That's probably because it displays only the latest data. You can add more with --since yesterday for example.



  • Can you give me what's previously displayed before?



  • Output is the same, as I said applaince was imported two hours ago.

    root@xoa:~# journalctl -u xoa-updater.service --since yesterday
    -- Logs begin at Fri 2015-06-05 14:40:19 CEST, end at Fri 2015-06-05 15:17:01 CEST. --
    Jun 05 14:40:33 xoa xoa-updater[1172]: Server listening on 9001
    Jun 05 14:46:45 xoa xoa-updater[1172]: [55B blob data]
    Jun 05 14:46:45 xoa xoa-updater[1172]: All up to date



  • There's some stuff missing. If xo-server has failed, we should see it why during the upgrade process.



  • Only I've seen is that it hasn't refresh its status, can you try to reproduce the same error I believe it would be easy 🙂
    Maybe there is 2 steps od upgrade:

    1. upgrade to 4.0.1 (reboot)
    2. upgrade to 4.0.2 than reboot again...

    Dubravko



  • We'll release a bundled dependencies version in few hours. Hang on!



  • Okay, our tests were really interesting. We detected the problematic external package (fibers), and we are removing it from our code. Expect a new release soon (next week) with all your problems solved (and more!)



  • Until then, I can give you a package to test directly on your side



  • Yes, will be happy to test it 🙂

    Dubravko



  • Just sent you a chat message 🙂



  • Ok, I see 4.0.3 is out, and XO works again 🙂

    Dubravko



  • 😉 4.1 will come this week with some changes in ACLs, plus a safer upgrade system to avoid the bug you encounter.



  • Part of ISO images and xentools now looks good and works 🙂

    Dubravko



  • Great 🙂

    4.1 will also hide non-authorized VDI (ISO or disks)


Log in to reply