Red Hat Bugzilla – Bug 1293978
appliance_console failed: "Could not find rake-10.4.2 in any of the sources"
Last modified: 2017-07-23 09:28:09 EDT
Description of problem:
After installing the CFME on new virtual machine, I got the below error.
Cannot run appliance console nor starting the appliance.
Version-Release number of selected component (if applicable)
100% tried with 2 different hosts
Steps to Reproduce:
1.download the latest cfme cfme-rhos-126.96.36.199-3.x86_64.qcow2
2. configure virtual machines using virsh
3. login to cloud forms VM
4. start appliance_console
failed to run appliance_console
run the appliance_console or having an alternate way to configure the appliance VMDB
[root@localhost ~]# appliance_console
/opt/rh/cfme-gemset/gems/bundler-1.11.2/lib/bundler/spec_set.rb:94:in `block in materialize': Could not find rake-10.4.2 in any of the sources (Bundler::GemNotFound)
from /opt/rh/cfme-gemset/gems/bundler-1.11.2/lib/bundler/spec_set.rb:87:in `map!'
from /opt/rh/cfme-gemset/gems/bundler-1.11.2/lib/bundler/spec_set.rb:87:in `materialize'
from /opt/rh/cfme-gemset/gems/bundler-1.11.2/lib/bundler/definition.rb:137:in `specs'
from /opt/rh/cfme-gemset/gems/bundler-1.11.2/lib/bundler/definition.rb:182:in `specs_for'
from /opt/rh/cfme-gemset/gems/bundler-1.11.2/lib/bundler/definition.rb:171:in `requested_specs'
from /opt/rh/cfme-gemset/gems/bundler-1.11.2/lib/bundler/environment.rb:18:in `requested_specs'
from /opt/rh/cfme-gemset/gems/bundler-1.11.2/lib/bundler/runtime.rb:13:in `setup'
from /opt/rh/cfme-gemset/gems/bundler-1.11.2/lib/bundler.rb:92:in `setup'
from /var/www/miq/vmdb/gems/pending/appliance_console.rb:16:in `<main>'
I can't reproduce this. Are there any additional steps you took in step 2 of your reproduction steps?
I'm using VMM on Fedora to test the qcow2 disks and can just use them directly. I'm wondering if there is some additional configuration you are doing that could be causing this issue?
This was actually an issue in the 188.8.131.52-1 build, but was subsequently fixed.
Can I either have access to the test environment where this is happening or can you double check the build version used?
I want to be sure because this would have to be an issue on all of the appliance versions if it is actually happening in 184.108.40.206-3 and I am not seeing it on any.