Greetings.
Our staging openshift is still version 3.5, and still warns/yells about nodes not having enough disk space (with 3.4 we allocated 20GB to them, but in 3.5 and later they want at least 40G).
So, I'd like to take our staging openshift down, reprovision it with more space for the nodes and also get it up to 3.7
Hopefully this won't take too long, and since we have no persistent data everything should just reprovision via ansible.
I'd like to look at doing this tomorrow.
If you are using staging openshift and would prefer some other time/date, please let me know.
Thanks,
kevin
On 02/22/2018 02:57 PM, Kevin Fenzi wrote:
Greetings.
Our staging openshift is still version 3.5, and still warns/yells about nodes not having enough disk space (with 3.4 we allocated 20GB to them, but in 3.5 and later they want at least 40G).
So, I'd like to take our staging openshift down, reprovision it with more space for the nodes and also get it up to 3.7
Hopefully this won't take too long, and since we have no persistent data everything should just reprovision via ansible.
I'd like to look at doing this tomorrow.
If you are using staging openshift and would prefer some other time/date, please let me know.
I went ahead and did this, but there's some things to still figure out... some of the apps (at least waiverdb) aren't coming up.
I'll try and investigate over the week/next week, but if any app owners want to look at their apps and see what they can find, please let me know
kevin
Excerpts from Kevin Fenzi's message of 2018-02-23 22:12 -08:00:
I went ahead and did this, but there's some things to still figure out... some of the apps (at least waiverdb) aren't coming up.
I'll try and investigate over the week/next week, but if any app owners want to look at their apps and see what they can find, please let me know
That one (Waiverdb) is our fault, sorry. We were working on deploying a new version but when it went onto stage we discovered some issues last week which we have been working through.
The most recent problem is that we are trying to use JSONB column type in Postgres but it's not supported on Postgres 9.2. Patrick has already figured this out for us and filed an issue, which we are looking at:
https://pagure.io/waiverdb/issue/134
So you can ignore the Waiverdb failures on stage, we will take care of it.
infrastructure@lists.fedoraproject.org