May 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2036) Post merge patchsets can run on pre-merge jobs in STDCI V2
by Daniel Belenky (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2036?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2036: ---------------------------------- Epic Link: OVIRT-400 > Post merge patchsets can run on pre-merge jobs in STDCI V2 > ---------------------------------------------------------- > > Key: OVIRT-2036 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2036 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > Currently, if one comments 'ci re-merge please' on a pre-merged patch, STDCI V2 will run post-merge jobs. > We need to fix it by checking if the event matches the actual state of the patch before running any user code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2036) Post merge patchsets can run on pre-merge jobs in STDCI V2
by Daniel Belenky (oVirt JIRA) 17 May '18

17 May '18

Daniel Belenky created OVIRT-2036: ------------------------------------- Summary: Post merge patchsets can run on pre-merge jobs in STDCI V2 Key: OVIRT-2036 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2036 Project: oVirt - virtualization made easy Issue Type: Bug Components: Standard CI (Pipelines) Reporter: Daniel Belenky Assignee: infra Currently, if one comments 'ci re-merge please' on a pre-merged patch, STDCI V2 will run post-merge jobs. We need to fix it by checking if the event matches the actual state of the patch before running any user code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[CQ]: 91320,1 (ovirt-host) failed "ovirt-4.2" system tests
by oVirt Jenkins 17 May '18

17 May '18

Change 91320,1 (ovirt-host) is probably the reason behind recent system test failures in the "ovirt-4.2" 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/91320/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1954/

1 0

[CQ]: 91312,1 (ovirt-host) failed "ovirt-master" system tests
by oVirt Jenkins 17 May '18

17 May '18

Change 91312,1 (ovirt-host) 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/91312/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7625/

1 0

[JIRA] (OVIRT-2035) CQ failed due to a patch from a non-whitelisted email
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2035?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2035: ----------------------------------- Assignee: Barak Korren (was: infra) > CQ failed due to a patch from a non-whitelisted email > ------------------------------------------------------ > > Key: OVIRT-2035 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2035 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue > Reporter: Evgheni Dereveanchin > Assignee: Barak Korren > > While investigating a change queue failure I saw a potentially buggy behavior when a patch is merged from a person that's not on the whitelist: > Failed CQ job: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7622/consoleF… > 08:00:49 ovirt-engine-api-model_master_build-artifacts-fc27-x86_64 (32) failed building > Related build-artifacts job: > http://jenkins.ovirt.org/job/ovirt-engine-api-model_master_build-artifacts-… > 07:07:10 shell-scripts/whitelist-filter.sh > 07:07:10 USER bburmest(a)redhat.com NOT FOUND IN THE WHITELIST, NOT RUNNING > 07:07:10 Build step 'Execute shell' marked build as failure > Merged gerrit patch: > https://gerrit.ovirt.org/#/c/91277/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2035) CQ failed due to a patch from a non-whitelisted email
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2035?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2035: ------------------------------------- Hmm... I think we fixed this in V2 - its a bit tricky to get a proper fox for this in V1, might even be impossible. > CQ failed due to a patch from a non-whitelisted email > ------------------------------------------------------ > > Key: OVIRT-2035 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2035 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue > Reporter: Evgheni Dereveanchin > Assignee: infra > > While investigating a change queue failure I saw a potentially buggy behavior when a patch is merged from a person that's not on the whitelist: > Failed CQ job: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7622/consoleF… > 08:00:49 ovirt-engine-api-model_master_build-artifacts-fc27-x86_64 (32) failed building > Related build-artifacts job: > http://jenkins.ovirt.org/job/ovirt-engine-api-model_master_build-artifacts-… > 07:07:10 shell-scripts/whitelist-filter.sh > 07:07:10 USER bburmest(a)redhat.com NOT FOUND IN THE WHITELIST, NOT RUNNING > 07:07:10 Build step 'Execute shell' marked build as failure > Merged gerrit patch: > https://gerrit.ovirt.org/#/c/91277/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2035) CQ failed due to a patch from a non-whitelisted email
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2035?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2035: -------------------------------- Epic Link: OVIRT-400 > CQ failed due to a patch from a non-whitelisted email > ------------------------------------------------------ > > Key: OVIRT-2035 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2035 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue > Reporter: Evgheni Dereveanchin > Assignee: infra > > While investigating a change queue failure I saw a potentially buggy behavior when a patch is merged from a person that's not on the whitelist: > Failed CQ job: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7622/consoleF… > 08:00:49 ovirt-engine-api-model_master_build-artifacts-fc27-x86_64 (32) failed building > Related build-artifacts job: > http://jenkins.ovirt.org/job/ovirt-engine-api-model_master_build-artifacts-… > 07:07:10 shell-scripts/whitelist-filter.sh > 07:07:10 USER bburmest(a)redhat.com NOT FOUND IN THE WHITELIST, NOT RUNNING > 07:07:10 Build step 'Execute shell' marked build as failure > Merged gerrit patch: > https://gerrit.ovirt.org/#/c/91277/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2035) CQ failed due to a patch from a non-whitelisted email
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2035?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2035: -------------------------------- Epic Link: OVIRT-400 > CQ failed due to a patch from a non-whitelisted email > ------------------------------------------------------ > > Key: OVIRT-2035 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2035 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue > Reporter: Evgheni Dereveanchin > Assignee: infra > > While investigating a change queue failure I saw a potentially buggy behavior when a patch is merged from a person that's not on the whitelist: > Failed CQ job: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7622/consoleF… > 08:00:49 ovirt-engine-api-model_master_build-artifacts-fc27-x86_64 (32) failed building > Related build-artifacts job: > http://jenkins.ovirt.org/job/ovirt-engine-api-model_master_build-artifacts-… > 07:07:10 shell-scripts/whitelist-filter.sh > 07:07:10 USER bburmest(a)redhat.com NOT FOUND IN THE WHITELIST, NOT RUNNING > 07:07:10 Build step 'Execute shell' marked build as failure > Merged gerrit patch: > https://gerrit.ovirt.org/#/c/91277/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2035) CQ failed due to a patch from a non-whitelisted email
by Evgheni Dereveanchin (oVirt JIRA) 17 May '18

