Re: [foreman-dev] slave02.rackspace.theforeman.org is down

2017-12-28 Thread Michael Moll
Hi,

On Thu, Dec 28, 2017 at 08:28:15AM -0500, Eric D Helms wrote:
> It appears that currently slave02.rackspace.theforeman.org is currently
> down. This is affecting most repositories as the pull_request_scanner job
> that checks nearly every repositories PRs is designed to run on that
> particular slave.
> 
> I am not familiar enough with our Rackspace slave's so if anyone else from
> infra (Michael, Greg, Ewoud) gets a chance to look into its disappearance
> it would be appreciated.

That slave got reconnected again.

Regards
-- 
Michael Moll

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[foreman-dev] slave02.rackspace.theforeman.org is down

2017-12-28 Thread Eric D Helms
It appears that currently slave02.rackspace.theforeman.org is currently
down. This is affecting most repositories as the pull_request_scanner job
that checks nearly every repositories PRs is designed to run on that
particular slave.

I am not familiar enough with our Rackspace slave's so if anyone else from
infra (Michael, Greg, Ewoud) gets a chance to look into its disappearance
it would be appreciated.

-- 
Eric D. Helms
Red Hat Engineering

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [foreman-dev] Prprocessor Moved

2017-12-28 Thread Eric D Helms
Ended up with a small error in how I ran the update script for some
repositories. They should all be fixed for real now.

On Mon, Dec 25, 2017 at 12:16 PM, Tomer Brisker  wrote:

> https://github.com/theforeman/foreman/pull/5110
> https://github.com/theforeman/foreman/pull/5111
>
> On Mon, Dec 25, 2017 at 6:41 PM, Eric D Helms 
> wrote:
>
>> Can you send an example?
>>
>> On Dec 25, 2017 5:14 AM, "Tomer Brisker"  wrote:
>>
>>> Looks like the processor still isn't running on the foreman-core repo.
>>>
>>> On Sat, Dec 23, 2017 at 4:01 AM, Eric D Helms 
>>> wrote:
>>>
 Appreciate the report Tomer. Turns out the update script was
 overwriting parts of the configuration leading the errors occurring on most
 repositories. I've modified the script [1] and re-ran it to update every
 repository. The example PRs you linked appear to have been updated by the
 prproccessor as of my checking this evenings.

 Please report any further oddities!

 Cheers,
 E

 [1] https://github.com/theforeman/prprocessor/pull/77

 On Dec 22, 2017 5:32 PM, "Tomer Brisker"  wrote:

> Looks like the latest PRs didn't trigger the prprocessor:
> https://github.com/theforeman/foreman/pull/5107
> https://github.com/theforeman/foreman/pull/5108
> https://github.com/theforeman/foreman/pull/5109
>
> On Thu, Dec 21, 2017 at 3:59 PM, Eric D Helms 
> wrote:
>
>> All,
>>
>> The prprocessor has been moved off of Openshift V2 onto the same box
>> that contains our Redmine instance and now has a permanent DNS. All
>> repositories that used the prprocessor have been updated. The new site 
>> is:
>>
>> http://prprocessor.theforeman.org/status
>>
>>
>> If you encounter any issues, such as not seeing labels or theforeman
>> bot commenting on pull requests please let us know here so that we can
>> investigate.
>>
>> --
>> Eric D. Helms
>> Red Hat Engineering
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "foreman-dev" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to foreman-dev+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Have a nice day,
> Tomer Brisker
> Red Hat Engineering
>
> --
> You received this message because you are subscribed to the Google
> Groups "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
 --
 You received this message because you are subscribed to the Google
 Groups "foreman-dev" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to foreman-dev+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> --
>>> Have a nice day,
>>> Tomer Brisker
>>> Red Hat Engineering
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "foreman-dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to foreman-dev+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "foreman-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to foreman-dev+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Have a nice day,
> Tomer Brisker
> Red Hat Engineering
>
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Eric D. Helms
Red Hat Engineering

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.