Re: Jenkins -> JIRA issue

2017-08-09 Thread Gavin McDonald 
I have updated all plugins in the UI (another 16 updates since last week alone)
and will restart all/most in progress jobs are completed.

Gav…

> On 9 Aug 2017, at 3:11 pm, Lukasz Lenart  wrote:
> 
> Thanks a lot :)
> 
> 2017-08-09 7:03 GMT+02:00 Olivier Lamy :
>> jira plugin 2.4 has an issue which is fixed in 2.4.2.
>> @infra so this means update the plugin and restart.
>> 
>> On 9 August 2017 at 14:50, Lukasz Lenart  wrote:
>> 
>>> Hi,
>>> 
>>> Do you know what's wrong? This was working recently but now it blows
>>> up on two different builds.
>>> 
>>> ERROR: Step ‘JIRA: Update relevant issues’ aborted due to exception:
>>> java.lang.ClassNotFoundException: com.atlassian.fugue.Effect
>>> at jenkins.util.AntClassLoader.findClassInComponents(
>>> AntClassLoader.java:1374)
>>> at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327)
>>> at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>>> Caused: java.lang.NoClassDefFoundError: com/atlassian/fugue/Effect
>>> at com.atlassian.httpclient.apache.httpcomponents.
>>> DefaultHttpClientFactory.doCreate(DefaultHttpClientFactory.java:68)
>>> at com.atlassian.httpclient.apache.httpcomponents.
>>> DefaultHttpClientFactory.create(DefaultHttpClientFactory.java:35)
>>> at com.atlassian.jira.rest.client.internal.async.
>>> AsynchronousHttpClientFactory.createClient(AsynchronousHttpClientFactory.
>>> java:63)
>>> at com.atlassian.jira.rest.client.internal.async.
>>> AsynchronousJiraRestClientFactory.create(AsynchronousJiraRestClientFact
>>> ory.java:35)
>>> at com.atlassian.jira.rest.client.internal.async.
>>> AsynchronousJiraRestClientFactory.createWithBasicHttpAuthentication(
>>> AsynchronousJiraRestClientFactory.java:42)
>>> at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:280)
>>> at hudson.plugins.jira.JiraSite.getSession(JiraSite.java:255)
>>> at hudson.plugins.jira.Updater.perform(Updater.java:95)
>>> at hudson.plugins.jira.JiraIssueUpdater.perform(JiraIssueUpdater.java:64)
>>> at hudson.tasks.BuildStepCompatibilityLayer.perform(
>>> BuildStepCompatibilityLayer.java:81)
>>> at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
>>> at hudson.model.AbstractBuild$AbstractBuildExecution.
>>> perform(AbstractBuild.java:735)
>>> at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(
>>> AbstractBuild.java:676)
>>> at hudson.model.Build$BuildExecution.post2(Build.java:186)
>>> at hudson.model.AbstractBuild$AbstractBuildExecution.post(
>>> AbstractBuild.java:621)
>>> at hudson.model.Run.execute(Run.java:1760)
>>> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>>> at hudson.model.ResourceController.execute(ResourceController.java:97)
>>> at hudson.model.Executor.run(Executor.java:405)
>>> 
>>> 
>>> Regards
>>> --
>>> Łukasz
>>> + 48 606 323 122 http://www.lenart.org.pl/
>>> 
>> 
>> 
>> 
>> --
>> Olivier Lamy
>> http://twitter.com/olamy | http://linkedin.com/in/olamy

[Hosting] {ns1, ns2}.osuosl.org RAID firmware upgrade Aug 8, 2017 10:30AM PDT (1730 UTC)

2017-08-09 Thread Lance Albertson 
All,

I need to perform a RAID firmware upgrade on both ns1 and ns2 tomorrow at
10:30AM. This upgrade is required to resolve an issue we ran into as
described in this CentOS bug [1]. I plan to to the steps described in this
comment [2] to resolve the issue.

Here's my plan for the upgrade:

1. Bring down 140.211.166.130 on ns1 and move it to ns2
2. Disable 140.211.166.130 from coming back up on ns1 during the upgrade as
I require several reboots
3. Do the upgrade tasks as described in [2].
4. Once the fix is validated, move 140.211.166.130 back over to ns1 and
re-enable it the network config

For ns2, I'll do the same steps but moving its IP (140.211.166.131) to ns1.
This should cause minimal downtime and outages for anyone using our DNS
servers.

If you have any questions or concerns please let me know.

Also, just a friendly plug and reminder that our crowd funding campaign [3]
has 16 days left!

Thanks-

[1] https://bugs.centos.org/view.php?id=13184
[2] https://bugs.centos.org/view.php?id=13184#c29499
[3] http://osl.io/crowdfunding

-- 
Lance Albertson
Director
Oregon State University | Open Source Lab
___
Hosting mailing list
host...@osuosl.org
https://lists.osuosl.org/mailman/listinfo/hosting

