Bug 599683 - wallaby-load won't load a snapshot from wallaby-dump
wallaby-load won't load a snapshot from wallaby-dump
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: wallaby (Show other bugs)
All Linux
medium Severity medium
: 1.3
: ---
Assigned To: Will Benton
Lubos Trilety
Depends On:
  Show dependency treegraph
Reported: 2010-06-03 14:30 EDT by Robert Rati
Modified: 2010-10-20 07:32 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Wallaby DB (78.25 KB, application/octet-stream)
2010-06-03 14:30 EDT, Robert Rati
no flags Details

  None (edit)
Description Robert Rati 2010-06-03 14:30:54 EDT
Created attachment 419475 [details]
Wallaby DB

Description of problem:
When executing wallaby-load <file>:
Console Connection Established...
Creating node 'redhat-7b6379dc'
/usr/lib/ruby/site_ruby/1.8/qmf.rb:554:in `method_missing': undefined method `MakeUnprovisioned' for #<Qmf::ConsoleObject:0x2aaab829bc78> (NoMethodError)
	from /usr/lib/ruby/site_ruby/1.8/mrg/grid/config-client.rb:46:in `send'
	from /usr/lib/ruby/site_ruby/1.8/mrg/grid/config-client.rb:46:in `method_missing'
	from /usr/lib/ruby/site_ruby/1.8/mrg/grid/config-proxies.rb:203:in `create_nodes'
	from /usr/lib/ruby/site_ruby/1.8/mrg/grid/config-proxies.rb:200:in `each'
	from /usr/lib/ruby/site_ruby/1.8/mrg/grid/config-proxies.rb:200:in `create_nodes'
	from /usr/lib/ruby/site_ruby/1.8/mrg/grid/config-proxies.rb:192:in `create_entities'
	from /usr/lib/ruby/site_ruby/1.8/mrg/grid/config-proxies.rb:186:in `load'
	from /usr/bin/wallaby-load:122

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. wallaby-load temp.dump
Actual results:
Above error

Expected results:
Successful DB load

Additional info:
Comment 1 Will Benton 2010-06-03 17:46:09 EDT
This was a lingering API reform issue that (surprisingly) slipped through the cracks.  It's fixed upstream now, and will be in the next (post-0.3.5-2) ruby-wallaby package.
Comment 2 Lubos Trilety 2010-07-20 08:21:25 EDT
Tested with (version):

Tested on:
RHEL5 x86_64  - passed
RHEL5 i386    - passed


Note You need to log in before you can comment on or make changes to this bug.