Bug 1194269
| Summary: | Deployment will stop on systems which boots/shutdowns quickly and foreman-proxy is terminated before buffer is flushed. | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Leonid Natapov <lnatapov> |
| Component: | foreman-discovery-image | Assignee: | Mike Burns <mburns> |
| Status: | CLOSED ERRATA | QA Contact: | Alexander Chuzhoy <sasha> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0 (Juno) | CC: | aberezin, adahms, lnatapov, mburns, nyechiel, oblaut, rhos-maint, sasha, sputhenp, yeylon |
| Target Milestone: | z2 | Keywords: | ZStream |
| Target Release: | Installer | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://projects.theforeman.org/issues/8320 | ||
| Whiteboard: | |||
| Fixed In Version: | foreman-proxy-1.6.0.30-6.el7ost foreman-discovery-image-7.0-20150227.0.el7ost | Doc Type: | Known Issue |
| Doc Text: |
In some rare cases, a host may shut down foreman-proxy before completing the reboot process. This causes hosts to fail to reboot when starting a Red Hat Enterprise Linux OpenStack Platform installer deployment. As a workaround, you can manually trigger the host to reboot and, if necessary, click 'Resume' to resume the deployment, allowing the deployment to proceed without issue.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-04-07 15:08:41 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: | |||
|
Description
Leonid Natapov
2015-02-19 13:00:16 UTC
Note: bug exists in foreman-proxy, but a new foreman-discovery-image will also need to be built to include the package. Backported the patch in the referenced upstream issue. Included it in a new foreman-proxy build and rebuilt the foreman-discovery-image with this new foreman-proxy. Verified: Environment: rhel-osp-installer-client-0.5.7-1.el7ost.noarch ruby193-rubygem-foreman_discovery-1.3.0-2.3.el7ost.noarch foreman-1.6.0.49-6.el7ost.noarch foreman-postgresql-1.6.0.49-6.el7ost.noarch foreman-selinux-1.6.0.14-1.el7sat.noarch openstack-foreman-installer-3.0.17-1.el7ost.noarch rhel-osp-installer-0.5.7-1.el7ost.noarch ruby193-rubygem-foreman-tasks-0.6.9-1.1.1.el7ost.noarch ruby193-rubygem-staypuft-0.5.21-1.el7ost.noarch foreman-proxy-1.6.0.30-6.el7ost.noarch rubygem-hammer_cli_foreman-0.1.1-16.el7sat.noarch openstack-puppet-modules-2014.2.8-2.el7ost.noarch ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el7ost.noarch foreman-installer-1.6.0-0.3.RC1.el7ost.noarch foreman-discovery-image-7.0-20150227.0.el7ost.noarch rubygem-hammer_cli_foreman-doc-0.1.1-16.el7sat.no The reported issue doesn't reproduce. 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://rhn.redhat.com/errata/RHSA-2015-0791.html |