- Infra - oVirt List Archives

[JIRA] (OVIRT-2001) Create FAQ/Knowledge Base for STDCI
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2001?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2001: -------------------------------- Epic Link: (was: OVIRT-400) > Create FAQ/Knowledge Base for STDCI > ----------------------------------- > > Key: OVIRT-2001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2001 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > There are many common use cases and issues in STDCI that could benefit from case/task-specific documentation. So we should have a FAQ page or a Knowledge Base about STDCI to cover these issues. > Before we can make the page we need a critical mass (at least 3) of issues and solutions, so we will use comments on this ticket to collect them as they arise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2001) Create FAQ/Knowledge Base for STDCI
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2001?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2001: -------------------------------- Epic Link: (was: OVIRT-400) > Create FAQ/Knowledge Base for STDCI > ----------------------------------- > > Key: OVIRT-2001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2001 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > Labels: first_time_task > > There are many common use cases and issues in STDCI that could benefit from case/task-specific documentation. So we should have a FAQ page or a Knowledge Base about STDCI to cover these issues. > Before we can make the page we need a critical mass (at least 3) of issues and solutions, so we will use comments on this ticket to collect them as they arise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2025) Document STDCI "V1.5" poll upstream sources jobs
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2025?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2025: -------------------------------- Epic Link: (was: OVIRT-400) > Document STDCI "V1.5" poll upstream sources jobs > ------------------------------------------------ > > Key: OVIRT-2025 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2025 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation, Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > Since we're about to introduce pipeline based poll-upstream-sources jobs, we need to have documentation for the process. Docs should include: > # How to create such job for a given project: implement a JJB temlpate > # How to configure STDCI configuration file so poll-upstream-sources will work. > If anything else is needed to be documented regarding this feature, please add it as a comment. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2025) Document STDCI "V1.5" poll upstream sources jobs
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2025?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2025: -------------------------------- Epic Link: (was: OVIRT-400) > Document STDCI "V1.5" poll upstream sources jobs > ------------------------------------------------ > > Key: OVIRT-2025 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2025 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation, Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > Since we're about to introduce pipeline based poll-upstream-sources jobs, we need to have documentation for the process. Docs should include: > # How to create such job for a given project: implement a JJB temlpate > # How to configure STDCI configuration file so poll-upstream-sources will work. > If anything else is needed to be documented regarding this feature, please add it as a comment. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2025) Document STDCI "V1.5" poll upstream sources jobs
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2025?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2025: -------------------------------- Component/s: Documentation > Document STDCI "V1.5" poll upstream sources jobs > ------------------------------------------------ > > Key: OVIRT-2025 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2025 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation, Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > Since we're about to introduce pipeline based poll-upstream-sources jobs, we need to have documentation for the process. Docs should include: > # How to create such job for a given project: implement a JJB temlpate > # How to configure STDCI configuration file so poll-upstream-sources will work. > If anything else is needed to be documented regarding this feature, please add it as a comment. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2029) Add cache pre-seed functionality to JJB
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2029?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2029: -------------------------------- Epic Link: (was: OVIRT-400) > Add cache pre-seed functionality to JJB > --------------------------------------- > > Key: OVIRT-2029 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2029 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: infra > Labels: upstream-contribution > > Since we run JJB from STDCI, we cannot have it rely on the existence of a persistent cache from its previous operation. Since JJB is most efficient when it has such a cache, our STDCI script generates such a cache for it from the contents of the previous commit. > To do that we essentially had to implement parts of the JJB internals (The cache handling) on our own. It desirable to have an option in JJB that would do that instead. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2029) Add cache pre-seed functionality to JJB
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2029?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2029: -------------------------------- Epic Link: (was: OVIRT-400) > Add cache pre-seed functionality to JJB > --------------------------------------- > > Key: OVIRT-2029 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2029 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: infra > Labels: upstream-contribution > > Since we run JJB from STDCI, we cannot have it rely on the existence of a persistent cache from its previous operation. Since JJB is most efficient when it has such a cache, our STDCI script generates such a cache for it from the contents of the previous commit. > To do that we essentially had to implement parts of the JJB internals (The cache handling) on our own. It desirable to have an option in JJB that would do that instead. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2030) Add cache-based deletion option to JJB
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2030?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2030: -------------------------------- Epic Link: (was: OVIRT-400) > Add cache-based deletion option to JJB > -------------------------------------- > > Key: OVIRT-2030 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2030 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: infra > Labels: upstream-contribution > > JJB currently supports two ways to delete jobs: > # The {{delete}} command which deletes specific jobs that are specified on the command line > # The {{--delete-old}] option to the {{update}} command which delete all jobs in Jenkins that are not included in the current update. > Both thes options do not do what we want whic is to delete all jobs not included in the current update that were previously manage by JJB. > To get this functionality we've made our scripts check the difference between to current and previous commits to find out which jobs were deleted. Instead we would like JJB to have the option for the {{update}} command to inspect the job cache from previous run (Or generated as explained in OVIRT-2029), and delete jobs found there that are not included in current update. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2030) Add cache-based deletion option to JJB
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2030?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2030: -------------------------------- Epic Link: (was: OVIRT-400) > Add cache-based deletion option to JJB > -------------------------------------- > > Key: OVIRT-2030 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2030 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: infra > Labels: upstream-contribution > > JJB currently supports two ways to delete jobs: > # The {{delete}} command which deletes specific jobs that are specified on the command line > # The {{--delete-old}] option to the {{update}} command which delete all jobs in Jenkins that are not included in the current update. > Both thes options do not do what we want whic is to delete all jobs not included in the current update that were previously manage by JJB. > To get this functionality we've made our scripts check the difference between to current and previous commits to find out which jobs were deleted. Instead we would like JJB to have the option for the {{update}} command to inspect the job cache from previous run (Or generated as explained in OVIRT-2029), and delete jobs found there that are not included in current update. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2033) Provide a "tagging" mecahnism for transactional mirrors.
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2033?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2033: -------------------------------- Epic Link: OVIRT-2184 (was: OVIRT-400) > Provide a "tagging" mecahnism for transactional mirrors. > -------------------------------------------------------- > > Key: OVIRT-2033 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2033 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI Mirrors > Reporter: Barak Korren > Assignee: infra > > Right now when using the CI mirrors, one can either: > # Use the latest snapshots from all mirrors as mock_runner and all the jobs do. > # Use a specific snapshot by using the direct URL to it as we do on slaves. > It is desirable to be able to mark or tag specific mirror snapshots for various uses. The primary use for this is to track which mirror snapshots have been tested successfully by the change queue in a similar fashion to the way we track passing packages by storing them in the 'tested' repo. The motivation behind doing this is described in OVIRT-1444 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2033) Provide a "tagging" mecahnism for transactional mirrors.
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2033?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2033: -------------------------------- Epic Link: OVIRT-2184 (was: OVIRT-400) > Provide a "tagging" mecahnism for transactional mirrors. > -------------------------------------------------------- > > Key: OVIRT-2033 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2033 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI Mirrors > Reporter: Barak Korren > Assignee: infra > > Right now when using the CI mirrors, one can either: > # Use the latest snapshots from all mirrors as mock_runner and all the jobs do. > # Use a specific snapshot by using the direct URL to it as we do on slaves. > It is desirable to be able to mark or tag specific mirror snapshots for various uses. The primary use for this is to track which mirror snapshots have been tested successfully by the change queue in a similar fashion to the way we track passing packages by storing them in the 'tested' repo. The motivation behind doing this is described in OVIRT-1444 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2036) Pre-merged patchsets can run on post-merged jobs in STDCI V2
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2036?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2036: -------------------------------- Epic Link: (was: OVIRT-400) > Pre-merged patchsets can run on post-merged 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 hence bypassing our whitelist filtering. > 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#100087)

