Bug 1112169
Summary: | Kickstart provisioning is on a loop when using compute profiles | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Martin Korbel <mkorbel> |
Component: | Provisioning | Assignee: | Dmitri Dolguikh <ddolguik> |
Status: | CLOSED ERRATA | QA Contact: | Martin Korbel <mkorbel> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.0.3 | CC: | achan, bbuckingham, cwelton, dcleal, djuran, jhutar, jmontleo, mmccune, ohadlevy, xdmoon |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://projects.theforeman.org/issues/4375 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Users experienced a loop when provisioning a virtual machine on oVirt/RHEV Compute Resources where the virtual machine will repeatedly kickstart and never finish. This was caused by a logic error in Foreman and is now fixed. Provisioning no longer loops when using oVirt/RHEV Compute Resources.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-11-13 22:28:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1139277 |
Description
Martin Korbel
2014-06-23 09:22:41 UTC
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. But I saw Jason mentioning this bug also with libvirt. Does this mean this is investigated and doco only? (In reply to Lukas Zapletal from comment #6) > But I saw Jason mentioning this bug also with libvirt. Does this mean this > is investigated and doco only? Not sure what you're referring to, but I can't see how this could be triggered under libvirt, nor why it would be a docs issue. Upstream bug assigned to ddolguik Moving to POST since upstream bug http://projects.theforeman.org/issues/4375 has been closed *** Bug 1146570 has been marked as a duplicate of this bug. *** Verified in Satellite-6.0.4-RHEL-7-20141107.0 * candlepin-0.9.23.1-1.el7.noarch * candlepin-common-1.0.1-1.el7.noarch * candlepin-guice-3.0-2_redhat_1.el7.noarch * candlepin-scl-1-5.el7.noarch * candlepin-scl-quartz-2.1.5-6.el7.noarch * candlepin-scl-rhino-1.7R3-3.el7.noarch * candlepin-scl-runtime-1-5.el7.noarch * candlepin-selinux-0.9.23.1-1.el7.noarch * candlepin-tomcat-0.9.23.1-1.el7.noarch * elasticsearch-0.90.10-6.el7sat.noarch * foreman-1.6.0.49-1.el7sat.noarch * foreman-compute-1.6.0.49-1.el7sat.noarch * foreman-gce-1.6.0.49-1.el7sat.noarch * foreman-libvirt-1.6.0.49-1.el7sat.noarch * foreman-ovirt-1.6.0.49-1.el7sat.noarch * foreman-postgresql-1.6.0.49-1.el7sat.noarch * foreman-proxy-1.6.0.30-1.el7sat.noarch * foreman-selinux-1.6.0.15-1.el7sat.noarch * foreman-vmware-1.6.0.49-1.el7sat.noarch * katello-1.5.0-30.el7sat.noarch * katello-certs-tools-1.5.6-1.el7sat.noarch * katello-default-ca-1.0-1.noarch * katello-installer-0.0.64-1.el7sat.noarch * katello-server-ca-1.0-1.noarch * openldap-2.4.39-3.el7.x86_64 * pulp-admin-client-2.4.3-1.el7sat.noarch * pulp-katello-0.3-4.el7sat.noarch * pulp-nodes-common-2.4.3-0.1.beta.el7sat.noarch * pulp-nodes-parent-2.4.3-0.1.beta.el7sat.noarch * pulp-puppet-plugins-2.4.3-1.el7sat.noarch * pulp-puppet-tools-2.4.3-1.el7sat.noarch * pulp-rpm-admin-extensions-2.4.3-1.el7sat.noarch * pulp-rpm-plugins-2.4.3-1.el7sat.noarch * pulp-selinux-2.4.3-1.el7sat.noarch * pulp-server-2.4.3-1.el7sat.noarch * python-ldap-2.4.6-6.el7.x86_64 * ruby193-rubygem-net-ldap-0.3.1-3.el7sat.noarch * ruby193-rubygem-runcible-1.1.0-2.el7sat.noarch * rubygem-hammer_cli-0.1.1-12.el7sat.noarch * rubygem-hammer_cli_foreman-0.1.1-16.el7sat.noarch * rubygem-hammer_cli_foreman_tasks-0.0.3-3.el7sat.noarch * rubygem-hammer_cli_import-0.10.4-1.3.el7sat.noarch * rubygem-hammer_cli_katello-0.0.4-14.el7sat.noarch * sssd-ldap-1.12.0-2.el7.x86_64 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-2014:1857 |