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
Looks like the latest PRs didn't trigger the prprocessor:
On Thu, Dec 21, 2017 at 3:59 PM, Eric D Helms <ericdhelms@gmail.com> 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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout\.
--
Have a nice day,
Tomer Brisker
Red Hat Engineering
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" <tbrisker@redhat.com> 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/5109On Thu, Dec 21, 2017 at 3:59 PM, Eric D Helms <ericdhelms@gmail.com> > 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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
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 <eric.d.helms@gmail.com> 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" <tbrisker@redhat.com> 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/5109On Thu, Dec 21, 2017 at 3:59 PM, Eric D Helms <ericdhelms@gmail.com> >> 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+unsubscribe@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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Have a nice day,
Tomer Brisker
Red Hat Engineering
Can you send an example?
On Dec 25, 2017 5:14 AM, "Tomer Brisker" <tbrisker@redhat.com> 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 <eric.d.helms@gmail.com> > 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" <tbrisker@redhat.com> 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/5109On Thu, Dec 21, 2017 at 3:59 PM, Eric D Helms <ericdhelms@gmail.com> >>> 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+unsubscribe@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+unsubscribe@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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
https://github.com/theforeman/foreman/pull/5111
On Mon, Dec 25, 2017 at 6:41 PM, Eric D Helms <eric.d.helms@gmail.com> wrote:
Can you send an example?
On Dec 25, 2017 5:14 AM, "Tomer Brisker" <tbrisker@redhat.com> 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 <eric.d.helms@gmail.com> >> 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,
EOn Dec 22, 2017 5:32 PM, "Tomer Brisker" <tbrisker@redhat.com> wrote:
Looks like the latest PRs didn't trigger the prprocessor:
Fix a bunch of layout cops by tbrisker · Pull Request #5107 · theforeman/foreman · GitHub
fixes #22062 - support vmware vmrc console by timogoebel · Pull Request #5108 · theforeman/foreman · GitHub
Fixes #21941 - Add foreign key in migration for hostgroup validation by rabajaj0509 · Pull Request #5109 · theforeman/foreman · GitHubOn Thu, Dec 21, 2017 at 3:59 PM, Eric D Helms <ericdhelms@gmail.com> >>>> 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+unsubscribe@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+unsubscribe@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+unsubscribe@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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout\.
--
Have a nice day,
Tomer Brisker
Red Hat Engineering
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 <tbrisker@redhat.com> wrote:
https://github.com/theforeman/foreman/pull/5110
https://github.com/theforeman/foreman/pull/5111On Mon, Dec 25, 2017 at 6:41 PM, Eric D Helms <eric.d.helms@gmail.com> > wrote:
Can you send an example?
On Dec 25, 2017 5:14 AM, "Tomer Brisker" <tbrisker@redhat.com> 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 <eric.d.helms@gmail.com> >>> 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" <tbrisker@redhat.com> 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/5109On Thu, Dec 21, 2017 at 3:59 PM, Eric D Helms <ericdhelms@gmail.com> >>>>> 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+unsubscribe@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+unsubscribe@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+unsubscribe@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+unsubscribe@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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Eric D. Helms
Red Hat Engineering
Looks like there are some issues again. It did not run on the following PRs:
Can’t say if it was the same case or another, but there was an error about not being able to handle nil somewhere. https://github.com/theforeman/prprocessor/pull/81 should fix that. Currently it appears to be applying labels so I can’t say if this was a network error of some kind.
I have merged and deployed the PR mentioned. Please let us know if issues continue.