root@opennebula:~# onehost show 0
[one.host.info] Error getting host [0].
Could you send us the DB, or at least the output of “select * from host_pool” executed in the DB?
output.txt (46.0 KB)
P.S. I try new clean install 5.2 and upgrade to 5.4. Same problem.
P.S.S I use Ubuntu 16.04, 17.04.
Hello tinova,
Any news about problem?
Thanks!
The problem seems to be in the XML of the host, which lacks HOST_SHARE information.
Could you send us:
- your original DB (we cannot reproduce the problem so far)
- ‘gem list’ of your front-end
opennebula.sql (323.4 KB)
root@ubuntu:~# gem list
*** LOCAL GEMS ***
addressable (2.4.0)
amazon-ec2 (0.9.17)
aws-sdk (2.5.10)
aws-sdk-core (2.5.10)
aws-sdk-resources (2.5.10)
azure (0.7.6)
azure-core (0.1.4)
bigdecimal (1.2.8)
blankslate (3.1.3)
builder (3.2.2)
bundler (1.15.2)
configparser (0.1.4)
curb (0.9.3)
daemons (1.1.9)
did_you_mean (1.0.0)
eventmachine (1.0.7)
faraday (0.9.2)
faraday_middleware (0.10.0)
hashie (3.4.4)
inflection (1.0.0)
io-console (0.4.5)
jmespath (1.3.1)
json (2.0.1, 1.8.3)
memcache-client (1.8.5)
mime-types (2.99.2)
minitest (5.10.2)
multipart-post (2.0.0)
mysql (2.9.1)
mysql2 (0.4.5)
net-ldap (0.12.1)
net-telnet (0.1.1)
nokogiri (1.6.8.1)
ox (2.4.4)
parse-cron (0.1.4)
pg (0.18.4)
pkg-config (1.2.3)
polyglot (0.3.5)
power_assert (0.2.7)
psych (2.1.0)
rack (1.6.4)
rack-protection (1.5.3)
rake (12.0.0)
rdoc (4.2.1)
ruby-termios (1.0.0)
scrub_rb (1.0.1)
sequel (4.37.0)
sequel_pg (1.6.16)
sinatra (1.4.7)
sqlite3 (1.3.13)
systemu (2.6.5)
test-unit (3.1.7)
thin (1.6.3)
thor (0.19.1)
tilt (2.0.1)
treetop (1.6.8)
trollop (2.1.2)
uuidtools (2.1.5)
xml-simple (1.1.5)
zendesk_api (1.13.4)
root@ubuntu:~# ^C
Thanks for the info.
We would need the original 5.2 DB. If it was a clean install, then we cannot reproduce the problem, we suggest starting over.
We did the upgrade process with the provided VM and everything went smooth.
This is the HOST SHARES of the host after the upgrade:
<HOST_SHARE>
<DISK_USAGE>0</DISK_USAGE>
<MEM_USAGE>174587904</MEM_USAGE>
<CPU_USAGE>7600</CPU_USAGE>
<MAX_DISK>0</MAX_DISK>
<MAX_MEM>486491584</MAX_MEM>
<MAX_CPU>16000</MAX_CPU>
<FREE_DISK>0</FREE_DISK>
<FREE_MEM>446977024</FREE_MEM>
<FREE_CPU>4656</FREE_CPU>
<USED_DISK>0</USED_DISK>
<USED_MEM>39514552</USED_MEM>
<USED_CPU>1343</USED_CPU>
<RUNNING_VMS>22</RUNNING_VMS>
<PCI_DEVICES/>
<TOTAL_CPU>6000</TOTAL_CPU>
<TOTAL_MEM>486491584</TOTAL_MEM>
</HOST_SHARE>
Yours were missing TOTAL CPU and MEM, but cannot reproduce the problem with your DB.
I try update 3 times and get this problem. Now I try one more and record video.
Hello,
Send video to PM.
Thanks for the video.
From what we see, the migration tool has been run after the onedb upgrade, this is clearly stated in the documentation:
"The migration tool must be run before a onedb upgrade command is executed.
Please stick to the documentation, you know what they say 
months of trial an error can save precious minutes of reading the documentation
Ok, I try. I write about doc. Manual is confused. You can add numbers for steps.
Update:
Now all works fine. Sorry for spent your time.