Created attachment 954467 [details] image creation fails Description of problem: Associating image to Openstack CR fails undefined method `downcase' for nil:NilClass Version-Release number of selected component (if applicable): # rpm -qa | grep foreman ruby193-rubygem-foreman-redhat_access-0.0.4-2.el7sat.noarch foreman-vmware-1.6.0.47-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-3.el7sat.noarch ruby193-rubygem-foreman_bootdisk-2.0.6-1.1.el7sat.noarch foreman-1.6.0.47-1.el7sat.noarch foreman-compute-1.6.0.47-1.el7sat.noarch foreman-proxy-1.6.0.30-1.el7sat.noarch ruby193-rubygem-foreman_hooks-0.3.5-2.el7sat.noarch foreman-gce-1.6.0.47-1.el7sat.noarch ruby193-rubygem-foreman_discovery-1.3.0-2.el7sat.noarch rubygem-hammer_cli_foreman-0.1.1-16.el7sat.noarch qe-sat6-rhel7.usersys.redhat.com-foreman-client-1.0-1.noarch foreman-postgresql-1.6.0.47-1.el7sat.noarch qe-sat6-rhel7.usersys.redhat.com-foreman-proxy-1.0-1.noarch foreman-selinux-1.6.0.15-1.el7sat.noarch foreman-libvirt-1.6.0.47-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.9-1.1.el7sat.noarch foreman-ovirt-1.6.0.47-1.el7sat.noarch How reproducible: everytime Steps to Reproduce: 1.Create Openstack compute resource 2.Navigate to Images tab on OS resource and click "new image" 3.undefined method `downcase' for nil:NilClass Actual results: Able to create new image Expected results: undefined method `downcase' for nil:NilClass Additional info: Added screen shot
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Please attach foreman-debug, preferably if you can enable debugging first before reproducing the issue: http://projects.theforeman.org/projects/foreman/wiki/Troubleshooting#How-do-I-enable-debugging
Created redmine issue http://projects.theforeman.org/issues/8302 from this bug
The issue here is specifically in the internal openstack there are images without names (causing errors when trying to sort by name) id="9f66e623-4c44-4874-a2ea-a375dc6cadd4", name=nil, created_at="2014-10-24T01:16:18Z", updated_at="2014-10-24T01:16:18Z", progress=25, status="SAVING", id="3c018863-ed63-45f7-af15-870840905836", name=nil, created_at="2014-10-23T03:48:18Z", updated_at="2014-10-23T03:48:18Z", progress=25, status="SAVING", This seems possible only when it's in a SAVING state. We should probably only be display ACTIVE openstack images anyway.
Created attachment 954562 [details] foreman-debug
Foreman debug attached . please check
Moving to POST since upstream bug http://projects.theforeman.org/issues/8302 has been closed ------------- Anonymous Applied in changeset commit:36bbbfdf332b8977bdec182f07f60ca12fa9025a.
*** This bug is verified in upstream. This fix should eventually land in future downstream builds *** RHEL65 / RHEL7 Version Tested: foreman-proxy-1.8.0-0.develop.201411121327gitab6edc2.el7.noarch yttrium.idmqe.lab.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-gce-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-selinux-1.8.0-0.develop.201410280941git10de1c5.el7.noarch foreman-vmware-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-release-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman_discovery-1.4.0-2.el7.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410git163c264.git.0.988ca80.el7.noarch foreman-postgresql-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman_docker-0.2.0-2.el7.noarch rubygem-hammer_cli_foreman-0.1.3-1.201411121216git9381fc5.el7.noarch foreman-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-ovirt-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman-tasks-0.6.9-1.el7.noarch foreman-libvirt-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-compute-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman_bootdisk-4.0.0-1.el7.noarch yttrium.idmqe.lab.eng.bos.redhat.com-foreman-client-1.0-1.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7.noarch able to add image
This bug is slated to be released with Satellite 6.1.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:1592