17 May '18

Evgheni Dereveanchin created OVIRT-2035: ------------------------------------------- Summary: CQ failed due to a patch from a non-whitelisted email Key: OVIRT-2035 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2035 Project: oVirt - virtualization made easy Issue Type: Bug Components: Change Queue Reporter: Evgheni Dereveanchin Assignee: infra While investigating a change queue failure I saw a potentially buggy behavior when a patch is merged from a person that's not on the whitelist: Failed CQ job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7622/consoleF… 08:00:49 ovirt-engine-api-model_master_build-artifacts-fc27-x86_64 (32) failed building Related build-artifacts job: http://jenkins.ovirt.org/job/ovirt-engine-api-model_master_build-artifacts-… 07:07:10 shell-scripts/whitelist-filter.sh 07:07:10 USER bburmest(a)redhat.com NOT FOUND IN THE WHITELIST, NOT RUNNING 07:07:10 Build step 'Execute shell' marked build as failure Merged gerrit patch: https://gerrit.ovirt.org/#/c/91277/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2034) Recreate the transactional CI mirrors with Pulp
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2034?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2034: -------------------------------- Epic Link: OVIRT-403 > Recreate the transactional CI mirrors with Pulp > ----------------------------------------------- > > Key: OVIRT-2034 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2034 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI Mirrors > Reporter: Barak Korren > Assignee: infra > > Right now, the CI mirrors are created and maintained by a set of custom scripts and jobs. > It seems that [Pulp|https://pulpproject.org/] can do what our current system does. The reason behind not using it when we first made the mirrors system was out desire to provide a quick solution and avoid adding more services to maintain. > There are however, quite a few reasons to want to switch to pulp: > # Aside from RPMs it can also manage other interesting kinds of resources like Containers, DEB packages and Python packages. > # If it works well for us - we can maintain less code by dropping the existing mirror management code > # It has built-in distribution mechanisms that can be useful to scale it up. > # It seems it has support for assigning packages to multiple repos. This cab be used as a tagging mechanism to implement OVIRT-2033 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0