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

CI test is failing due to error: dpkg status database is locked by another process #887

Closed
shaominchen opened this issue Feb 3, 2017 · 5 comments

Comments

@shaominchen
Copy link
Contributor

CI test is failing due to error: dpkg status database is locked by another process. Both Mark and I have run into this issue:

https://ci.vmware.run/vmware/docker-volume-vsphere/1063
https://ci.vmware.run/vmware/docker-volume-vsphere/1065

@msterin @shuklanirdesh82 @kerneltime

@ashahi1
Copy link
Contributor

ashahi1 commented Feb 8, 2017

Hit this issue durin CI run: https://ci.vmware.run/vmware/docker-volume-vsphere/1095

===================================
Snippet from error log:

=> Deploying [email protected] : deb Wed Feb 8 23:11:59 UTC 2017

dpkg: error: dpkg status database is locked by another process
make[1]: *** [deploy-vm] Error 2
make: *** [deploy-vm] Error 2

=> Build + Test not successful Wed Feb 8 23:12:00 UTC 2017

@ashahi1
Copy link
Contributor

ashahi1 commented Feb 9, 2017

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

=====
=> Deploying [email protected] : deb Thu Feb 9 00:30:49 UTC 2017

dpkg: error: dpkg status database is locked by another process
make[1]: *** [deploy-vm] Error 2
make: *** [deploy-vm] Error 2

@ashahi1
Copy link
Contributor

ashahi1 commented Feb 9, 2017

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

==========
=> Deploying [email protected] : deb Thu Feb 9 00:46:08 UTC 2017

dpkg: error: dpkg status database is locked by another process
make[1]: *** [deploy-vm] Error 2
make: *** [deploy-vm] Error 2

=> Build + Test not successful

@shuklanirdesh82
Copy link
Contributor

shuklanirdesh82 commented Feb 9, 2017

Looking at it, just a quick note (192.168.31.85 & 192.168.31.83 only are having the issue).

@pdhamdhere pdhamdhere added this to the 0.12 milestone Feb 9, 2017
@shuklanirdesh82
Copy link
Contributor

@shaominchen @ashahi1 : I've fixed both VMs and made sure by running multiple times. Please reopen if observes again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants