Bug 1766337 - Deployment fails at step 5 - iscsid container fails to start
Summary: Deployment fails at step 5 - iscsid container fails to start
Keywords:
Status: CLOSED DUPLICATE of bug 1757845
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 16.0 (Train)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-28 18:48 UTC by Eliad Cohen
Modified: 2019-11-05 14:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 14:27:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Undercloud files and folders (12.83 MB, application/x-xz)
2019-10-28 18:48 UTC, Eliad Cohen 		no flags Details
View All

Description Eliad Cohen 2019-10-28 18:48:08 UTC 
Created attachment 1629886 [details]
Undercloud files and folders

Description of problem:
The deployment fails during step 5 with logged error [1]

Version-Release number of selected component (if applicable):
RHOS_TRUNK-16.0-RHEL-8-20191007.n.0

How reproducible:


Steps to Reproduce:
1. Deployed a hyperconverged topology 3 controllers and 3 hcicephall nodes (1 undercloud)
2.
3.

Actual results:
Fails during step 5

Expected results:
Deployment to complete successfully

Additional info:
[1] http://pastebin.test.redhat.com/809427
Comment 1 Dougal Matthews 2019-10-29 14:26:54 UTC 
Moving to DFH:Storage. Found the following error in the logs:

    run failed after standard_init_linux.go:211: exec user process caused \"no such file or directory\"",

sounds like either temporary, or missing on-host volume target for a bind-mount
Comment 2 Alan Bishop 2019-11-05 14:27:00 UTC 
The messages at L221 and L311 of the pastebin indicate this BZ is a dup.

*** This bug has been marked as a duplicate of bug 1757845 ***
Note You need to log in before you can comment on or make changes to this bug.