Bug #9420
closedDeleting a docker-based repo shows an error in the background but the UI shows that everything is ok
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1193651
Description of problem:
When I delete an existing, un-syced docker based repository from my custom product, the UI shows that a task was triggered to delete the repo. If I move away from that page and re-visit it, the repo is indeed gone. However I am seeing a stacktrace generated in the logs when I delete the repo and I'm not sure what to make of it.
Version-Release number of selected component (if applicable):
- apr-util-ldap-1.3.9-3.el6_0.1.x86_64
- candlepin-0.9.42-1.el6.noarch
- candlepin-common-1.0.21-1.el6.noarch
- candlepin-selinux-0.9.42-1.el6.noarch
- candlepin-tomcat6-0.9.42-1.el6.noarch
- elasticsearch-0.90.10-7.el6.noarch
- foreman-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
- foreman-compute-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
- foreman-debug-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
- foreman-gce-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
- foreman-libvirt-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
- foreman-ovirt-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
- foreman-postgresql-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
- foreman-proxy-1.8.0-0.develop.201502121459git0207401.el6.noarch
- foreman-release-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
- foreman-selinux-1.8.0-0.develop.201412151103gite2863e4.el6.noarch
- foreman-vmware-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
- katello-2.2.0-1.201502171650git5cf9de7.el6.noarch
- katello-certs-tools-2.0.1-1.el6.noarch
- katello-common-2.2.0-1.201502171650git5cf9de7.el6.noarch
- katello-default-ca-1.0-1.noarch
- katello-installer-2.2.0-1.201502160627gite8ff373.el6.noarch
- katello-installer-base-2.2.0-1.201502160627gite8ff373.el6.noarch
- katello-repos-2.1.1-1.el6.noarch
- katello-server-ca-1.0-1.noarch
- openldap-2.4.39-8.el6.x86_64
- pulp-docker-plugins-0.2.2-1.el6.noarch
- pulp-katello-0.3-3.el6.noarch
- pulp-nodes-common-2.6.0-0.7.beta.el6.noarch
- pulp-nodes-parent-2.6.0-0.7.beta.el6.noarch
- pulp-puppet-plugins-2.6.0-0.7.beta.el6.noarch
- pulp-puppet-tools-2.6.0-0.7.beta.el6.noarch
- pulp-rpm-plugins-2.6.0-0.7.beta.el6.noarch
- pulp-selinux-2.6.0-0.7.beta.el6.noarch
- pulp-server-2.6.0-0.7.beta.el6.noarch
- python-ldap-2.3.10-1.el6.x86_64
- ruby193-rubygem-ldap_fluff-0.3.3-1.el6.noarch
- ruby193-rubygem-net-ldap-0.10.0-1.el6.noarch
- ruby193-rubygem-runcible-1.3.1-1.el6.noarch
- rubygem-hammer_cli-0.1.4-1.201502121207git0ab2866.el6.noarch
- rubygem-hammer_cli_foreman-0.1.4-1.201501221305git706b057.el6.noarch
- rubygem-hammer_cli_foreman_bootdisk-0.1.2-1.el6.noarch
- rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410gitc96619d.git.0.37f3704.el6.noarch
- rubygem-hammer_cli_gutterball-0.0.1-1.201501072024git01fe139.git.0.06e884f.el6.noarch
- rubygem-hammer_cli_import-0.10.4-1.el6.noarch
- rubygem-hammer_cli_katello-0.0.7-1.201502061831git68a34d6.git.0.9c4412d.el6.noarch
- sssd-ldap-1.11.6-30.el6.x86_64
How reproducible:
Steps to Reproduce:
1. Create a custom product
2. Add a custom docker-based repo for busybox and sync it
3. Add a custom docker-based repo for fedora/ssh and delete it while watching /var/log/foreman/production.log
Actual results:
NoMethodError: undefined method `[]' for nil:NilClass shows up in the logs
Expected results:
Additional info: