May 2019 - Infra - Ovirt List Archives

[CQ]: 99949, 5 (ovirt-engine-ui-extensions) failed "ovirt-master" system tests

by oVirt Jenkins

Change 99949,5 (ovirt-engine-ui-extensions) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/99949/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14185/

5 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-2732) New Grafana available

by Eyal Edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2732?page=com.atlassian.jir... ] Eyal Edri reassigned OVIRT-2732: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > New Grafana available > --------------------- > > Key: OVIRT-2732 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2732 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > Just seen we are running Grafana 5.4.2 on https://graphite.phx.ovirt.org . > Please note Grafana 6.1.6 is packaged and shipped with Fedora >= 29. > Not sure what is running on the host but you may consider haveing Fedora > Server 30 there with Grafana 6.1.6. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

5 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-2732) New Grafana available

by Eyal Edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2732?page=com.atlassian.jir... ] Eyal Edri updated OVIRT-2732: ----------------------------- Issue Type: Task (was: By-EMAIL) > New Grafana available > --------------------- > > Key: OVIRT-2732 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2732 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: sbonazzo > Assignee: infra > > Just seen we are running Grafana 5.4.2 on https://graphite.phx.ovirt.org . > Please note Grafana 6.1.6 is packaged and shipped with Fedora >= 29. > Not sure what is running on the host but you may consider haveing Fedora > Server 30 there with Grafana 6.1.6. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

5 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-2732) New Grafana available

by Eyal Edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2732?page=com.atlassian.jir... ] Eyal Edri commented on OVIRT-2732: ---------------------------------- Thanks for bringing this up, we'll consider it in the future, I'm not sure we have plans for upgrading ATM, as we still have quite a big backlog of urgent tasks to complete. I also think we're using CentOS 7 to run. > New Grafana available > --------------------- > > Key: OVIRT-2732 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2732 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Just seen we are running Grafana 5.4.2 on https://graphite.phx.ovirt.org . > Please note Grafana 6.1.6 is packaged and shipped with Fedora >= 29. > Not sure what is running on the host but you may consider haveing Fedora > Server 30 there with Grafana 6.1.6. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

5 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-2732) New Grafana available

by sbonazzo (oVirt JIRA)

sbonazzo created OVIRT-2732: ------------------------------- Summary: New Grafana available Key: OVIRT-2732 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2732 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Just seen we are running Grafana 5.4.2 on https://graphite.phx.ovirt.org . Please note Grafana 6.1.6 is packaged and shipped with Fedora >= 29. Not sure what is running on the host but you may consider haveing Fedora Server 30 there with Grafana 6.1.6. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

5 years, 6 months

1
0
0 / 0

Jenkins build became unstable: ovirt_4.2_publish-rpms_nightly #610

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/ovirt_4.2_publish-rpms_nightly/610/display/r...>

5 years, 6 months

1
2
0 / 0

oVirt infra daily report - unstable production jobs - 830

by jenkins＠jenkins.phx.ovirt.org

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/830//artifact/exported... Cheers, Jenkins

5 years, 6 months

1
0
0 / 0

[CQ]: 99935,3 (ovirt-engine) failed "ovirt-master" system tests

by oVirt Jenkins

Change 99935,3 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/99935/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14173/

5 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-2731) Can't docker push when using newer docker daemon?

by Roy Golan (oVirt JIRA)

Roy Golan created OVIRT-2731: -------------------------------- Summary: Can't docker push when using newer docker daemon? Key: OVIRT-2731 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2731 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Roy Golan Assignee: infra With this patch <https://github.com/oVirt/ovirt-openshift-extensions/pull/136>I'm building multi-stage images in my builds, and I'm trying to push them to quay. The docker push was working without any problems before the daemon change. The difference is that now the docker client is inside a container, which is inside mock, which has the docker socket of a docker daemon version 18. Docker login succeeds according to the job logs The push when uploading layers: [2019-05-19T06:12:03.008Z] + make push-containers PUSH_LATEST=0 <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshif...>[2019-05-19T06:12:03.008Z] Login Succeeded <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshif...>[2019-05-19T06:12:03.008Z] docker push quay.io/rgolangh/ovirt-flexvolume-driver:0.4.0-11.gd0ead0b <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshif...>[2019-05-19T06:12:03.008Z] The push refers to repository [quay.io/rgolangh/ovirt-flexvolume-driver] <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshif...>[2019-05-19T06:12:03.008Z] bf535c6e5461: Preparing <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshif...>[2019-05-19T06:12:03.008Z] e6318b33302c: Preparing <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshif...>[2019-05-19T06:12:03.008Z] a3890b39a2b2: Preparing <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshif...>[2019-05-19T06:12:03.008Z] e78e5b504103: Preparing <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshif...>[2019-05-19T06:12:03.008Z] f7fa4accb0ea: Preparing <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshif...>[2019-05-19T06:12:03.008Z] 35265ad107f5: Preparing <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshif...>[2019-05-19T06:12:03.008Z] 4765a2d3f85d: Preparing <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshif...>[2019-05-19T06:12:03.008Z] 35265ad107f5: Waiting <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshif...>[2019-05-19T06:12:03.008Z] 4765a2d3f85d: Waiting <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshif...>[2019-05-19T06:12:03.008Z] unauthorized: access to the requested resource is not authorized <https://jenkins.ovirt.org/blue/organizations/jenkins/oVirt_ovirt-openshif...>[2019-05-19T06:12:03.008Z] make: *** [container-push-ovirt-flexvolume-driver] Error 1 Can I get the daemon logs? anyone see it? any advice? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

5 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-2730) Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2730?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-2730: ------------------------------------- On Fri, 17 May 2019 at 01:04, Nir Soffer (oVirt JIRA) < I looked at the parameters screen <https://jenkins.ovirt.org/job/standard-manual-runner/265/parameters/> for the refspec you passed to the manual runner (refs/changes/07/100007/8) and then simply checked out the patch with `git review -d 100007`. Looking at `stdci.yaml` there you can see its quite different then the one in the master branch. So is commenting `ci test please` or `ci please test` or just `ci test` in gerrit.... Checkout the patch and have a look, the CI system does not rebase before testing, so it does not matter which branch you intend to merge into, only which commit you started from when first creating the local branch you wrote the patch in. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > Running sub stages using https://jenkins.ovirt.org/job/standard-manual-runner/ > ------------------------------------------------------------------------------ > > Key: OVIRT-2730 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2730 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I tried to run check-patch and check-patch linters substage from the > command line: > using: > https://github.com/nirs/oci/pull/37 > I assumed that this will run the entire check-patch stage, including all > the sub stages: > ./ovirt-ci run -s check-patch 100007 > But it run something that looks like check-patch with el7: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runn... > The test environment seems to be different that what we have when > check-patch is triggered > from gerrit. > Then I tried to run the linters substage: > ./ovirt-ci run -s check-patch.linters 100007 > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runn... > ./ovirt-ci run -s check-patch.linters 100007 > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runn... > Both succeeded without running anything :-) > Running build-artifacts works, not sure about check-network. > Can we fix the manual job so: > - it run exactly the same way as it run when gerrit trigger the job > - allow selection of a sub stage? > - nice to have - allow selection of multiple sub stages > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100102)

5 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra May 2019