Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto update locks will fail Chef-run #5

Open
jujugrrr opened this issue Apr 10, 2015 · 2 comments
Open

Auto update locks will fail Chef-run #5

jujugrrr opened this issue Apr 10, 2015 · 2 comments

Comments

@jujugrrr
Copy link
Contributor

I think we had some issues before where Chef runs were failing because an automatic update was already running.

By example it's 3am, yum is running an uprade, Chef-client start and cannot install a package because yum install is already run.

Maybe we can have a library which will run at the beginning of a Chef run to detect if there is already something using the package manager.

I'll try to get more details on how we were impacted before.

@jujugrrr jujugrrr changed the title Lock on on Chef-run Auto update locks will fail Chef-run Apr 10, 2015
@martinb3
Copy link
Contributor

I'd be curious to see what problems actually happened. I think the package manager already has logic to detect if another instance of it is already running.

@jujugrrr
Copy link
Contributor Author

@lmunro I thing you have more context on this. Do you remember what was the conflict?

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

No branches or pull requests

2 participants