[Hosting] Fwd: Planned maintenance: Internet2 circuit migration 2017-08-14 and 2017-08-15

2017-08-09 Thread Lance Albertson 
FYI

-- Forwarded message --
From: Stephen Fromm 
Date: Wed, Aug 9, 2017 at 9:45 AM
Subject: Planned maintenance: Internet2 circuit migration 2017-08-14 and
2017-08-15
To: NERO Outages List 


Internet2 will perform maintenance on the Oregon Gigapop circuits that
connect to Internet2 in Seattle and Los Angeles during two upcoming
maintenance windows.  The first window is August 14 21:00 to August 15
06:00; the second is August 15 21:00 to August 16: 06:00.  Work will be
staged one circuit at a time so as to minimize impact.

Please contact the NERO NOC if you have questions or concerns:

email: n...@nero.net
phone: 541.346.6376

--
Stephen Fromm
Network for Education and Research in Oregon
___
systems mailing list
syst...@osuosl.org
https://lists.osuosl.org/mailman/listinfo/systems




-- 
Lance Albertson
Director
Oregon State University | Open Source Lab
___
Hosting mailing list
host...@osuosl.org
https://lists.osuosl.org/mailman/listinfo/hosting

Re: [Hosting] {ns1, ns2}.osuosl.org RAID firmware upgrade Aug 10, 2017 10:30AM PDT (1730 UTC)

2017-08-09 Thread Lance Albertson 
Oops, I just realized I had the wrong date in the subject. The correct date
is August 10th at 10:30am.

On Wed, Aug 9, 2017 at 9:45 AM, Lance Albertson  wrote:

> All,
>
> I need to perform a RAID firmware upgrade on both ns1 and ns2 tomorrow at
> 10:30AM. This upgrade is required to resolve an issue we ran into as
> described in this CentOS bug [1]. I plan to to the steps described in this
> comment [2] to resolve the issue.
>
> Here's my plan for the upgrade:
>
> 1. Bring down 140.211.166.130 on ns1 and move it to ns2
> 2. Disable 140.211.166.130 from coming back up on ns1 during the upgrade
> as I require several reboots
> 3. Do the upgrade tasks as described in [2].
> 4. Once the fix is validated, move 140.211.166.130 back over to ns1 and
> re-enable it the network config
>
> For ns2, I'll do the same steps but moving its IP (140.211.166.131) to
> ns1. This should cause minimal downtime and outages for anyone using our
> DNS servers.
>
> If you have any questions or concerns please let me know.
>
> Also, just a friendly plug and reminder that our crowd funding campaign
> [3] has 16 days left!
>
> Thanks-
>
> [1] https://bugs.centos.org/view.php?id=13184
> [2] https://bugs.centos.org/view.php?id=13184#c29499
> [3] http://osl.io/crowdfunding
>
> --
> Lance Albertson
> Director
> Oregon State University | Open Source Lab
>



-- 
Lance Albertson
Director
Oregon State University | Open Source Lab
___
Hosting mailing list
host...@osuosl.org
https://lists.osuosl.org/mailman/listinfo/hosting

Re: [Hosting] Planned maintenance: Internet2 circuit migration 2017-08-14 and 2017-08-15

2017-08-09 Thread Lance Albertson 
A few of you were curious about the downtime impact. Here is the reply I
got back from our ISP:

*"The circuits are used for BGP peering with Interenet2. Traffic will shift
to other paths as the BGP peering sessions go down. We don't expect the
circuits to be down for more than a few minutes.*

*Might be a slight blip if someone had an active data transfer that
transitions to a different path across the Internet. But I don't suspect
you would see any hard outages from this event, and if you did, it would
very short (a few seconds)."*

On Wed, Aug 9, 2017 at 9:50 AM, Lance Albertson  wrote:

> FYI
>
> -- Forwarded message --
> From: Stephen Fromm 
> Date: Wed, Aug 9, 2017 at 9:45 AM
> Subject: Planned maintenance: Internet2 circuit migration 2017-08-14 and
> 2017-08-15
> To: NERO Outages List 
>
>
> Internet2 will perform maintenance on the Oregon Gigapop circuits that
> connect to Internet2 in Seattle and Los Angeles during two upcoming
> maintenance windows.  The first window is August 14 21:00 to August 15
> 06:00; the second is August 15 21:00 to August 16: 06:00.  Work will be
> staged one circuit at a time so as to minimize impact.
>
> Please contact the NERO NOC if you have questions or concerns:
>
> email: n...@nero.net
> phone: 541.346.6376
>
> --
> Stephen Fromm
> Network for Education and Research in Oregon
> ___
> systems mailing list
> syst...@osuosl.org
> https://lists.osuosl.org/mailman/listinfo/systems
>
>
>
>
> --
> Lance Albertson
> Director
> Oregon State University | Open Source Lab
>



-- 
Lance Albertson
Director
Oregon State University | Open Source Lab
___
Hosting mailing list
host...@osuosl.org
https://lists.osuosl.org/mailman/listinfo/hosting