1 0

[JIRA] (OVIRT-2036) Pre-merged patchsets can run on post-merged jobs in STDCI V2
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2036?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2036: -------------------------------- Epic Link: (was: OVIRT-400) > Pre-merged patchsets can run on post-merged 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 hence bypassing our whitelist filtering. > 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#100087)

1 0

[JIRA] (OVIRT-2037) Patchsets from non-whitelisted users can't run post-merge tasks
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2037?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2037: -------------------------------- Epic Link: (was: OVIRT-400) > Patchsets from non-whitelisted users can't run post-merge tasks > --------------------------------------------------------------- > > Key: OVIRT-2037 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2037 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Freestyle) > Reporter: Daniel Belenky > Assignee: infra > > In some cases, even if a patch was created by a non-whitelisted user, project maintainer can decide to merge > the patch. Currently, STDCI (V1) will block the patch from running any post-merge jobs due to whitelist check. > We need to allow project maintainers to bypass the whitelist check or disable whitelist checking on post-merge jobs. > Note: If we decide to disable whitelist check on post-merge jobs, we need to make sure we run post-merge jobs only on *merged* patchsets. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2037) Patchsets from non-whitelisted users can't run post-merge tasks
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2037?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2037: -------------------------------- Epic Link: (was: OVIRT-400) > Patchsets from non-whitelisted users can't run post-merge tasks > --------------------------------------------------------------- > > Key: OVIRT-2037 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2037 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Freestyle) > Reporter: Daniel Belenky > Assignee: infra > > In some cases, even if a patch was created by a non-whitelisted user, project maintainer can decide to merge > the patch. Currently, STDCI (V1) will block the patch from running any post-merge jobs due to whitelist check. > We need to allow project maintainers to bypass the whitelist check or disable whitelist checking on post-merge jobs. > Note: If we decide to disable whitelist check on post-merge jobs, we need to make sure we run post-merge jobs only on *merged* patchsets. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2039) Make JJB able to configure all aspects of the Jenkins master
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2039?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2039: -------------------------------- Epic Link: (was: OVIRT-400) > Make JJB able to configure all aspects of the Jenkins master > ------------------------------------------------------------ > > Key: OVIRT-2039 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2039 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: JJB > Reporter: Barak Korren > Assignee: infra > Labels: upstream-contribution > > There are two aspects of jenkins that JJB knows how to configure at this time: > # Jobs > # Views > There are however, other important aspects of the Jenkins configuration one typically needs to deal with: > # Plugins > # Credentials > # Global configuration setting such as global environment > # Gerrit and GitHub trigger settings > # Custom user data > It is desirable that JJB would be able to encompass all the required configuration for a given Jenkins instance. We should consider enabling it to configure the setting mentioned above and contribute that work to the upstream JJB project or distribute it as a separate plugin. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2039) Make JJB able to configure all aspects of the Jenkins master
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2039?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2039: -------------------------------- Epic Link: (was: OVIRT-400) > Make JJB able to configure all aspects of the Jenkins master > ------------------------------------------------------------ > > Key: OVIRT-2039 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2039 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: JJB > Reporter: Barak Korren > Assignee: infra > Labels: upstream-contribution > > There are two aspects of jenkins that JJB knows how to configure at this time: > # Jobs > # Views > There are however, other important aspects of the Jenkins configuration one typically needs to deal with: > # Plugins > # Credentials > # Global configuration setting such as global environment > # Gerrit and GitHub trigger settings > # Custom user data > It is desirable that JJB would be able to encompass all the required configuration for a given Jenkins instance. We should consider enabling it to configure the setting mentioned above and contribute that work to the upstream JJB project or distribute it as a separate plugin. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2167) Near real time log updates for STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2167?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2167: -------------------------------- Component/s: STDCI Build Report > Near real time log updates for STDCI build summary > -------------------------------------------------- > > Key: OVIRT-2167 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2167 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines), STDCI Build Report > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to see live log updates when running my build in order to trace the progress of my builds. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2167) Near real time log updates for STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2167?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2167: -------------------------------- Epic Link: (was: OVIRT-400) > Near real time log updates for STDCI build summary > -------------------------------------------------- > > Key: OVIRT-2167 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2167 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to see live log updates when running my build in order to trace the progress of my builds. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2167) Near real time log updates for STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2167?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2167: -------------------------------- Epic Link: (was: OVIRT-400) > Near real time log updates for STDCI build summary > -------------------------------------------------- > > Key: OVIRT-2167 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2167 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to see live log updates when running my build in order to trace the progress of my builds. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2168) Show build artifacts as soon as they are created in STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2168?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2168: -------------------------------- Epic Link: (was: OVIRT-400) > Show build artifacts as soon as they are created in STDCI build summary > ----------------------------------------------------------------------- > > Key: OVIRT-2168 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2168 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines), STDCI Build Report > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to have access to build artifacts as soon as possible in order to access different logs and outputs of my code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2168) Show build artifacts as soon as they are created in STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2168?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2168: -------------------------------- Epic Link: (was: OVIRT-400) > Show build artifacts as soon as they are created in STDCI build summary > ----------------------------------------------------------------------- > > Key: OVIRT-2168 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2168 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines), STDCI Build Report > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to have access to build artifacts as soon as possible in order to access different logs and outputs of my code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2168) Show build artifacts as soon as they are created in STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2168?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2168: -------------------------------- Component/s: Standard CI (Pipelines) STDCI Build Report > Show build artifacts as soon as they are created in STDCI build summary > ----------------------------------------------------------------------- > > Key: OVIRT-2168 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2168 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines), STDCI Build Report > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to have access to build artifacts as soon as possible in order to access different logs and outputs of my code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2169) Show important thread information in STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2169?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2169: -------------------------------- Epic Link: (was: OVIRT-400) > Show important thread information in STDCI build summary > -------------------------------------------------------- > > Key: OVIRT-2169 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2169 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > When debugging builds on STDCI I want to have quick access to information about thread's execution environment such as: hostname it's being executed on, host's distro and arch, maybe even some basic specs of the host(?) so I won't have to search for this information in Console Output. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2169) Show important thread information in STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2169?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2169: -------------------------------- Epic Link: (was: OVIRT-400) > Show important thread information in STDCI build summary > -------------------------------------------------------- > > Key: OVIRT-2169 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2169 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > When debugging builds on STDCI I want to have quick access to information about thread's execution environment such as: hostname it's being executed on, host's distro and arch, maybe even some basic specs of the host(?) so I won't have to search for this information in Console Output. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2170) Link from SCM to STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2170?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2170: -------------------------------- Epic Link: (was: OVIRT-400) > Link from SCM to STDCI build summary > ------------------------------------ > > Key: OVIRT-2170 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2170 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to have quick access to STDCI build summary so I can see information about my build without having to access it through Jenkins. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2170) Link from SCM to STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2170?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2170: -------------------------------- Epic Link: (was: OVIRT-400) > Link from SCM to STDCI build summary > ------------------------------------ > > Key: OVIRT-2170 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2170 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to have quick access to STDCI build summary so I can see information about my build without having to access it through Jenkins. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2171) Add support for HTML artifacts in STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2171?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2171: -------------------------------- Epic Link: (was: OVIRT-400) > Add support for HTML artifacts in STDCI build summary > ----------------------------------------------------- > > Key: OVIRT-2171 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2171 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > Priority: Low > > As an STDCI user, I want to have quick view of HTML artifacts from STDCI build summary so I wont have to search for it under build-artifacts. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2171) Add support for HTML artifacts in STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2171?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2171: -------------------------------- Epic Link: (was: OVIRT-400) > Add support for HTML artifacts in STDCI build summary > ----------------------------------------------------- > > Key: OVIRT-2171 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2171 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > Priority: Low > > As an STDCI user, I want to have quick view of HTML artifacts from STDCI build summary so I wont have to search for it under build-artifacts. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2172) STDCI build summary to write message when no threads were found
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2172?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2172: -------------------------------- Epic Link: (was: OVIRT-400) > STDCI build summary to write message when no threads were found > --------------------------------------------------------------- > > Key: OVIRT-2172 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2172 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to see a dedicated message at STDCI build summary that warns me that no threads were executed for my build to prevent cases where I think something runs while it doesn't (currently it shows blank page - users can think it's a bug in the summary.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2172) STDCI build summary to write message when no threads were found
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2172?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2172: -------------------------------- Epic Link: (was: OVIRT-400) > STDCI build summary to write message when no threads were found > --------------------------------------------------------------- > > Key: OVIRT-2172 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2172 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to see a dedicated message at STDCI build summary that warns me that no threads were executed for my build to prevent cases where I think something runs while it doesn't (currently it shows blank page - users can think it's a bug in the summary.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2173) STDCI build summary to include details about the STDCI event
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2173?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2173: -------------------------------- Epic Link: (was: OVIRT-400) > STDCI build summary to include details about the STDCI event > ------------------------------------------------------------ > > Key: OVIRT-2173 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2173 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to have quick view of the event details such as who is the change owner, what branch it was pushed to, and etc so I won't have to extract this information from the SCM. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2173) STDCI build summary to include details about the STDCI event
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2173?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2173: -------------------------------- Epic Link: (was: OVIRT-400) > STDCI build summary to include details about the STDCI event > ------------------------------------------------------------ > > Key: OVIRT-2173 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2173 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to have quick view of the event details such as who is the change owner, what branch it was pushed to, and etc so I won't have to extract this information from the SCM. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2174) Show dedicated message to early infra failures on STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2174?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2174: -------------------------------- Epic Link: (was: OVIRT-400) > Show dedicated message to early infra failures on STDCI build summary > --------------------------------------------------------------------- > > Key: OVIRT-2174 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2174 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to see a dedicated message on STDCI build summary in case STDCI failed before even running my code so I can quickly contact the infra team. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2174) Show dedicated message to early infra failures on STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2174?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2174: -------------------------------- Epic Link: (was: OVIRT-400) > Show dedicated message to early infra failures on STDCI build summary > --------------------------------------------------------------------- > > Key: OVIRT-2174 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2174 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to see a dedicated message on STDCI build summary in case STDCI failed before even running my code so I can quickly contact the infra team. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2176: ------------------------------------- Putting this under OVIRT-2184 as it seems full gating of platform changes would solve this as well. > oVirt CI should support fast moving platform releases > ----------------------------------------------------- > > Key: OVIRT-2176 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2176 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri > Assignee: infra > > It's a bit hard to describe this as a user story, but the idea is to think what can we (oVirt CI) do keep oVirt stable as it is today, while taking into account the platforms that support it ( Ansible, Wildfly, CentOS, Fedora. OpenShift? ) will at some point shift to a faster release cadence which is much more frequent from today and possibly breaks oVirt users if the proper testing won't be done right. > We are already doing good things today with oVirt System Tests and change queue, but it might not flexible and scalable enough if we'll start getting releases of layered products much faster. > This solution might include tighter cooperation with the relevant CI teams for the other products, improved OST framework, and infrastructure changes to support it. > Due to the side of this effort, it should be broken down into Epics and smaller user stories while grooming it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2176: -------------------------------- Epic Link: OVIRT-2184 > oVirt CI should support fast moving platform releases > ----------------------------------------------------- > > Key: OVIRT-2176 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2176 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri > Assignee: infra > > It's a bit hard to describe this as a user story, but the idea is to think what can we (oVirt CI) do keep oVirt stable as it is today, while taking into account the platforms that support it ( Ansible, Wildfly, CentOS, Fedora. OpenShift? ) will at some point shift to a faster release cadence which is much more frequent from today and possibly breaks oVirt users if the proper testing won't be done right. > We are already doing good things today with oVirt System Tests and change queue, but it might not flexible and scalable enough if we'll start getting releases of layered products much faster. > This solution might include tighter cooperation with the relevant CI teams for the other products, improved OST framework, and infrastructure changes to support it. > Due to the side of this effort, it should be broken down into Epics and smaller user stories while grooming it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2176: -------------------------------- Epic Link: OVIRT-2184 > oVirt CI should support fast moving platform releases > ----------------------------------------------------- > > Key: OVIRT-2176 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2176 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri > Assignee: infra > > It's a bit hard to describe this as a user story, but the idea is to think what can we (oVirt CI) do keep oVirt stable as it is today, while taking into account the platforms that support it ( Ansible, Wildfly, CentOS, Fedora. OpenShift? ) will at some point shift to a faster release cadence which is much more frequent from today and possibly breaks oVirt users if the proper testing won't be done right. > We are already doing good things today with oVirt System Tests and change queue, but it might not flexible and scalable enough if we'll start getting releases of layered products much faster. > This solution might include tighter cooperation with the relevant CI teams for the other products, improved OST framework, and infrastructure changes to support it. > Due to the side of this effort, it should be broken down into Epics and smaller user stories while grooming it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2176: -------------------------------- Epic Link: (was: OVIRT-400) > oVirt CI should support fast moving platform releases > ----------------------------------------------------- > > Key: OVIRT-2176 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2176 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri > Assignee: infra > > It's a bit hard to describe this as a user story, but the idea is to think what can we (oVirt CI) do keep oVirt stable as it is today, while taking into account the platforms that support it ( Ansible, Wildfly, CentOS, Fedora. OpenShift? ) will at some point shift to a faster release cadence which is much more frequent from today and possibly breaks oVirt users if the proper testing won't be done right. > We are already doing good things today with oVirt System Tests and change queue, but it might not flexible and scalable enough if we'll start getting releases of layered products much faster. > This solution might include tighter cooperation with the relevant CI teams for the other products, improved OST framework, and infrastructure changes to support it. > Due to the side of this effort, it should be broken down into Epics and smaller user stories while grooming it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2176: -------------------------------- Epic Link: (was: OVIRT-400) > oVirt CI should support fast moving platform releases > ----------------------------------------------------- > > Key: OVIRT-2176 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2176 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri > Assignee: infra > > It's a bit hard to describe this as a user story, but the idea is to think what can we (oVirt CI) do keep oVirt stable as it is today, while taking into account the platforms that support it ( Ansible, Wildfly, CentOS, Fedora. OpenShift? ) will at some point shift to a faster release cadence which is much more frequent from today and possibly breaks oVirt users if the proper testing won't be done right. > We are already doing good things today with oVirt System Tests and change queue, but it might not flexible and scalable enough if we'll start getting releases of layered products much faster. > This solution might include tighter cooperation with the relevant CI teams for the other products, improved OST framework, and infrastructure changes to support it. > Due to the side of this effort, it should be broken down into Epics and smaller user stories while grooming it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 90411, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Jun '18

