Bug 1512704
| Summary: | Bulk introspection succeeds, however one node failed | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Joe Talerico <jtaleric> |
| Component: | openstack-tripleo-common | Assignee: | Dougal Matthews <dmatthew> |
| Status: | CLOSED ERRATA | QA Contact: | Alexander Chuzhoy <sasha> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 12.0 (Pike) | CC: | bfournie, jtaleric, mburns, mlammon, rhel-osp-director-maint, slinaber, srevivo |
| Target Milestone: | z2 | Keywords: | Triaged, ZStream |
| Target Release: | 12.0 (Pike) | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-common-7.6.9-2.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-03-28 17:27:14 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
Joe Talerico
2017-11-13 21:51:29 UTC
Hi Joe - is it consistently the same node that fails introspection or random? If the same, can we get console logs and/or tcpdump from this node to see if PXE boot is happening correctly? In either case, can we get ironic inspector logs and deploy logs for the failed node (if available)? Thanks. Joe - possible to get more info for this? @Bob - it was the same node. It was due to a boot order issue. However, bulk should of not succeeded... I assume it's https://bugs.launchpad.net/tripleo/+bug/1733303 Deployed latest. This included introspection and did not hit any error in our case Env verified: openstack-tripleo-common-containers-7.6.9-2.el7ost.noarch 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-2018:0607 |