-
Notifications
You must be signed in to change notification settings - Fork 7
settings.yml: Use CentOS provided vagrant boxes #129
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
settings.yml: Use CentOS provided vagrant boxes #129
Conversation
phlogistonjohn
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems reasonable to me.
Hashicorp confirms that it was misconfiguration. Anyway I'll try to fix the CI failures with the switch to CentOS official boxes. |
eab818d to
b96a611
Compare
|
/retest all |
We don’t want any surprises while resolving dependencies for any Samba packages that may be present by default. Signed-off-by: Anoop C S <[email protected]>
Signed-off-by: Anoop C S <[email protected]>
Signed-off-by: Anoop C S <[email protected]>
We previously switched[1] from official CentOS vagrant boxes as they were not regularly updated. But the situation has improved a lot since the last year where boxes are more frequently updated. On top of all that vagrant cloud platform(HCP-Hashicorp Cloud Platform) has recently implemented rate limits for downloading boxes[2]. Given all these facts it is better to get back to official CentOS vagrant boxes. These are externally hosted on CentOS cloud(and properly redirected from HCP) allowing us to bypass the throttling seen with HCP. [1] samba-in-kubernetes@d1a8534 [2] hashicorp/vagrant#13590 Signed-off-by: Anoop C S <[email protected]>
b96a611 to
b2f6a45
Compare
|
It looks like the new images already have a newer kernel than the one we want to install and it doesn't get replaced. We should force the installation of the kernel, even if it's a downgrade. I'll try to look at this, maybe tomorrow. |
Yes, I had noticed it.
Ok, feel free to update the branch with an additional commit. |
Signed-off-by: Xavi Hernandez <[email protected]>
Thanks for the minimal change 🙂. |
We previously switched from official CentOS vagrant boxes as they were not regularly updated. But the situation has improved a lot since the last year where boxes are more frequently updated. On top of all that vagrant cloud platform(HCP-Hashicorp Cloud Platform) has recently implemented rate limits for downloading boxes. Given all these facts it is better to get back to official CentOS vagrant boxes. These are externally hosted on CentOS cloud(and properly redirected from HCP) allowing us to bypass the throttling seen with HCP.