Support #17173
closedUnable to start Foreman
Description
Hello,
I've got a fresh install of Foreman (1.13.1) on CentOS7, and I'm attempting to set it up with XenServer as a compute resource.
I've installed Foreman via RPM repo/foreman-installer, and installed the packages below (the most recent version of each).
$ yum list installed | grep -e "xen\|protected_attributes"
tfm-rubygem-fog-xenserver.noarch 0.2.3-1.el7 @foreman
tfm-rubygem-foreman_xen.noarch 0.3.1-1.fm1_13.el7 @foreman-plugins
tfm-rubygem-foreman_xen-doc.noarch 0.3.1-1.fm1_13.el7 @foreman-plugins
tfm-rubygem-protected_attributes.noarch 1.1.3-3.el7 @foreman
tfm-rubygem-protected_attributes-doc.noarch 1.1.3-3.el7 @foreman
After restarting the httpd process, I get this message in the browser when I try to access Foreman:
"Web application could not be started
ForemanXen::Xenserver is using attr_accessible so must either be converted to strong parameters, or add the protected_attributes gem (RuntimeError)"
In the foreman-xen README.md it says Foreman 1.13 is compatible with plugin version 0.4. Yet the most recent RPM of tfm-rubygem-foreman_xen provided by the repo seems to be 0.3.1-1.fm1_13. I'm in two minds if that is related, as despite this being 0.3, there is the fm1_13 suffix at the version number, which might imply that it's ok?
Is this a bug, or something I'm doing incorrectly?
Thanks,
Stephen
Updated by Anonymous over 8 years ago
- Status changed from New to Assigned
- Assignee set to Anonymous
Seems I forgot to do a release of the plugin in the 1.13 release cycle.
Updated by Anonymous over 8 years ago
- Status changed from Assigned to Resolved
0.4.0 is in the YUM and APT repos now.
Updated by Stephen Whittle over 8 years ago
Thank you, I've updated and can now select Xenserver as a compute resource.
Thanks,
Stephen