Bug 1902746 - [BM][IP] Master deployment failed - Base.1.0.GeneralError: database is locked
Summary: [BM][IP] Master deployment failed - Base.1.0.GeneralError: database is locked
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.0
Assignee: Dmitry Tantsur
QA Contact: Lubov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-30 14:44 UTC by Yurii Prokulevych
Modified: 2021-02-24 15:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:36:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github metal3-io metal3-dev-env pull 578 0 None closed Bump sushy-tools to 0.13.0 2021-02-02 15:44:42 UTC
OpenStack gerrit 765333 0 None MERGED Make memoize behave better in concurrent environments 2021-02-02 15:44:42 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:36:56 UTC

Description Yurii Prokulevych 2020-11-30 14:44:08 UTC
Created attachment 1734885 [details]
sushy-tools logs

Description of problem:
-----------------------
Baremetal deploy failed during master provisioning deployment

time="2020-11-30T11:17:57Z" level=debug msg="module.masters.ironic_node_v1.openshift-master-host[1]: Still creating... [16m40s elapsed]"
time="2020-11-30T11:18:04Z" level=debug msg="module.masters.ironic_node_v1.openshift-master-host[2]: Creation complete after 16m47s [id=d79ad973-eca4-4749-a69e-daf4774ec8aa]"
time="2020-11-30T11:18:07Z" level=debug msg="module.masters.ironic_node_v1.openshift-master-host[1]: Still creating... [16m50s elapsed]"
time="2020-11-30T11:18:15Z" level=debug msg="module.masters.ironic_node_v1.openshift-master-host[1]: Creation complete after 16m57s [id=95cc5198-9d37-42a2-9efc-224356bb3de1]"
time="2020-11-30T11:18:15Z" level=error
time="2020-11-30T11:18:15Z" level=error msg="Error: could not inspect: could not inspect node, node is currently 'inspect failed', last error was 'Failed to inspect hardware. Reason: unable to start inspection: HTTP GET https://[fd2e:6f44:5dd8::1]:8000/redfish/v1/Systems/1ebb4df7-3f53-48b6-9db0-ec1e233e6b0d returned code 500. Base.1.0.GeneralError: database is locked'"
time="2020-11-30T11:18:15Z" level=error
time="2020-11-30T11:18:15Z" level=error msg="  on ../../tmp/openshift-install-042966663/masters/main.tf line 1, in resource \"ironic_node_v1\" \"openshift-master-host\":"
time="2020-11-30T11:18:15Z" level=error msg="   1: resource \"ironic_node_v1\" \"openshift-master-host\" {"
time="2020-11-30T11:18:15Z" level=error
time="2020-11-30T11:18:15Z" level=error
time="2020-11-30T11:18:15Z" level=fatal msg="failed to fetch Cluster: failed to generate asset \"Cluster\": failed to create cluster: failed to apply Terraform: failed to complete the change"


Version-Release number of selected component (if applicable):
-------------------------------------------------------------
registry.svc.ci.openshift.org/ocp/release:4.7.0-0.nightly-2020-11-29-133728


How reproducible:
-----------------
Not 100%


Steps to Reproduce:
-------------------
1. Follow BM IPI deployment procedure
2.
3.

Actual results:
---------------
Deployment failed. 1 of 3 masters failed to start


Expected results:
-----------------
Deployment succeeds


Additional info:
----------------
Virtual deployment 3masters + 2workers; provisioning and baremetal networks with IPv6

Comment 1 Dmitry Tantsur 2020-12-23 17:34:48 UTC
All patches merged.

Comment 3 Lubov 2020-12-24 15:46:35 UTC
Verified on  4.7.0-0.nightly-2020-12-21-131655

Run few attempts to deploy - the problem not reproduced

Comment 6 errata-xmlrpc 2021-02-24 15:36:33 UTC
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633


Note You need to log in before you can comment on or make changes to this bug.