Bug 1652544
| Summary: | xinetd locks the tftp port - please backport https://review.openstack.org/#/c/619500/ | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Luca Miccini <lmiccini> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Dmitry Tantsur <dtantsur> |
| Status: | CLOSED ERRATA | QA Contact: | mlammon |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 13.0 (Queens) | CC: | bfournie, dcadzow, ealcaniz, mariel, mburns |
| Target Milestone: | z4 | Keywords: | FeatureBackport, Triaged, ZStream |
| Target Release: | 13.0 (Queens) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-8.0.7-11.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
During an upgrade to a containerized deployment with Ironic, the TFTP server did not shut down correctly, which caused the upgrade to fail. This fix corrects the shutdown process of the TFTP server, so now the server can listen to the port and the upgrade completes successfully.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-01-16 17:55:25 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
Luca Miccini
2018-11-22 10:44:56 UTC
13 -p 2018-12-13.4 yum info openstack-ironic-python-agent Loaded plugins: search-disabled-repos Available Packages Name : openstack-ironic-python-agent Arch : noarch Version : 3.2.1 Release : 4.el7ost Size : 9.9 k Repo : rhelosp-13.0-puddle/x86_64 Verified code in place. If problem persists it can be re-opened or new one. /usr/share/openstack-tripleo-heat-templates/docker/services/ironic-pxe.yaml 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-2019:0068 |