Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 911996[details]
firebug raises NetworkError 404 not found
Description of problem:
I was trying to create a new host, and I selected the hostgroup from dropdown. Later I unselected the hostgroup by selecting a empty row there and then Firebug raises error:
"NetworkError: 404 Not Found - https://dhcp207-190.lab.eng.pnq.redhat.com/hosts/process_hostgroup"
Version-Release number of selected component (if applicable):
sat6 beta snap10 compose3
How reproducible:
always
Steps to Reproduce:
1. create a hostgroup
2. while creating new host, select hostgroup from down and then unselect it by selecting empty row from drop down
3.
Actual results:
Expected results:
no error should be raised on selecting empty row to unselect the previous selection
Additional info:
log from production.log:
Processing by HostsController#process_hostgroup as */*
Parameters: {"utf8"=>"✓", "authenticity_token"=>"/P7i8eyaFGfuUe8/6uOXt6kv8lh8YdzzQ/U1UkONi8s=", "host"=>{"name"=>"shost", "organization_id"=>"1", "location_id"=>"2", "hostgroup_id"=>"", "compute_resource_id"=>"1", "environment_id"=>"3", "content_source_id"=>"1", "puppet_ca_proxy_id"=>"", "puppet_proxy_id"=>"", "puppetclass_ids"=>[""], "managed"=>"true", "progress_report_id"=>"[FILTERED]", "type"=>"Host::Managed", "compute_attributes"=>{"cpus"=>"1", "memory"=>"805306368", "nics_attributes"=>{"new_nics"=>{"type"=>"bridge", "_delete"=>"", "bridge"=>"eth0", "model"=>"virtio"}, "0"=>{"type"=>"bridge", "_delete"=>"", "bridge"=>"eth0", "model"=>"virtio"}}, "volumes_attributes"=>{"new_volumes"=>{"pool_name"=>"default", "capacity"=>"10G", "allocation"=>"0G", "format_type"=>"raw", "_delete"=>""}, "0"=>{"pool_name"=>"default", "capacity"=>"10G", "allocation"=>"0G", "format_type"=>"raw", "_delete"=>""}}, "start"=>"1"}, "domain_id"=>"2", "realm_id"=>"", "mac"=>"", "subnet_id"=>"1", "ip"=>"192.168.100.3", "interfaces_attributes"=>{"new_interfaces"=>{"_destroy"=>"false", "type"=>"Nic::Managed", "mac"=>"", "name"=>"", "domain_id"=>"", "ip"=>"", "provider"=>"IPMI"}}, "architecture_id"=>"1", "operatingsystem_id"=>"1", "provision_method"=>"build", "build"=>"1", "ptable_id"=>"7", "disk"=>"", "root_pass"=>"[FILTERED]", "is_owned_by"=>"1-Users", "enabled"=>"1", "comment"=>"", "overwrite"=>"false"}, "kt_environment_id"=>"ACME_Corporation/Dev", "capabilities"=>"build image", "provider"=>"Libvirt"}
Completed 404 Not Found in 32ms (ActiveRecord: 3.4ms)
Moving to POST since upstream bug http://projects.theforeman.org/issues/6376 has been closed
-------------
Shimon Shtein
Applied in changeset commit:5c7e4ed69b422e6c1e8a73362d80fb23b75b3a95.
Verified in sat6.2 snap3. Now there is no empty row. User can just unselect the selected option by clicking on 'x'. And I don't see 404 on selecting/unselecting the hostgroup from new_host form.
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/RHBA-2016:1500