Skip to content
This repository has been archived by the owner on Jan 16, 2024. It is now read-only.

Sometimes the CONTEXT volume is not available when vmcontext starts #7

Closed
phroton opened this issue May 8, 2015 · 3 comments
Closed

Sometimes the CONTEXT volume is not available when vmcontext starts #7

phroton opened this issue May 8, 2015 · 3 comments
Assignees
@jfontan

Comments

@phroton
Copy link

phroton commented May 8, 2015

At 2-3 of 8 newly instantiated VMs on our environment (Opennebula with StorPool Integration), the CONTEXT volume is not available when vmcontext starts.

I added a hotfix and simple logging to our environment:
phroton@0aea9c0

Could be done better, but works for us.
@jfontan jfontan self-assigned this May 14, 2015
@jfontan
Copy link
Contributor

jfontan commented May 14, 2015

This issue is related to these other ones in redmine:

We think all these problems can be fixed using the blkid method described in the last link.

jfontan added a commit that referenced this issue May 14, 2015
@jfontan
gh-7: use blkid to find the context CD
14ecc23 
Also for http://dev.opennebula.org tickets #3749 and #3365
jfontan pushed a commit that referenced this issue May 14, 2015
@Madko @jfontan
gh-7: use blkid to find the context CD
d54cad7 
Also for http://dev.opennebula.org tickets #3749 and #3365
@jfontan
Copy link
Contributor

jfontan commented May 14, 2015

I've generated a new test package. Can you check that it works for you?

https://transfer.sh/oRuHN/one-context-4.13.0.rpm

@jfontan
Copy link
Contributor

jfontan commented Jun 3, 2015

Checked that this change fixes the problem in CentOS 7

@jfontan jfontan closed this as completed Jun 3, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jfontan jfontan

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jfontan @phroton