12 Jun '18

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

1 0

[JIRA] (OVIRT-2193) vdsm project CQ failure: 004_basic_sanity.preview_snapshot_with_memory
by Dafna Ron (oVirt JIRA) 12 Jun '18

12 Jun '18

Dafna Ron created OVIRT-2193: -------------------------------- Summary: vdsm project CQ failure: 004_basic_sanity.preview_snapshot_with_memory Key: OVIRT-2193 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2193 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra we have a failed vdsm test in basic master suite. 004_basic_sanity.preview_snapshot_with_memory seems like a regression. ' 2018-06-12 07:31:08,080-04 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiNegotiationFilter] (default task-27) [] SsoRestApiNegotiationFilter Not performing Negotiate Auth 2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Input validation failed while processing 'POST' request for path '/vms/ec6dcfb7-dda9-4c58-b048-87b08ffcbfbe /previewsnapshot'. 2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Exception: org.ovirt.api.metamodel.server.ValidationException: Parameter 'snapshot.id' is mandatory but was not provided. at org.ovirt.engine.api.resource.VmResourceHelper.validatePreviewSnapshot(VmResourceHelper.java:75) [restapi-definition.jar:] at org.ovirt.engine.api.resource.VmResource.doPreviewSnapshot(VmResource.java:333) [restapi-definition.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_171] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_171] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_171] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_171]' Change 90532,7 (vdsm) 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/90532/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8169/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2180) Missing packages when trying to create reposync-config ovirt-master on Fedora 28
by Gal Ben Haim (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2180?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2180: ------------------------------------- Thanks. If I understand you correctly, until we drop the fluentd requirement from ovirt-engine, installing oVirt on Fedora is blocked? > Missing packages when trying to create reposync-config ovirt-master on Fedora 28 > -------------------------------------------------------------------------------- > > Key: OVIRT-2180 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2180 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > When trying to create reposync-config for ovirt-master on FC28 the following packges are missing: > {code:java} > Error: > Problem 1: conflicting requests > - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180308070539.git35a6428.fc28.x86_64 > - package ovirt-host-4.3.0-0.0.master.20180530065728.git836691d.fc28.s390x does not have a compatible architecture > - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180530070102.git836691d.fc28.x86_64 > - package ovirt-host-4.3.0-0.0.master.20180604121623.git6aeb275.fc28.s390x does not have a compatible architecture > - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180604121713.git6aeb275.fc28.x86_64 > - package ovirt-host-4.3.0-0.0.master.20180607122548.gitbdfe919.fc28.s390x does not have a compatible architecture > - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180607122828.gitbdfe919.fc28.x86_64 > Problem 2: conflicting requests > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180306070711.git2d3047c73c.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180530170515.git426823eb4a1.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601113423.git27f22ec3801.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601125541.gita6e87e15f8e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601151553.git588d48026c5.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603153247.git23ea19a71b9.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603185407.git60b31ae4ff6.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603200841.git0b63d547fb2.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604071126.git524908b0e26.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604084747.git8b9ad6a435e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604135226.git3e394fa5ef3.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180607083125.git21907ef1790.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608075105.gitff92e12aed8.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608115732.gita4bbacb7277.fc28.noarch > Problem 3: conflicting requests > - package ovirt-engine-extension-aaa-ldap-setup-1.3.8-0.0.master.gitf069cb9.fc28.noarch requires ovirt-engine >= 3.6, but none of the providers can be installed > - package ovirt-engine-extension-aaa-ldap-setup-1.3.8-0.0.master.gitff6678b.fc28.noarch requires ovirt-engine >= 3.6, but none of the providers can be installed > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180306070711.git2d3047c73c.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180530170515.git426823eb4a1.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601113423.git27f22ec3801.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601125541.gita6e87e15f8e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601151553.git588d48026c5.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603153247.git23ea19a71b9.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603185407.git60b31ae4ff6.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603200841.git0b63d547fb2.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604071126.git524908b0e26.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604084747.git8b9ad6a435e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604135226.git3e394fa5ef3.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180607083125.git21907ef1790.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608075105.gitff92e12aed8.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608115732.gita4bbacb7277.fc28.noarch > Problem 4: conflicting requests > - package ovirt-engine-extension-aaa-ldap-1.3.8-0.0.master.gitf069cb9.fc28.noarch requires ovirt-engine >= 3.5, but none of the providers can be installed > - package ovirt-engine-extension-aaa-ldap-1.3.8-0.0.master.gitff6678b.fc28.noarch requires ovirt-engine >= 3.5, but none of the providers can be installed > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180306070711.git2d3047c73c.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180530170515.git426823eb4a1.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601113423.git27f22ec3801.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601125541.gita6e87e15f8e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601151553.git588d48026c5.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603153247.git23ea19a71b9.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603185407.git60b31ae4ff6.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603200841.git0b63d547fb2.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604071126.git524908b0e26.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604084747.git8b9ad6a435e.fc28.noarch > - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604135226.git3e394fa5ef3.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180607083125.git21907ef1790.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608075105.gitff92e12aed8.fc28.noarch > - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608115732.gita4bbacb7277.fc28.noarch > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 90532,7 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 12 Jun '18

12 Jun '18

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

1 0

[JIRA] (OVIRT-2054) false change reported since package is not deployed on ost
by Dafna Ron (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2054?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2054: ---------------------------------- I did not keep the original build. will leave open until we see this again. > false change reported since package is not deployed on ost > ---------------------------------------------------------- > > Key: OVIRT-2054 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2054 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > Change 91507,1 (ovirt-engine-sdk-java) 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/91507/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ > The package is not deployed on OST so it could not have been the reason for failure. > + I am investigating the cause of failure but since we do not deploy the package on ost there is actually no chance that the failure was due to the change - hence its false report. > Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2148) 005_network_by_label.assign_hosts_network_label
by Dafna Ron (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2148?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2148: ----------------------------- Issue Type: Bug (was: Task) > 005_network_by_label.assign_hosts_network_label > ------------------------------------------------ > > Key: OVIRT-2148 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2148 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > Change 91614,10 (ovirt-provider-ovn) 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/91614/10 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2312/ > Fault reason is "Operation Failed". Fault detail is "[Cannot add Label. Another Setup Networks or Host Refresh process in progress on the host. Please try later.]". HTTP response code is 409. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2022) libguestfs-1.36.10-6.el7.centos.ppc64le requires qemu-img-ma
by Dafna Ron (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2022?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2022: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > libguestfs-1.36.10-6.el7.centos.ppc64le requires qemu-img-ma > ------------------------------------------------------------- > > Key: OVIRT-2022 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2022 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra, ost_infra_packages > > build-artifacts failing on http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/3508/c… > The error is package missing for; > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Error: Package: 1:libguestfs-1.36.10-6.el7.centos.ppc64le (el) > 12:20:11 Requires: qemu-img-ma > 12:20:11 Available: 10:qemu-img-ma-2.10.0-21.el7.ppc64le (el) > 12:20:11 qemu-img-ma = 10:2.10.0-21.el7 > 12:20:11 Available: 10:qemu-img-ma-2.10.0-21.el7_5.1.ppc64le (el-updates) > 12:20:11 qemu-img-ma = 10:2.10.0-21.el7_5.1 > 12:20:11 You could try using --skip-broken to work around the problem > 12:20:11 You could try running: rpm -Va --nofiles --nodigest > 12:20:11 > 12:20:11 Init took 28 seconds > 12:20:11 ============================ > 12:20:11 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > 12:20:11 @@ Thu May 10 12:20:11 UTC 2018 automation/build-artifacts.sh chroot finished > 12:20:11 @@ took 28 seconds > 12:20:11 @@ rc = 1 > 12:20:11 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > 12:20:11 ========== Scrubbing chroot > 12:20:11 mock \ > The issue is with centos: > https://bugzilla.redhat.com/show_bug.cgi?id=1570533 > The 7.5.1 should come out tomorrow and this issue will be fixed > opening ticket to follow up and make sure that its back to normal tomorrow. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2022) libguestfs-1.36.10-6.el7.centos.ppc64le requires qemu-img-ma
by Dafna Ron (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2022?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2022: ---------------------------------- this indeed is resolved. closing > libguestfs-1.36.10-6.el7.centos.ppc64le requires qemu-img-ma > ------------------------------------------------------------- > > Key: OVIRT-2022 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2022 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra, ost_infra_packages > > build-artifacts failing on http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/3508/c… > The error is package missing for; > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Error: Package: 1:libguestfs-1.36.10-6.el7.centos.ppc64le (el) > 12:20:11 Requires: qemu-img-ma > 12:20:11 Available: 10:qemu-img-ma-2.10.0-21.el7.ppc64le (el) > 12:20:11 qemu-img-ma = 10:2.10.0-21.el7 > 12:20:11 Available: 10:qemu-img-ma-2.10.0-21.el7_5.1.ppc64le (el-updates) > 12:20:11 qemu-img-ma = 10:2.10.0-21.el7_5.1 > 12:20:11 You could try using --skip-broken to work around the problem > 12:20:11 You could try running: rpm -Va --nofiles --nodigest > 12:20:11 > 12:20:11 Init took 28 seconds > 12:20:11 ============================ > 12:20:11 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > 12:20:11 @@ Thu May 10 12:20:11 UTC 2018 automation/build-artifacts.sh chroot finished > 12:20:11 @@ took 28 seconds > 12:20:11 @@ rc = 1 > 12:20:11 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > 12:20:11 ========== Scrubbing chroot > 12:20:11 mock \ > The issue is with centos: > https://bugzilla.redhat.com/show_bug.cgi?id=1570533 > The 7.5.1 should come out tomorrow and this issue will be fixed > opening ticket to follow up and make sure that its back to normal tomorrow. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2027) NPE with no thread appears in engine log
by Dafna Ron (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2027?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2027: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) > NPE with no thread appears in engine log > ---------------------------------------- > > Key: OVIRT-2027 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2027 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > This is not failing tests but should be fixed > [CQ]: 84817,6 (ovirt-engine) failed "ovirt-master" system tests > For further details about the change see: > https://gerrit.ovirt.org/#/c/84817/6 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7601/ > 2018-05-16 03:10:00,001-04 ERROR [org.ovirt.engine.core.bll.AutoRecoveryManager] (EE-ManagedThreadFactory-engineScheduled-Thread-92) [] Exception in recover: NullPointerException: -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2027) NPE with no thread appears in engine log
by Dafna Ron (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2027?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2027: ---------------------------------- I looked in several builds with failures and could not find this. I am closing as cannot reproduce. > NPE with no thread appears in engine log > ---------------------------------------- > > Key: OVIRT-2027 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2027 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > This is not failing tests but should be fixed > [CQ]: 84817,6 (ovirt-engine) failed "ovirt-master" system tests > For further details about the change see: > https://gerrit.ovirt.org/#/c/84817/6 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7601/ > 2018-05-16 03:10:00,001-04 ERROR [org.ovirt.engine.core.bll.AutoRecoveryManager] (EE-ManagedThreadFactory-engineScheduled-Thread-92) [] Exception in recover: NullPointerException: -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0