April 2019 - Infra - oVirt List Archives

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Michal Skrivanek reopened OVIRT-2714: ------------------------------------- > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Michal Skrivanek edited comment on OVIRT-2714 at 4/10/19 10:04 AM: ------------------------------------------------------------------- the intent of the original ticket to solve manual OST, but it only solves building artifacts. e still need more concurrent (or at least 1!!!) worker for the actual OST run was (Author: mskrivanek): actually, now that i read the description again. it was the intent of the original ticket to solve manual OST...so the original ticket is the right one > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Michal Skrivanek updated OVIRT-2714: ------------------------------------ Resolution: Duplicate Status: Done (was: To Do) > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Michal Skrivanek commented on OVIRT-2714: ----------------------------------------- actually, now that i read the description again. it was the intent of the original ticket to solve manual OST...so the original ticket is the right one > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Michal Skrivanek updated OVIRT-2714: ------------------------------------ Description: This one is about manual OST runs cloned from OVIRT-2704 --- We started to use this job to build artifacts for running OST. Looks like this job is limited to one concurrent job, which make it less useful than it could be. If we don't make it easy to run OST, people will not run it, and the change queue will break. Please change the limit to use the same limit used for regular builds. We seem to be able to create more then 10 concurrent builds by uploading patches to gerrit. The manual runner should this as well. Nir was: We started to use this job to build artifacts for running OST. Looks like this job is limited to one concurrent job, which make it less useful than it could be. If we don't make it easy to run OST, people will not run it, and the change queue will break. Please change the limit to use the same limit used for regular builds. We seem to be able to create more then 10 concurrent builds by uploading patches to gerrit. The manual runner should this as well. Nir > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Michal Skrivanek updated OVIRT-2714: ------------------------------------ Summary: Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs (was: CLONE - Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs) > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) CLONE - Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

Michal Skrivanek created OVIRT-2714: --------------------------------------- Summary: CLONE - Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs Key: OVIRT-2714 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Michal Skrivanek Assignee: infra We started to use this job to build artifacts for running OST. Looks like this job is limited to one concurrent job, which make it less useful than it could be. If we don't make it easy to run OST, people will not run it, and the change queue will break. Please change the limit to use the same limit used for regular builds. We seem to be able to create more then 10 concurrent builds by uploading patches to gerrit. The manual runner should this as well. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2713) Package does not match intended download on PHX mirror
by Evgheni Dereveanchin (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2713?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2713: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Package does not match intended download on PHX mirror > ------------------------------------------------------ > > Key: OVIRT-2713 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2713 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > I was working on updating some nodes and hit an issue that was reported before in CI. Basically, a package fails to install when running "yum update" with the following error: > Error downloading packages: > polkit-0.112-18.el7_6.1.x86_64: failed to retrieve Packages/polkit-0.112-18.el7_6.1.x86_64.rpm from centos-updates-el7 > error was [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=centos-updates-el7 clean metadata > Last time I checked the file was intact on the mirror so it may be a sign of metadata corruption on the snapshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2713) Package does not match intended download on PHX mirror
by Evgheni Dereveanchin (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2713?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2713: --------------------------------------------- The exact URL that fails is: http://mirrors.phx.ovirt.org/repos/yum/centos-updates-el7/base/Packages/pol… Downloading this file produces an md5sum of 79c1fa6804307bfc54833c880743c358 which matches the file from an upstream mirror: http://mirror.centos.org/centos/7/updates/x86_64/Packages/polkit-0.112-18.e… Running "rpm -Uvh" on the downloaded RPM does not produce any warnings either so it is intact. > Package does not match intended download on PHX mirror > ------------------------------------------------------ > > Key: OVIRT-2713 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2713 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > I was working on updating some nodes and hit an issue that was reported before in CI. Basically, a package fails to install when running "yum update" with the following error: > Error downloading packages: > polkit-0.112-18.el7_6.1.x86_64: failed to retrieve Packages/polkit-0.112-18.el7_6.1.x86_64.rpm from centos-updates-el7 > error was [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=centos-updates-el7 clean metadata > Last time I checked the file was intact on the mirror so it may be a sign of metadata corruption on the snapshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2713) Package does not match intended download on PHX mirror
by Evgheni Dereveanchin (oVirt JIRA) 10 Apr '19

10 Apr '19

Evgheni Dereveanchin created OVIRT-2713: ------------------------------------------- Summary: Package does not match intended download on PHX mirror Key: OVIRT-2713 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2713 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra I was working on updating some nodes and hit an issue that was reported before in CI. Basically, a package fails to install when running "yum update" with the following error: Error downloading packages: polkit-0.112-18.el7_6.1.x86_64: failed to retrieve Packages/polkit-0.112-18.el7_6.1.x86_64.rpm from centos-updates-el7 error was [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=centos-updates-el7 clean metadata Last time I checked the file was intact on the mirror so it may be a sign of metadata corruption on the snapshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0