August 2019 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2785) Unable to add Documentation +1 flag to patch

by Eyal Edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2785?page=com.atlassian.jir... ] Eyal Edri commented on OVIRT-2785: ---------------------------------- I just added myself to the documentation group and was able to add the Documentation flag myself. Is it possible you have 2 users that might need merging? On Thu, Aug 29, 2019 at 10:54 AM Dafna Ron (oVirt JIRA) < -- Eyal edri He / Him / His MANAGER CONTINUOUS PRODUCTIZATION SYSTEM ENGINEERING Red Hat <https://www.redhat.com/> <https://red.ht/sig> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel) > Unable to add Documentation +1 flag to patch > -------------------------------------------- > > Key: OVIRT-2785 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2785 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Steve Goodman > Assignee: infra > > I was able to add the Documentation +1 to patches in the ovirt-engine-api project, but now I can't. For example, https://gerrit.ovirt.org/#/c/102438/, when I click Reply, I don't see the Documentation flag. I do see the Code Review and Verified flags. > I checked to see if I'm on https://gerrit.ovirt.org/#/admin/groups/131,members and I am. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

5 years, 3 months

1
0
0 / 0

[JIRA] (OVIRT-2785) Unable to add Documentation +1 flag to patch

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2785?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2785: ---------------------------------- [~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143] was this removed? > Unable to add Documentation +1 flag to patch > -------------------------------------------- > > Key: OVIRT-2785 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2785 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Steve Goodman > Assignee: infra > > I was able to add the Documentation +1 to patches in the ovirt-engine-api project, but now I can't. For example, https://gerrit.ovirt.org/#/c/102438/, when I click Reply, I don't see the Documentation flag. I do see the Code Review and Verified flags. > I checked to see if I'm on https://gerrit.ovirt.org/#/admin/groups/131,members and I am. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

5 years, 3 months

2
1
0 / 0

[JIRA] (OVIRT-2785) Unable to add Documentation +1 flag to patch

by Steve Goodman (oVirt JIRA)

Steve Goodman created OVIRT-2785: ------------------------------------ Summary: Unable to add Documentation +1 flag to patch Key: OVIRT-2785 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2785 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Steve Goodman Assignee: infra I was able to add the Documentation +1 to patches in the ovirt-engine-api project, but now I can't. For example, https://gerrit.ovirt.org/#/c/102438/, when I click Reply, I don't see the Documentation flag. I do see the Code Review and Verified flags. I checked to see if I'm on https://gerrit.ovirt.org/#/admin/groups/131,members and I am. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

5 years, 3 months

1
0
0 / 0

[JIRA] (OVIRT-2140) enforce SSL on resources.ovirt.org

by Eyal Edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2140?page=com.atlassian.jir... ] Eyal Edri commented on OVIRT-2140: ---------------------------------- [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] can we enable https for only the official releases under /pub and not for tested? so it won't affect the CI jobs speed, at least not at first stage? > enforce SSL on resources.ovirt.org > ---------------------------------- > > Key: OVIRT-2140 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2140 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > SSL was enabled on Resources with OVIRT-1472, this ticket is to transform the non-SSL virtual hosts into redirects to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

5 years, 3 months

1
0
0 / 0

[CQ]: 102845,2 (cockpit-ovirt) failed "ovirt-master" system tests

by oVirt Jenkins

Change 102845,2 (cockpit-ovirt) 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/102845/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15602/

5 years, 3 months

1
0
0 / 0

[JIRA] (OVIRT-2140) enforce SSL on resources.ovirt.org

by Marc Dequènes (Duck) (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2140?page=com.atlassian.jir... ] Marc Dequènes (Duck) commented on OVIRT-2140: --------------------------------------------- [~accountid:557058:2dee8503-051b-4630-8a75-2c544524dce8] with the above security concerns then YES we need to do it and infosec just came at my door to ask for the progress, so we’d better prioritize this task before one day we’re told to shutdown the service altogether. > enforce SSL on resources.ovirt.org > ---------------------------------- > > Key: OVIRT-2140 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2140 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > SSL was enabled on Resources with OVIRT-1472, this ticket is to transform the non-SSL virtual hosts into redirects to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

5 years, 3 months

1
0
0 / 0

[JIRA] (OVIRT-2140) enforce SSL on resources.ovirt.org

by Marc Dequènes (Duck) (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2140?page=com.atlassian.jir... ] Marc Dequènes (Duck) commented on OVIRT-2140: --------------------------------------------- [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] signed packages on HTTP are not safe because old releases are also valid thus it’s possible to do replay attacks by providing older and security buggy packages. it’s better but not sufficient. > enforce SSL on resources.ovirt.org > ---------------------------------- > > Key: OVIRT-2140 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2140 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > SSL was enabled on Resources with OVIRT-1472, this ticket is to transform the non-SSL virtual hosts into redirects to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

5 years, 3 months

1
0
0 / 0

oVirt infra daily report - unstable production jobs - 931

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/931//artifact/exported... Cheers, Jenkins

5 years, 3 months

1
0
0 / 0

[CQ]: 960bb3d (ovirt-web-ui) failed "ovirt-4.2" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-4.2" change queue including change 960bb3d (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change 4aaca2c (ovirt-web-ui) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 4aaca2c (ovirt-web-ui) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://github.com/oVirt/ovirt-web-ui/commit/960bb3d33f463f68448eda99b74a... For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-web-ui/commit/4aaca2c9b02867698024c4ae2f3e... For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4756/

5 years, 3 months

1
0
0 / 0

[CQ]: 960bb3d (ovirt-web-ui) failed "ovirt-4.3" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-4.3" change queue including change 960bb3d (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change 4aaca2c (ovirt-web-ui) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 4aaca2c (ovirt-web-ui) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://github.com/oVirt/ovirt-web-ui/commit/960bb3d33f463f68448eda99b74a... For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-web-ui/commit/4aaca2c9b02867698024c4ae2f3e... For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1927/

5 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra August 2019