July 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2353) remove system-sync_mirrors-glusterfs-4.1-testing-el7-x86 job

by Ehud Yonasi (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2353?page=com.atlassian.jir... ] Ehud Yonasi reassigned OVIRT-2353: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > remove system-sync_mirrors-glusterfs-4.1-testing-el7-x86 job > ------------------------------------------------------------ > > Key: OVIRT-2353 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2353 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Ehud Yonasi > > this job is failing and Daniel confirmed we do not need it any longer. > can we remove it or cancel alerts for it? > https://jenkins.ovirt.org/blue/organizations/jenkins/system-sync_mirrors-... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2353) remove system-sync_mirrors-glusterfs-4.1-testing-el7-x86 job

by Ehud Yonasi (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2353?page=com.atlassian.jir... ] Ehud Yonasi commented on OVIRT-2353: ------------------------------------ This job was created by me for sandro, and it is now fixed. i sent a couple of emails to ignore it (and btw this is a living proof that replying to emails might not be the best solution for syncing infra owners :) ) Details are here: [1] Jira Ticket: https://ovirt-jira.atlassian.net/browse/OVIRT-2290 [2] Gerrit Patch: https://gerrit.ovirt.org/#/c/93041/ > remove system-sync_mirrors-glusterfs-4.1-testing-el7-x86 job > ------------------------------------------------------------ > > Key: OVIRT-2353 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2353 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > > this job is failing and Daniel confirmed we do not need it any longer. > can we remove it or cancel alerts for it? > https://jenkins.ovirt.org/blue/organizations/jenkins/system-sync_mirrors-... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2353) remove system-sync_mirrors-glusterfs-4.1-testing-el7-x86 job

by Eyal Edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2353?page=com.atlassian.jir... ] Eyal Edri commented on OVIRT-2353: ---------------------------------- +1 from me, [~sbonazzo(a)redhat.com] and @sahina which isn't here should also ACK, But you can also verify it by checking if it is on any OST reposync file or in the official oVirt release RPMs. > remove system-sync_mirrors-glusterfs-4.1-testing-el7-x86 job > ------------------------------------------------------------ > > Key: OVIRT-2353 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2353 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > > this job is failing and Daniel confirmed we do not need it any longer. > can we remove it or cancel alerts for it? > https://jenkins.ovirt.org/blue/organizations/jenkins/system-sync_mirrors-... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2358?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-2358: ------------------------------------- [~eedri] not sure I see where the gap is. [~sradco(a)redhat.com] can you use links to reosurces instead of Jenkins? > Permissions to revert "keep build forever" in jenkins > ----------------------------------------------------- > > Key: OVIRT-2358 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > I seem to be missing permission to revert "keep build forever" in jenkins. > Can you add me this permission? > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins

by Eyal Edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2358?page=com.atlassian.jir... ] Eyal Edri commented on OVIRT-2358: ---------------------------------- [~bkorren(a)redhat.com] I mean, can we provide a reasonable way for [~sradco(a)redhat.com] to get the same info she needs to a release and not have to use the 'keep forever' option? even if its manual ( as its today as well ). > Permissions to revert "keep build forever" in jenkins > ----------------------------------------------------- > > Key: OVIRT-2358 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > I seem to be missing permission to revert "keep build forever" in jenkins. > Can you add me this permission? > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2358?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-2358: ------------------------------------- [~eedri] yeah, look at the job output/artifacts. Not sure what you mean by "an immediate alternative option", this is a manual process where people update a ropman configurationfil in releng-tools, they can put any URL there including ones that point to resoures.ovirt.org. Also this being a repoman configuration file, people can do quite complex things like put a general link to the repo on resources and then use filters to select the exact desired set of packages. > Permissions to revert "keep build forever" in jenkins > ----------------------------------------------------- > > Key: OVIRT-2358 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > I seem to be missing permission to revert "keep build forever" in jenkins. > Can you add me this permission? > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-2359: ------------------------------------- it sounds very strange that systemd just drops the environment information passed to the container; We shouldn't be inventing our own ways to pass this information; There must be some work-around for this somewhere; Perhaps the root environment is exposed by some file in /proc or /sys? > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins

by Eyal Edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2358?page=com.atlassian.jir... ] Eyal Edri commented on OVIRT-2358: ---------------------------------- Is there an easy way to for someone to know the RPM name? I didn't understand from your answer if there is an immediate alternative option to the current flow. > Permissions to revert "keep build forever" in jenkins > ----------------------------------------------------- > > Key: OVIRT-2358 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > I seem to be missing permission to revert "keep build forever" in jenkins. > Can you add me this permission? > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 5 months

1
0
0 / 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jir... ] Daniel Belenky commented on OVIRT-2359: --------------------------------------- currently, in order to start an stdci container, you need to write an environment file for systemd. This file needs information such as the agent's name, the secret, etc. We need it because systemd unitfile doesn't have access to the environment where docker set's the variables (root user's environment). So you need one systemd-environment file per container. It's done dynamically when you run not during the build. Thinking of it now, it serves a completely different purpose and shoudn't be mixed. > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > We need to set a variable under the jenkins user that will indicate we're running inside a container. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

6 years, 5 months

1
0
0 / 0

Build failed in Jenkins: system-sync_mirrors-glusterfs-4.1-testing-el7-x86_64 #1

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-4.1-testing-el...> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-4.1-testing-el...> Cloning the remote Git repository Cloning repository http://gerrit.ovirt.org/jenkins.git > git init <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-4.1-testing-el...> # timeout=10 Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 No valid HEAD. Skipping the resetting > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision a0f3a1b493603a886874a3128be830a462c211ad (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f a0f3a1b493603a886874a3128be830a462c211ad Commit message: "Add engine-db-query to stdci-v2" First time build. Skipping changelog. [system-sync_mirrors-glusterfs-4.1-testing-el7-x86_64] $ /bin/bash -xe /tmp/jenkins2502757672743858937.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror glusterfs-4.1-testing-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Warning: cannot find repository glusterfs-4.1-testing-el7 No repositories found Build step 'Execute shell' marked build as failure

6 years, 5 months

1
15
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra July 2018