Skip to content
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

Failed to initialize SingleNode Config DB on esx #1936

Closed
ashahi1 opened this issue Oct 13, 2017 · 2 comments
Closed

Failed to initialize SingleNode Config DB on esx #1936

ashahi1 opened this issue Oct 13, 2017 · 2 comments

Comments

@ashahi1
Copy link
Contributor

ashahi1 commented Oct 13, 2017

CI run: https://ci.vmware.run/vmware/docker-volume-vsphere/1666

2017/10/13 00:27:29 Initializing the SingleNode Config DB on esx [192.168.31.19] 
2017/10/13 00:27:29 Creating volume [restart_test_volume_931106] on VM [192.168.31.163]
2017/10/13 00:27:38 Adding create access for vmgroup _DEFAULT, datastore 'vsandatastore' on esx [192.168.31.19] 

----------------------------------------------------------------------
FAIL: restart_test.go:44: RestartTestData.SetUpSuite

restart_test.go:73:
    c.Assert(err, IsNil, Commentf(out))
... value *exec.ExitError = &exec.ExitError{ProcessState:(*os.ProcessState)(0xc420336900), Stderr:[]uint8(nil)} ("exit status 1")
... Configuration not found. Please init configuration with 'esxcli storage guestvol config init'.

2017/10/13 00:27:39 Removing container [restart_test_container_299385 restart_test_container_420764 restart_test_container_1080449] on VM [192.168.31.163]
2017/10/13 00:27:39 Destroying volume [restart_test_volume_931106]
2017/10/13 00:27:41 Removing access for 'vsandatastore' from vmgroup _DEFAULT

----------------------------------------------------------------------
FAIL: restart_test.go:82: RestartTestData.TearDownSuite

restart_test.go:93:
    c.Assert(err, IsNil, Commentf(out))
... value *exec.ExitError = &exec.ExitError{ProcessState:(*os.ProcessState)(0xc4203781a0), Stderr:[]uint8(nil)} ("exit status 1")
... Configuration not found. Please init configuration with 'esxcli storage guestvol config init'.
@shuklanirdesh82
Copy link
Contributor

@govint Please adjust the Estimate after your investigation.

@govint
Copy link
Contributor

govint commented Oct 24, 2017

The build seems to have succeeded (was it restarted?) in any case its not shown up since the time this issue was reported. Lets see if it gets a repro and debug that via a new issue. Am closing this one as not reproduced.

@govint govint closed this as completed Oct 24, 2017
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Projects
None yet
Development

No branches or pull requests

3 participants