- Infra - oVirt List Archives

[JIRA] (OVIRT-2019) users can't unsubscribe from list
by Marc Dequènes (Duck) (oVirt JIRA) 14 May '18

14 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2019?page=com.atlassian.jira.… ] Marc Dequènes (Duck) updated OVIRT-2019: ---------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) Status: In Progress (was: To Do) I looked into the logs and found traces similar to the previous bug ("Connection lost during _handle_client()", see https://gitlab.com/mailman/mailman/issues/416) After migration people began to use the ML again and this bug reappeared, but only for the gerrit ML. I fixed the DB manually and it did not reappear. This might be related. I subscribed and tried to unsubcribe from the UI and it worked. If I use the leave address instead, the previous trace occur but I shortly after (there is a delay due to greylisting) received the confirmation mail; I replied and it worked. > users can't unsubscribe from list > ---------------------------------- > > Key: OVIRT-2019 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2019 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri > Assignee: Marc Dequènes (Duck) > Priority: Highest > > There has been multiple reports from users on users(a)ovirt.org that they can't un-subscribe from the list, either using the UI or the leave ML alias. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100084)

1 0

[JIRA] (OVIRT-2018) Add documentation for the stdci_conf_check.py utility
by Barak Korren (oVirt JIRA) 14 May '18

14 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2018?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2018: ----------------------------------- Assignee: Emil Natan (was: infra) > Add documentation for the stdci_conf_check.py utility > ----------------------------------------------------- > > Key: OVIRT-2018 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2018 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation > Reporter: Emil Natan > Assignee: Emil Natan > Priority: High > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100084)

1 0

[JIRA] (OVIRT-2018) Add documentation for the stdci_conf_check.py utility
by Barak Korren (oVirt JIRA) 14 May '18

14 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2018?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2018: -------------------------------- Epic Link: OVIRT-400 Priority: High (was: Low) > Add documentation for the stdci_conf_check.py utility > ----------------------------------------------------- > > Key: OVIRT-2018 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2018 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation > Reporter: Emil Natan > Assignee: infra > Priority: High > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100084)

1 0

[JIRA] (OVIRT-2018) Add documentation for the stdci_conf_check.py utility
by Barak Korren (oVirt JIRA) 14 May '18

14 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2018?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2018: -------------------------------- Epic Link: OVIRT-400 > Add documentation for the stdci_conf_check.py utility > ----------------------------------------------------- > > Key: OVIRT-2018 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2018 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation > Reporter: Emil Natan > Assignee: infra > Priority: Low > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100084)

1 0

Re: [ovirt-users] Re: [ovirt-devel] Re: Mailing-Lists upgrade
by Marc Dequènes (Duck) 14 May '18

14 May '18

Quack, On 05/13/2018 08:27 PM, Alex K wrote: > I am also experiencing random issues with this mailing list, even before > the upgrade. Some replies I never receive them ( I know this because a > friend of mine relays the emails I dont get...). I tried to unsubscribe > and subscribe but I still face this issue. Well, as it happened before the migration I guess it's more of mail antispam & co problem. Could you open a JIRA ticket with as much information as you can on the subject please? I'm going to focus on migration problems first, but I'll a look at it afterwards. \_o<

1 0

[CQ]: 91128, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 May '18

13 May '18

A system test invoked by the "ovirt-master" change queue including change 91128,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91084,1 (ovirt-engine) 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 91084,1 (ovirt-engine) 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://gerrit.ovirt.org/#/c/91128/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91084/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7558/

1 0

[CQ]: 91188, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 May '18

13 May '18

A system test invoked by the "ovirt-master" change queue including change 91188,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91084,1 (ovirt-engine) 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 91084,1 (ovirt-engine) 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://gerrit.ovirt.org/#/c/91188/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91084/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7552/

1 0

[JIRA] (OVIRT-2020) Implement a normalizer for runtime_requirements
by Daniel Belenky (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2020?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2020: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Implement a normalizer for runtime_requirements > ----------------------------------------------- > > Key: OVIRT-2020 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2020 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > Currently, we are not parsing the data under runtime_requirements at all. > It means that the 1st place user will encounter an error is when the job runs - > it's bad since debugging it is much harder than our DSL. > Since we lack a normalizer for runtime_requirements, as a temporary workaround we have code in > standard-stage.groovy that verifies the value of some inputs under runtime_requirements. > It should be removed as soon as a proper normalizer is implemented. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2020) Implement a normalizer for runtime_requirements
by Daniel Belenky (oVirt JIRA) 13 May '18

13 May '18

Daniel Belenky created OVIRT-2020: ------------------------------------- Summary: Implement a normalizer for runtime_requirements Key: OVIRT-2020 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2020 Project: oVirt - virtualization made easy Issue Type: Task Components: Standard CI (Pipelines), STDCI DSL Reporter: Daniel Belenky Assignee: infra Currently, we are not parsing the data under runtime_requirements at all. It means that the 1st place user will encounter an error is when the job runs - it's bad since debugging it is much harder than our DSL. Since we lack a normalizer for runtime_requirements, as a temporary workaround we have code in standard-stage.groovy that verifies the value of some inputs under runtime_requirements. It should be removed as soon as a proper normalizer is implemented. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2020) Implement a normalizer for runtime_requirements
by Daniel Belenky (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2020?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2020: ---------------------------------- Epic Link: OVIRT-400 > Implement a normalizer for runtime_requirements > ----------------------------------------------- > > Key: OVIRT-2020 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2020 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > Currently, we are not parsing the data under runtime_requirements at all. > It means that the 1st place user will encounter an error is when the job runs - > it's bad since debugging it is much harder than our DSL. > Since we lack a normalizer for runtime_requirements, as a temporary workaround we have code in > standard-stage.groovy that verifies the value of some inputs under runtime_requirements. > It should be removed as soon as a proper normalizer is implemented. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0