I'm going to be taking taskotron.stg down for a bit to redeploy it on F21 hosts before beta freeze starts tomorrow.
I don't expect this will take more than a couple hours and will send out another message when everything's back up.
Tim
On Mon, 30 Mar 2015 16:02:42 -0600 Tim Flink tflink@redhat.com wrote:
I'm going to be taking taskotron.stg down for a bit to redeploy it on F21 hosts before beta freeze starts tomorrow.
I don't expect this will take more than a couple hours and will send out another message when everything's back up.
I ended up hitting a few snags in the re-deployment process and the whole thing took quite a bit longer than I was expecting.
There are still a couple of things that need to be chased down (issues with sudo on taskotron-stg01.qa and some transient network issues that may have gone away) but everything appears to be up and running for now.
If you see any issues with staging, please let me know.
Tim
On Mon, 30 Mar 2015 21:43:56 -0600 Tim Flink tflink@redhat.com wrote:
On Mon, 30 Mar 2015 16:02:42 -0600 Tim Flink tflink@redhat.com wrote:
I'm going to be taking taskotron.stg down for a bit to redeploy it on F21 hosts before beta freeze starts tomorrow.
I don't expect this will take more than a couple hours and will send out another message when everything's back up.
I ended up hitting a few snags in the re-deployment process and the whole thing took quite a bit longer than I was expecting.
There are still a couple of things that need to be chased down (issues with sudo on taskotron-stg01.qa and some transient network issues that may have gone away) but everything appears to be up and running for now.
Turns out the old taskotron-stg VM wasn't removed and the issues I was seeing last night can be explained by dueling IPs.
Everything should be working in stg now.
Tim
qa-devel@lists.fedoraproject.org