September 2018 - Infra - oVirt List Archives

[CQ]: 85744, 2 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Sep '18

04 Sep '18

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

1 0

[CQ]: 85721, 4 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Sep '18

04 Sep '18

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

1 0

[CQ]: 85724, 2 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Sep '18

04 Sep '18

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

1 0

[CQ]: 85779, 3 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Sep '18

04 Sep '18

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

1 0

[CQ]: cab89d8 (ovirt-ansible-manageiq) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Sep '18

04 Sep '18

A system test invoked by the "ovirt-4.2" change queue including change cab89d8 (ovirt-ansible-manageiq) failed. However, this change seems not to be the root cause for this failure. Change 9e1fdd0 (ovirt-ansible-manageiq) 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 9e1fdd0 (ovirt-ansible- manageiq) 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-ansible-manageiq/commit/cab89d8f80fdad5f06d2… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-manageiq/commit/9e1fdd087daecbf2b201… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3041/

1 0

[CQ]: 85707, 5 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Sep '18

04 Sep '18

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

1 0

[CQ]: 85794, 3 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Sep '18

04 Sep '18

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

1 0

[JIRA] (OVIRT-2471) Make timeout configurable from STDCI DSL
by Daniel Belenky (oVirt JIRA) 04 Sep '18

04 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2471?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2471: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Make timeout configurable from STDCI DSL > ---------------------------------------- > > Key: OVIRT-2471 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2471 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > As new projects have new timeout requirements, we should allow them to configure the timeout from stdci.yaml. > The configuration should probably go to runtime_requirements and configurable under the 'timeout' key. The configuration should be from the following form: > {code:java} > [0-9]+(\s+)?(h|s|m) > {code} > and where h, s and m can have multiple forms such as hour, hours, minute, etc... > Example: > {code:java} > --- > runtime requirements: > timeout: 2h > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2471) Make timeout configurable from STDCI DSL
by Daniel Belenky (oVirt JIRA) 04 Sep '18

04 Sep '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2471?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2471: ---------------------------------- Description: As new projects have new timeout requirements, we should allow them to configure the timeout from stdci.yaml. The configuration should probably go to runtime_requirements and configurable under the 'timeout' key. The configuration should be from the following form: {code:java} [0-9]+(\s+)?(h|s|m) {code} and where h, s and m can have multiple forms such as hour, hours, minute, etc... Example: {code:java} --- runtime requirements: timeout: 2h {code} was: As new projects have new timeout requirements, we should allow them to configure the timeout from stdci.yaml. The configuration should probably go to runtime_requirements and configurable under the 'timeout' key. The configuration should be from the following form: [0-9]+(\s+)?(h|s|m) and where h, s and m can have multiple forms such as hour, hours, minute, etc... Example: {code:java} --- runtime requirements: timeout: 2h {code} > Make timeout configurable from STDCI DSL > ---------------------------------------- > > Key: OVIRT-2471 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2471 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > > As new projects have new timeout requirements, we should allow them to configure the timeout from stdci.yaml. > The configuration should probably go to runtime_requirements and configurable under the 'timeout' key. The configuration should be from the following form: > {code:java} > [0-9]+(\s+)?(h|s|m) > {code} > and where h, s and m can have multiple forms such as hour, hours, minute, etc... > Example: > {code:java} > --- > runtime requirements: > timeout: 2h > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0

[JIRA] (OVIRT-2471) Make timeout configurable from STDCI DSL
by Daniel Belenky (oVirt JIRA) 04 Sep '18

04 Sep '18

Daniel Belenky created OVIRT-2471: ------------------------------------- Summary: Make timeout configurable from STDCI DSL Key: OVIRT-2471 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2471 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: infra As new projects have new timeout requirements, we should allow them to configure the timeout from stdci.yaml. The configuration should probably go to runtime_requirements and configurable under the 'timeout' key. The configuration should be from the following form: [0-9]+(\s+)?(h|s|m) and where h, s and m can have multiple forms such as hour, hours, minute, etc... Example: {code:java} --- runtime requirements: timeout: 2h {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091)

1 0