infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Takamori (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (INFRA-15790) Jenkins worker beam5 not accesible
Date Sat, 27 Jan 2018 02:16:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-15790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341906#comment-16341906
] 

Daniel Takamori edited comment on INFRA-15790 at 1/27/18 2:15 AM:
------------------------------------------------------------------

I've put puppet on it twice now, and after coming back from 10 hours of package installs the
VM seems to have reimaged itself.  Is there anything that would be causing the VM to reinstall
the OS after some check fails?
We noticed a ban from the machine on our LDAP server, so something was also happening on our
side. So I'm going to install puppet again so hopefully I can finish before some funky happens.


was (Author: pono):
I've put puppet on it twice now, and after coming back from 10 hours of package installs the
VM seems to have reimaged itself.  Is there anything that would be causing the VM to reinstall
the OS after some check fails?

> Jenkins worker beam5 not accesible
> ----------------------------------
>
>                 Key: INFRA-15790
>                 URL: https://issues.apache.org/jira/browse/INFRA-15790
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Ismaël Mejía
>            Assignee: Daniel Takamori
>            Priority: Minor
>
> I noticed that jenkins is saying that one of the machines in our project is not accesible.
> https://builds.apache.org/computer/beam5/
> Can somebody please help us to check what is going on and re-enable the access so it
can receive jobs from jenkins. Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message