Re: Ready for JDK 9 ?

2017-08-09 Thread Gavin McDonald 
One piece of feedback for you.

conf/security/java.security 

seems to have ‘crypto.policy=unlimited’ already turned on.

That seems backwards and imo should be set to ‘limited’ by default, especially 
considering 
this is way it has always been and also from reading the preceding text in that 
file.

I will provide our projects with both a limited and unlimited-security version 
for this b181.

HTH

Gav...

> On 9 Aug 2017, at 8:38 am, Gavin McDonald  wrote:
> 
> Hi Guys
> 
> For my part - my ‘project’ is ensuring these builds are available on the ASF 
> Build Slaves which include 75+ jenkins nodes and 20+ Buildbot nodes.
> 
> https://github.com/apache/infrastructure-puppet/blob/deployment/modules/build_slaves/manifests/jenkins.pp#L23
>  
> 
>  
> 
> currently the ‘latest’ build there is b179 installed not long ago, I will 
> make sure to get b181 on all our jenkins/buildbot nodes today.
> 
> For those of you on the builds@ mailing list, please do change or create a 
> build using this b181 and provide this list and Rory directly 
> with your feedback over the next few days.
> 
> My next mail will be me saying b181 is installed and ready to go….
> 
> Gav…
> 
>> On 8 Aug 2017, at 7:39 pm, Rory O'Donnell  wrote:
>> 
>> 
>> Hi Mark & Gavin,
>> 
>> Thank you very much for all your testing of JDK 9 during its development! 
>> Such contributions have significantly helped shape and improve JDK 9.
>> 
>> Now that we have reached the JDK 9 Final Release Candidate phase [1] , I 
>> would like to ask if your project can be considered to be 'ready for JDK 9', 
>> or if there are any remaining show stopper issues which you've encountered 
>> when testing with the JDK 9 release candidate.
>> 
>> JDK 9  b181 is available at http://jdk.java.net/9/
>> 
>> If you have a public web page, mailing list post, or even a tweet announcing 
>> you project's readiness for JDK 9, I'd love to add the URL to the upcoming 
>> JDK 9 readiness page on the Quality Outreach wiki.
>> 
>> 
>> Looking forward to hearing from you,
>> Rory
>> 
>> [1] http://openjdk.java.net/projects/jdk9/
>> 
>> -- 
>> Rgds,Rory O'Donnell
>> Quality Engineering Manager
>> Oracle EMEA , Dublin, Ireland
>> 
>

Re: Ready for JDK 9 ?

2017-08-09 Thread Gavin McDonald 
All Jenkins and Buildbot nodes should have JDK 9 b181 and JDK 9 b181 (unlimited 
security) 
installed and available.

See https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix 
 for 
the Jenkins  
locations, or use the Jenkins drop down menus in your configs.

For buildbot, they should be located in 
/home/buildslave/slave/tools/java/jdk-9-b181 etc

HTH

Gav…


> On 9 Aug 2017, at 8:38 am, Gavin McDonald  wrote:
> 
> Hi Guys
> 
> For my part - my ‘project’ is ensuring these builds are available on the ASF 
> Build Slaves which include 75+ jenkins nodes and 20+ Buildbot nodes.
> 
> https://github.com/apache/infrastructure-puppet/blob/deployment/modules/build_slaves/manifests/jenkins.pp#L23
>  
> 
>  
> 
> currently the ‘latest’ build there is b179 installed not long ago, I will 
> make sure to get b181 on all our jenkins/buildbot nodes today.
> 
> For those of you on the builds@ mailing list, please do change or create a 
> build using this b181 and provide this list and Rory directly 
> with your feedback over the next few days.
> 
> My next mail will be me saying b181 is installed and ready to go….
> 
> Gav…
> 
>> On 8 Aug 2017, at 7:39 pm, Rory O'Donnell  wrote:
>> 
>> 
>> Hi Mark & Gavin,
>> 
>> Thank you very much for all your testing of JDK 9 during its development! 
>> Such contributions have significantly helped shape and improve JDK 9.
>> 
>> Now that we have reached the JDK 9 Final Release Candidate phase [1] , I 
>> would like to ask if your project can be considered to be 'ready for JDK 9', 
>> or if there are any remaining show stopper issues which you've encountered 
>> when testing with the JDK 9 release candidate.
>> 
>> JDK 9  b181 is available at http://jdk.java.net/9/
>> 
>> If you have a public web page, mailing list post, or even a tweet announcing 
>> you project's readiness for JDK 9, I'd love to add the URL to the upcoming 
>> JDK 9 readiness page on the Quality Outreach wiki.
>> 
>> 
>> Looking forward to hearing from you,
>> Rory
>> 
>> [1] http://openjdk.java.net/projects/jdk9/
>> 
>> -- 
>> Rgds,Rory O'Donnell
>> Quality Engineering Manager
>> Oracle EMEA , Dublin, Ireland
>> 
>