> Hello,
> I used foreman alone, and add the foreman-vmware plugin but i now have
> this problem :
> undefined local variable or method `spinner' for
> #<#<Class:0x007f0894f1bb40>:0x0000000a3770f8>
>
> A debug file has been created: /tmp/foreman-debug-SwScM.tar.xz (238112
> bytes)
>
> Uploading…
> The tarball has been uploaded, please contact us on our mailing list or IRC
> referencing the following URL:
>
> http://debugs.theforeman.org/foreman-debug-SwScM.tar.xz
It looks like you have a mix of Foreman packages installed from 1.9 and
1.11.
> rpm -qa 'foreman' || dpkg -l 'foreman' | sort
tfm-rubygem-hammer_cli_foreman-0.6.2-1.el7.noarch
foreman-1.11.2-1.el7.noarch
foreman-cli-1.11.2-1.el7.noarch
foreman-release-1.9.3-1.el7.noarch
foreman-selinux-1.9.3-1.el7.noarch
foreman-installer-1.9.3-1.el7.noarch
foreman-proxy-1.9.3-1.el7.noarch
ruby193-rubygem-foreman_setup-3.0.2-1.fm1_9.el7.noarch
foreman-compute-1.11.2-1.el7.noarch
foreman-postgresql-1.11.2-1.el7.noarch
foreman-vmware-1.11.2-1.el7.noarch
foreman-release-scl-1-1.el7.x86_64
foreman-debug-1.9.3-1.el7.noarch
It looks like you might have a 1.9 installation and then installed some
of 1.11 on top of it, but without upgrading everything. Unless you have
a rollback mechanism, I'd suggest trying to complete the upgrade but
using our upgrade instructions
(Foreman :: Manual) to ensure all
packages are updated.
···
On 31/05/16 13:59, Benoit Joseph wrote:–
Dominic Cleal
dominic@cleal.org