Bug 1391602
| Summary: | fail: openstack baremetal import --json instackenv.json, Exception registering nodes: No valid host was found. Reason: No conductor service registered which supports driver... | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Matt Young <matyoung> |
| Component: | openstack-ironic | Assignee: | Lucas Alvares Gomes <lmartins> |
| Status: | CLOSED WORKSFORME | QA Contact: | Raviv Bar-Tal <rbartal> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 10.0 (Newton) | CC: | dtantsur, hrybacki, jkilpatr, jschluet, matyoung, mburns, rhel-osp-director-maint, rlandy, srevivo, whayutin |
| Target Milestone: | --- | Keywords: | Automation, AutomationBlocker |
| Target Release: | 10.0 (Newton) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-14 15:16: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
Matt Young
2016-11-03 15:42:57 UTC
Current details are being tracked here: - https://review.rdoproject.org/etherpad/p/rdo-internal-issues #55 When exactly did you first see this failure? We first saw the error 11/2, using an image from RDO (RDO newton + centos). Subsequent builds using RDO Newton RPM's (from hash above) atop RHEL 7.2 base also exhibited the issue. workaround for tripleo-quickstart based CI jobs has landed here: - https://github.com/redhat-openstack/ansible-role-tripleo-overcloud-prep-images/commit/0aa9d3691bab401a60dd10933136d27f18c5f761 Adding external tracker - LP#1639013 -- We are seeing this in all pipelines What's your mariadb version? the timing and mysql relationship suspiciously aligns with https://bugs.launchpad.net/tripleo/+bug/1638864 The run where we initially saw this was using: mariadb-10.1.18-1.el7 https://thirdparty-logs.rdoproject.org/jenkins-tripleo-quickstart-periodic-newton-delorean-ha_192gb-3/undercloud/var/log/extra/import-delorean-testing.txt.gz --- In other news, adding a github issue to track removal of the workaround we have in place in CI https://github.com/redhat-openstack/ansible-role-tripleo-overcloud-prep-images/issues/1 According to https://bugs.launchpad.net/tripleo/+bug/1638864, this version has problems. Could you please try mariadb-10.1.18-3? The issue does not look too related, but I'd prefer to rule out this possibility completely. RDO newton just promoted a new hash: - https://trunk.rdoproject.org/centos7-newton/8e/bb/8ebb715a52afef8c5eea6fa343a915d97910907c_13bba89f with: - https://ci.centos.org/view/rdo/view/promotion-pipeline/job/rdo-delorean-promote-newton/138/ - https://ci.centos.org/job/tripleo-quickstart-promote-newton-delorean-minimal/95/ Containing: - mariadb-10.1.18-3.el7 - https://ci.centos.org/artifacts/rdo/jenkins-tripleo-quickstart-promote-newton-delorean-minimal-95/undercloud/var/log/extra/import-delorean-testing.txt.gz The internal pipelines are running now on this hash. Both internal and ci.centos pipelines have the workaround in place. We can run a separate run without the workaround to confirm, but not until a little later today when current jobs are complete. I'll circle back with details. I've just kicked the run mentioned in comment #10 Hi! Any updates here? Did the MariaDB update fix the jobs? Yup. I did run the pipeline once with the workaround disabled and it appears to have worked and not reproduced. Before I could get a second pass, we have run into a series of other issues (some infra, some not). We've been chasing these and should ideally be back to green status today, whereupon I can layer in removal of the workaround. In a perfect world I could do this in parallel but it's not possible with current HW resources. I'll circle back tonight, or over the next few days to confirm, but before removing the workaround that is currently in place (and affecting all tripleo-quickstart jobs (ci.centos and internal)) I would like a second data point. Thanks! I'll close it for now, but please feel free to reopen. |