February 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1179) build-artifacts failure for ovirt-engine-nodejs
by Greg Sheremeta (oVirt JIRA) 21 Feb '17

21 Feb '17

Greg Sheremeta created OVIRT-1179: ------------------------------------- Summary: build-artifacts failure for ovirt-engine-nodejs Key: OVIRT-1179 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1179 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra Hey, It builds fine locally in mock_runner, and works in koji (brew). http://jenkins.ovirt.org/job/ovirt-engine-nodejs_master_build-artifacts-fc2… 15:44:23 make[1]: execvp: printf: Argument list too long 15:44:23 deps/openssl/openssl.target.mk:860: recipe for target '/home/jenkins/workspace/ovirt-engine-nodejs_master_build-artifacts-fc25-x86_64/ovirt-engine-nodejs/rpmbuild/BUILD/node-v6.9.4/out/Release/obj.target/deps/openssl/libopenssl.a' failed https://gerrit.ovirt.org/#/c/72375/ -- Juan tried messing with the ulimit, but it didn't seem to help. The comments in the patch might help. It also failed for the on-demand job. Thanks, Greg -- Greg Sheremeta, MBA Red Hat, Inc. Sr. Software Engineer gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1178) create ovirt-engine-phantomjs project
by Greg Sheremeta (oVirt JIRA) 21 Feb '17

21 Feb '17

Greg Sheremeta created OVIRT-1178: ------------------------------------- Summary: create ovirt-engine-phantomjs project Key: OVIRT-1178 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1178 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra Hi, Please create a ovirt-engine-phantomjs project in gerrit. It does not need to mirror to github. It will use standard CI. Thanks, Greg -- Greg Sheremeta, MBA Red Hat, Inc. Sr. Software Engineer gshereme(a)redhat.com -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

Fwd: ** PROBLEM Service Alert: ovirt-mirrorchecker/www.gtlib.gatech.edu/pub/oVirt/pub mirror site last sync is WARNING **
by Nadav Goldin 21 Feb '17

21 Feb '17

Hi, The oVirt mirror site seems to be out of sync, could you please take a look? Thanks, Nadav. ---------- Forwarded message ---------- From: icinga <icinga(a)monitoring.ovirt.org> Date: Tue, Feb 21, 2017 at 11:10 PM Subject: ** PROBLEM Service Alert: ovirt-mirrorchecker/www.gtlib.gatech.edu/pub/oVirt/pub mirror site last sync is WARNING ** To: ngoldin(a)redhat.com ***** Icinga ***** Notification Type: PROBLEM Service: www.gtlib.gatech.edu/pub/oVirt/pub mirror site last sync Host: ovirt-mirrorchecker Address: 66.187.230.105 State: WARNING Date/Time: Tue Feb 21 21:10:32 UTC 2017 Additional Info: WARNING - 237804 seconds since last sync, which are 66.0567 hours.

1 0

[JIRA] (OVIRT-1177) Please add emarcian@redhat.com to jenkins whitelist
by rgolan (oVirt JIRA) 21 Feb '17

21 Feb '17

rgolan created OVIRT-1177: ----------------------------- Summary: Please add emarcian(a)redhat.com to jenkins whitelist Key: OVIRT-1177 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1177 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: rgolan Assignee: infra Hi Infra, please add emarcian(a)redhat.com to jenkins whitelist Thanks, Roy -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1170) add option to disable networking (or have it off by default)
by Greg Sheremeta (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1170?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-1170: --------------------------------------- Nod, I'll test it. > add option to disable networking (or have it off by default) > ------------------------------------------------------------ > > Key: OVIRT-1170 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1170 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Greg Sheremeta > Assignee: infra > > Add option to disable networking (or have it off by default). Basically, we want to prevent a job from accessing the internet if we want repeatable builds and/or are doing a downstream build somewhere else. Other/downstream build environments often have networking off. Copr has an option: (See: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.… ) > In particular, the ovirt-engine-nodejs-modules build-artifacts job *tries* to stay offline, but an evil node module called 'phantomjs' connects to the internet in a post-offline-install hook. I'd like the option to disallow that and have the build fail. -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Michal Skrivanek (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Michal Skrivanek commented on OVIRT-1154: ----------------------------------------- Hmm, I suppose CR+1 from a maintainer is a good idea anyway. Though I'm not sure whther the actual list of maintainers is truly up to date and easy to get....but if it is it does sound good enough if the previously mentioned method of git log is not feasible > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Barak Korren (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1154: ------------------------------------- We can use other things - maybe a +1 from a maintainer? > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Michal Skrivanek (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Michal Skrivanek commented on OVIRT-1154: ----------------------------------------- if you by "confirm" mean something like those "ci build" comments then please no. I never remember what's the right abracadabra magic word....it just sucks > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1170) add option to disable networking (or have it off by default)
by Barak Korren (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1170?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1170: ------------------------------------- Oh sorry that should have been: {code} rm /etc/resolv.conf {code} Or perhaps more safely: {code} truncate /etc/resolv.conf {code} This should be safe enough, and will block anything that does not use direct IP addresses to access outside resources. > add option to disable networking (or have it off by default) > ------------------------------------------------------------ > > Key: OVIRT-1170 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1170 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Greg Sheremeta > Assignee: infra > > Add option to disable networking (or have it off by default). Basically, we want to prevent a job from accessing the internet if we want repeatable builds and/or are doing a downstream build somewhere else. Other/downstream build environments often have networking off. Copr has an option: (See: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.… ) > In particular, the ovirt-engine-nodejs-modules build-artifacts job *tries* to stay offline, but an evil node module called 'phantomjs' connects to the internet in a post-offline-install hook. I'd like the option to disallow that and have the build fail. -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Barak Korren (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1154: -------------------------------- Summary: Improve and automate the jenkins-whitelist mechanism (was: Improve and automate the jenkins-whitelist mecahnism) > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0