- Infra - oVirt List Archives

[JIRA] (OVIRT-2218) python-six package is missing on slaves
by Barak Korren (oVirt JIRA) 19 Jun '18

19 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2218?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2218: ----------------------------------- Assignee: Barak Korren (was: infra) > python-six package is missing on slaves > --------------------------------------- > > Key: OVIRT-2218 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2218 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: Barak Korren > Priority: High > > We're seeing job failures because the python-six package is missing. We're seeing those on the newly installed FC28 slaves ATM but we have reasons to believe this will affect any newly installed slave that uses updated repos. > We did not have code explicitly installing python-sic so far, instead we got it as a dependency of some other package we were using that probably dropped the dependency recently. > We should: > # Manually ensure that python-six and ptyhon3-six in installed on all slaves > # Make sure that global_setup.sh installs these packages > # Make sure the slave setup scripts install these packages -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2218) python-six package is missing on slaves
by Barak Korren (oVirt JIRA) 19 Jun '18

19 Jun '18

Barak Korren created OVIRT-2218: ----------------------------------- Summary: python-six package is missing on slaves Key: OVIRT-2218 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2218 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra Priority: High We're seeing job failures because the python-six package is missing. We're seeing those on the newly installed FC28 slaves ATM but we have reasons to believe this will affect any newly installed slave that uses updated repos. We did not have code explicitly installing python-sic so far, instead we got it as a dependency of some other package we were using that probably dropped the dependency recently. We should: # Manually ensure that python-six and ptyhon3-six in installed on all slaves # Make sure that global_setup.sh installs these packages # Make sure the slave setup scripts install these packages -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2217) global-setup should install python-six
by Daniel Belenky (oVirt JIRA) 19 Jun '18

19 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2217?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2217: ------------------------------------- Assignee: Daniel Belenky (was: infra) > global-setup should install python-six > -------------------------------------- > > Key: OVIRT-2217 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2217 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > Global setup should install python-six package since it's a core requirement for STDCI. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2217) global-setup should install python-six
by Daniel Belenky (oVirt JIRA) 19 Jun '18

19 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2217?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2217: ---------------------------------- Epic Link: OVIRT-400 > global-setup should install python-six > -------------------------------------- > > Key: OVIRT-2217 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2217 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Daniel Belenky > Assignee: infra > > Global setup should install python-six package since it's a core requirement for STDCI. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2217) global-setup should install python-six
by Daniel Belenky (oVirt JIRA) 19 Jun '18

19 Jun '18

Daniel Belenky created OVIRT-2217: ------------------------------------- Summary: global-setup should install python-six Key: OVIRT-2217 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2217 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Daniel Belenky Assignee: infra Global setup should install python-six package since it's a core requirement for STDCI. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2215) Developer permissions - Ovirt Jenkins
by Emil Natan (oVirt JIRA) 19 Jun '18

19 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2215?page=com.atlassian.jira.… ] Emil Natan reassigned OVIRT-2215: --------------------------------- Assignee: Emil Natan (was: infra) > Developer permissions - Ovirt Jenkins > ------------------------------------- > > Key: OVIRT-2215 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2215 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Asaf Rachmani > Assignee: Emil Natan > > Hi, > Can you please provide me developer permissions in Ovirt Jenkins (re-trigger option for example)? > Thanks, > Asaf -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2214) proxy test fails due to wget missing on CI slaves
by Barak Korren (oVirt JIRA) 19 Jun '18

19 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2214?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2214: -------------------------------- Component/s: mock_runner > proxy test fails due to wget missing on CI slaves > ------------------------------------------------- > > Key: OVIRT-2214 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2214 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Evgheni Dereveanchin > Assignee: infra > > A lot of jobs have this warning in their logs: > Failed to contact proxy http://proxy01.phx.ovirt.org:3128, falling back to non-proxied config > The proxy is running fine and is reachable yet wget is missing in minimal setups of CentOS and Fedora. We are not installing it from global_setup and it seems to be needed by the try_proxy function of mock_runner that is used to generate mock configs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2214) proxy test fails due to wget missing on CI slaves
by Barak Korren (oVirt JIRA) 19 Jun '18

19 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2214?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2214: -------------------------------- Issue Type: Bug (was: Task) > proxy test fails due to wget missing on CI slaves > ------------------------------------------------- > > Key: OVIRT-2214 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2214 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > A lot of jobs have this warning in their logs: > Failed to contact proxy http://proxy01.phx.ovirt.org:3128, falling back to non-proxied config > The proxy is running fine and is reachable yet wget is missing in minimal setups of CentOS and Fedora. We are not installing it from global_setup and it seems to be needed by the try_proxy function of mock_runner that is used to generate mock configs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2214) proxy test fails due to wget missing on CI slaves
by Barak Korren (oVirt JIRA) 19 Jun '18

19 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2214?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2214: ------------------------------------- Maybe we can switch it to 'curl' in mock runner - I think curl is more common these days anyway. [~ederevea] can you quickly confirm we have curl everywhere? > proxy test fails due to wget missing on CI slaves > ------------------------------------------------- > > Key: OVIRT-2214 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2214 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: infra > > A lot of jobs have this warning in their logs: > Failed to contact proxy http://proxy01.phx.ovirt.org:3128, falling back to non-proxied config > The proxy is running fine and is reachable yet wget is missing in minimal setups of CentOS and Fedora. We are not installing it from global_setup and it seems to be needed by the try_proxy function of mock_runner that is used to generate mock configs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 256 - Failure!
by jenkins＠jenkins.phx.ovirt.org 19 Jun '18

19 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master… Build Number: 256 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #256 [Yedidyah Bar David] UI sanity: Increase timeout [Sandro Bonazzola] ovirt-jboss-modules-maven-plugin: move to v2 ----------------- Failed Tests: ----------------- All tests passed

1 1

[oVirt CI] standard-enqueue - Build #14428 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 19 Jun '18

19 Jun '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/14428/ Build Name: #14428 Build Description: Gerrit: 92316 - ovirt-imageio (4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/92316 - title: docs: unix-support - project: ovirt-imageio - branch: master - author: Daniel Erez <derez(a)redhat.com>

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 272 - Failure!
by jenkins＠jenkins.phx.ovirt.org 18 Jun '18

18 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/272/ Build Number: 272 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #272 [Milan Zamazal] Make sure complete SS_PATH exists [Barak Korren] Control slave repos for FC28 [Barak Korren] Update slave mirror snapshots ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2216) Cannot find a valid baseurl for repo: base/7/x86_64
by eyal edri (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2216?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2216: ---------------------------------- This looks like a broken repo issue. Try closing 4.2 to external repos like we did for master. On Mon, Jun 18, 2018, 19:07 Dafna Ron (oVirt JIRA) < > Cannot find a valid baseurl for repo: base/7/x86_64 > --------------------------------------------------- > > Key: OVIRT-2216 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2216 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra, ost_race > > vm deployment in lago fails with: > Cannot find a valid baseurl for repo: base/7/x86_64 > This is the 3ed time I have seen this and I think we may have network lag that is causing a time out. > [~ederevea] can you please take a look? > https://jenkins.ovirt.org/view/Change queue jobs/job/ovirt-4.2_change-queue-tester/2431 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2216) Cannot find a valid baseurl for repo: base/7/x86_64
by Dafna Ron (oVirt JIRA) 18 Jun '18

18 Jun '18

Dafna Ron created OVIRT-2216: -------------------------------- Summary: Cannot find a valid baseurl for repo: base/7/x86_64 Key: OVIRT-2216 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2216 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra vm deployment in lago fails with: Cannot find a valid baseurl for repo: base/7/x86_64 This is the 3ed time I have seen this and I think we may have network lag that is causing a time out. [~ederevea] can you please take a look? https://jenkins.ovirt.org/view/Change queue jobs/job/ovirt-4.2_change-queue-tester/2431 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

2 1

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

18 Jun '18

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

1 0

[JIRA] (OVIRT-2215) Developer permissions - Ovirt Jenkins
by Asaf Rachmani (oVirt JIRA) 18 Jun '18

18 Jun '18

Asaf Rachmani created OVIRT-2215: ------------------------------------ Summary: Developer permissions - Ovirt Jenkins Key: OVIRT-2215 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2215 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Asaf Rachmani Assignee: infra Hi, Can you please provide me developer permissions in Ovirt Jenkins (re-trigger option for example)? Thanks, Asaf -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2214) proxy test fails due to wget missing on CI slaves
by Evgheni Dereveanchin (oVirt JIRA) 18 Jun '18

18 Jun '18

Evgheni Dereveanchin created OVIRT-2214: ------------------------------------------- Summary: proxy test fails due to wget missing on CI slaves Key: OVIRT-2214 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2214 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra A lot of jobs have this warning in their logs: Failed to contact proxy http://proxy01.phx.ovirt.org:3128, falling back to non-proxied config The proxy is running fine and is reachable yet wget is missing in minimal setups of CentOS and Fedora. We are not installing it from global_setup and it seems to be needed by the try_proxy function of mock_runner that is used to generate mock configs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1717) When a component build passes OST, tag its git hash
by Daniel Belenky (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1717: ------------------------------------- Assignee: Daniel Belenky (was: infra) > When a component build passes OST, tag its git hash > --------------------------------------------------- > > Key: OVIRT-1717 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1717 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Change Queue > Reporter: danken > Assignee: Daniel Belenky > Labels: change-queue, standard-ci > > As a project maintainer, I want to see which changes passed CI gating (aka CQ) so that it will be easy for me to tell if a specific commit was tested in CQ and is available for QA. > *Scenario:* Project maintainer specifies in _stdci.yaml_ config that he wants STDCI to tag changes of this project by specifying > {code:java} > tag-on-release: > enabled: True > tag_template: "SomeTemplate with Jinja support { branch } and { queue_name } variables should be available too" > {code} > "standard stage" will add the relevant information to the change object and CQ will handle the tagging. > Need to see if the tags will be pushed by CQ as well or another component should be used (such as pusher.py) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1717) When a component build passes OST, tag its git hash
by Daniel Belenky (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1717: ---------------------------------- Description: As a project maintainer, I want to see which changes passed CI gating (aka CQ) so that it will be easy for me to tell if a specific commit was tested in CQ and is available for QA. *Scenario:* Project maintainer specifies in _stdci.yaml_ config that he wants STDCI to tag changes of this project by specifying {code:java} tag-on-release: enabled: True tag_template: "SomeTemplate with Jinja support { branch } and { queue_name } variables should be available too" {code} "standard stage" will add the relevant information to the change object and CQ will handle the tagging. Need to see if the tags will be pushed by CQ as well or another component should be used (such as pusher.py) was:Tagging the source git would make it easier for me to tell if a specific git commit is already tested by OST and available for QA. > When a component build passes OST, tag its git hash > --------------------------------------------------- > > Key: OVIRT-1717 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1717 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Change Queue > Reporter: danken > Assignee: infra > Labels: change-queue, standard-ci > > As a project maintainer, I want to see which changes passed CI gating (aka CQ) so that it will be easy for me to tell if a specific commit was tested in CQ and is available for QA. > *Scenario:* Project maintainer specifies in _stdci.yaml_ config that he wants STDCI to tag changes of this project by specifying > {code:java} > tag-on-release: > enabled: True > tag_template: "SomeTemplate with Jinja support { branch } and { queue_name } variables should be available too" > {code} > "standard stage" will add the relevant information to the change object and CQ will handle the tagging. > Need to see if the tags will be pushed by CQ as well or another component should be used (such as pusher.py) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2201: ------------------------------------- [~sbonazzo(a)redhat.com] I'll need some help to write the user stories for the requirements you state so we can properly evaluate and triage them. {quote} a way to quickly see if jobs are failing on a specific branch {quote} How about: "As an oVirt developer, I want to see the build status for the HEAD commit of a particular branch of my project so that I can <need to fill in reason here>" {quote} a way to consume builds from a specific branch {quote} "As an oVirt developer I want to have a way to acquire the lasted CI build on a particular branch on a particular project so that I can use it as a dependency for other jobs". About this last one - I guess we can ask people in devel if "tested" would be a good enough compromise? > [regression] STDCI v2 doesn't distinguish jobs for different branches > --------------------------------------------------------------------- > > Key: OVIRT-2201 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Standard CI (Pipelines) > Reporter: sbonazzo > Assignee: infra > > In V1 we had jobs with different name based on branches they were building. > In V2 we have single job building all branches. > As an example for imgbased: > https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBuil… > will contain randomly 4.2 or master builds. > This won't allow to filter jenkins to see which branches are failing to > build, forcing developers to check manually. > This also won't allow to check if latest build landed in tested repo > because thee build may be targeted to a different branch than the one under > check. > To me this is a regression that will make me rethink about the switching to > v2 and considering reverting to v1. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 92278,1 (ovirt-appliance) failed "ovirt-master" system tests
by oVirt Jenkins 18 Jun '18

18 Jun '18

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

2 1

[CQ]: 92278,1 (ovirt-appliance) failed "ovirt-master" system tests
by oVirt Jenkins 18 Jun '18

18 Jun '18

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

2 1

[CQ]: 92323,2 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 18 Jun '18

18 Jun '18

Change 92323,2 (ovirt-engine) 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/92323/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2431/

1 0

[CQ]: 92245,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 18 Jun '18

18 Jun '18

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

2 1

[JIRA] (OVIRT-2213) Cleaning up ISO in tested repo and keeping latest version
by Ehud Yonasi (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2213?page=com.atlassian.jira.… ] Ehud Yonasi reassigned OVIRT-2213: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > Cleaning up ISO in tested repo and keeping latest version > --------------------------------------------------------- > > Key: OVIRT-2213 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2213 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt Infra > Reporter: Ehud Yonasi > Assignee: Ehud Yonasi > > ISO images under tested repo got huge and require an automatic cleanup to free tested repo. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2213) Cleaning up ISO in tested repo and keeping latest version
by Ehud Yonasi (oVirt JIRA) 18 Jun '18

18 Jun '18

Ehud Yonasi created OVIRT-2213: ---------------------------------- Summary: Cleaning up ISO in tested repo and keeping latest version Key: OVIRT-2213 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2213 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt Infra Reporter: Ehud Yonasi Assignee: infra ISO images under tested repo got huge and require an automatic cleanup to free tested repo. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2213) Cleaning up ISO in tested repo and keeping latest version
by Ehud Yonasi (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2213?page=com.atlassian.jira.… ] Ehud Yonasi updated OVIRT-2213: ------------------------------- Epic Link: OVIRT-1744 > Cleaning up ISO in tested repo and keeping latest version > --------------------------------------------------------- > > Key: OVIRT-2213 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2213 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt Infra > Reporter: Ehud Yonasi > Assignee: infra > > ISO images under tested repo got huge and require an automatic cleanup to free tested repo. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 92245,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 18 Jun '18

18 Jun '18

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

2 1

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 253 - Failure!
by jenkins＠jenkins.phx.ovirt.org 18 Jun '18

18 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master… Build Number: 253 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #253 [Milan Zamazal] Make sure complete SS_PATH exists ----------------- Failed Tests: ----------------- All tests passed

1 2

[JIRA] (OVIRT-2212) Document the steps needed to add a new distro for CI slaves
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2212?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2212: ------------------------------------- Just so we don't forget - when we add a new distro we need to: # Create mirror sync jobs for it # Create a 'slave-repos' file in the 'jenkins' repo to force the slaves of that distro to use a particular mirror snapshot. > Document the steps needed to add a new distro for CI slaves > ----------------------------------------------------------- > > Key: OVIRT-2212 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2212 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation, Jenkins Slaves > Reporter: Evgheni Dereveanchin > Assignee: infra > > Adding a new distro/architecture to CI involves multiple steps like installing software, creating users, managing software mirrors. This process needs to be documented on ReadTheDocs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2212) Document the steps needed to add a new distro for CI slaves
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2212?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2212: -------------------------------- Component/s: Jenkins Slaves > Document the steps needed to add a new distro for CI slaves > ----------------------------------------------------------- > > Key: OVIRT-2212 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2212 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation, Jenkins Slaves > Reporter: Evgheni Dereveanchin > Assignee: infra > > Adding a new distro/architecture to CI involves multiple steps like installing software, creating users, managing software mirrors. This process needs to be documented on ReadTheDocs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2212) Document the steps needed to add a new distro for CI slaves
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2212?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2212: -------------------------------- Summary: Document the steps needed to add a new distro for CI slaves (was: Document the steps needed to add a new distro to CI) > Document the steps needed to add a new distro for CI slaves > ----------------------------------------------------------- > > Key: OVIRT-2212 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2212 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation > Reporter: Evgheni Dereveanchin > Assignee: infra > > Adding a new distro/architecture to CI involves multiple steps like installing software, creating users, managing software mirrors. This process needs to be documented on ReadTheDocs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2212) Document the steps needed to add a new distro to CI
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2212?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2212: -------------------------------- Component/s: Documentation > Document the steps needed to add a new distro to CI > --------------------------------------------------- > > Key: OVIRT-2212 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2212 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation > Reporter: Evgheni Dereveanchin > Assignee: infra > > Adding a new distro/architecture to CI involves multiple steps like installing software, creating users, managing software mirrors. This process needs to be documented on ReadTheDocs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2212) Document the steps needed to add a new distro to CI
by Evgheni Dereveanchin (oVirt JIRA) 18 Jun '18

18 Jun '18

Evgheni Dereveanchin created OVIRT-2212: ------------------------------------------- Summary: Document the steps needed to add a new distro to CI Key: OVIRT-2212 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2212 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Adding a new distro/architecture to CI involves multiple steps like installing software, creating users, managing software mirrors. This process needs to be documented on ReadTheDocs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2211) Add verification that the 'mock' GID is set to a proper value
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

Barak Korren created OVIRT-2211: ----------------------------------- Summary: Add verification that the 'mock' GID is set to a proper value Key: OVIRT-2211 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2211 Project: oVirt - virtualization made easy Issue Type: Outage Components: mock_runner, Standard CI (Pipelines) Reporter: Barak Korren Assignee: infra After having encountered OVIRT-2210, we want to detect such issues sooner next time we add a new slave OS. So we want to have the CI system pre-emptively verify the 'mock' GID is set to a proper value. There are two possible places we can do this: # In the 'check-patch' sage for the 'jenkins' repo # In {{global-setup.sh}} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2210) VDSM CI failes on all new FC28 slaves becaose of the 'mock' GID
by Evgheni Dereveanchin (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2210?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2210: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > VDSM CI failes on all new FC28 slaves becaose of the 'mock' GID > --------------------------------------------------------------- > > Key: OVIRT-2210 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2210 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: CI client projects, Jenkins Slaves > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Priority: Highest > > We see all check-patch jobs for VDSM failing when running on the new FC28 slaves, with an error like the following: > {code} > ERROR: Command failed: > # /usr/sbin/groupadd -g 1000 mock > {code} > The reason for this issue is that mock tries to have the 'mock' group have the same GID inside and outside of the mock environment. In the case of the new slaves the GID for the 'mock' group is 1000. Since 1000 is the 1st GID you get of you run 'groupadd' the probability of it colliding with any GID created by a package inside the 'mock' env is quite high. > In the case of the VDSM CI, the GID 1000 is taken by the 'openvswitch' package for the 'hugetlbfs' group. This on its own is a bug because no package should be taking GIDs beyond 1000, but having said that, the CI should not break on this, so we need to move the mock GID to below 1000 to a number that is unlikely to collide with others. > In the meantime all fc28 slaves will be disabled. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

CI fails on vdsm 4.2 branch
by Ala Hino 18 Jun '18

18 Jun '18

Something is odd ... I see that CI run only on RHEL (CentOS), but not on Fedora. Link to CI log: https://jenkins.ovirt.org/job/vdsm_4.2_check-patch-el7-x86_64/370/consoleFu… Link to patch: https://gerrit.ovirt.org/#/c/92309/

2 4

[JIRA] (OVIRT-2210) VDSM CI failes on all new FC28 slaves becaose of the 'mock' GID
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

Barak Korren created OVIRT-2210: ----------------------------------- Summary: VDSM CI failes on all new FC28 slaves becaose of the 'mock' GID Key: OVIRT-2210 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2210 Project: oVirt - virtualization made easy Issue Type: Outage Components: CI client projects, Jenkins Slaves Reporter: Barak Korren Assignee: infra Priority: Highest We see all check-patch jobs for VDSM failing when running on the new FC28 slaves, with an error like the following: {code} ERROR: Command failed: # /usr/sbin/groupadd -g 1000 mock {code} The reason for this issue is that mock tries to have the 'mock' group have the same GID inside and outside of the mock environment. In the case of the new slaves the GID for the 'mock' group is 1000. Since 1000 is the 1st GID you get of you run 'groupadd' the probability of it colliding with any GID created by a package inside the 'mock' env is quite high. In the case of the VDSM CI, the GID 1000 is taken by the 'openvswitch' package for the 'hugetlbfs' group. This on its own is a bug because no package should be taking GIDs beyond 1000, but having said that, the CI should not break on this, so we need to move the mock GID to below 1000 to a number that is unlikely to collide with others. In the meantime all fc28 slaves will be disabled. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 92263,1 (vdsm) failed "ovirt-4.2" system tests
by oVirt Jenkins 18 Jun '18

18 Jun '18

Change 92263,1 (vdsm) 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/92263/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2426/

2 1

CI failing: /usr/sbin/groupadd -g 1000 mock
by Nir Soffer 18 Jun '18

18 Jun '18

2 Fedora builds failed recently with this error: 19:40:34 ERROR: Command failed: 19:40:34 # /usr/sbin/groupadd -g 1000 mock See latest builds of this patch: https://gerrit.ovirt.org/#/c/91834/ I merged the patch regardless, but please take a look. Nir

3 3

[JIRA] (OVIRT-2209) Add mock version to the mock cache key
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

Barak Korren created OVIRT-2209: ----------------------------------- Summary: Add mock version to the mock cache key Key: OVIRT-2209 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2209 Project: oVirt - virtualization made easy Issue Type: Improvement Components: mock_runner Reporter: Barak Korren Assignee: infra Sometimes updates to mock make in incompatible with caches created by older versions. We should have the mock version be a part of the key used to retrieve cached mock environments. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2209) Add mock version to the mock cache key
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2209?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2209: -------------------------------- Epic Link: OVIRT-2189 > Add mock version to the mock cache key > -------------------------------------- > > Key: OVIRT-2209 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2209 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > > Sometimes updates to mock make in incompatible with caches created by older versions. We should have the mock version be a part of the key used to retrieve cached mock environments. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2208) Gate package changes on FC28 slaves
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2208?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2208: ----------------------------------- Assignee: Barak Korren (was: infra) > Gate package changes on FC28 slaves > ----------------------------------- > > Key: OVIRT-2208 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2208 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > We need to gate package changes on FC28 slaves just like we do on all other slaves. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2208) Gate package changes on FC28 slaves
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

Barak Korren created OVIRT-2208: ----------------------------------- Summary: Gate package changes on FC28 slaves Key: OVIRT-2208 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2208 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra Priority: Highest We need to gate package changes on FC28 slaves just like we do on all other slaves. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches
by sbonazzo (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-2201: --------------------------------- It covers ~90% of what we had in v1, it still miss: - a way to quickly see if jobs are failing on a specific branch - a way to consume builds from a specific branch (some jobs take latestSuccessfulBuild from Jenkins for building and this causes random branch selection based on last build). About this, maybe jobs should be changed for not consuming builders directly, but needs to track down them. > [regression] STDCI v2 doesn't distinguish jobs for different branches > --------------------------------------------------------------------- > > Key: OVIRT-2201 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Standard CI (Pipelines) > Reporter: sbonazzo > Assignee: infra > > In V1 we had jobs with different name based on branches they were building. > In V2 we have single job building all branches. > As an example for imgbased: > https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBuil… > will contain randomly 4.2 or master builds. > This won't allow to filter jenkins to see which branches are failing to > build, forcing developers to check manually. > This also won't allow to check if latest build landed in tested repo > because thee build may be targeted to a different branch than the one under > check. > To me this is a regression that will make me rethink about the switching to > v2 and considering reverting to v1. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 110 - Failure!
by jenkins＠jenkins.phx.ovirt.org 18 Jun '18

18 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/110/ Build Number: 110 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #110 [Milan Zamazal] Make sure complete SS_PATH exists ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2066) Re: Users list mail issue
by Marc Dequènes (Duck) (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2066?page=com.atlassian.jira.… ] Marc Dequènes (Duck) updated OVIRT-2066: ---------------------------------------- Resolution: Fixed Status: Done (was: To Do) Whoua, it's old. Also there was some latency due to greylisting, both on the new server and world's servers because the IP changed. Four hours seem a bit long though. I had no such complaints recently and all seem to work fine, so let's close. > Re: Users list mail issue > ------------------------- > > Key: OVIRT-2066 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2066 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: Marc Dequènes (Duck) > > Opening a ticket > On Wed, May 30, 2018, 18:39 Fred Rolland <frolland(a)redhat.com> wrote: > > Hi, > > > > It seems that I am receiving some emails from users list after a long > > delay. > > > > For example this thread: > > > > > > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/5N6N4BHF6ZFJLE… > > > > I have received only 2 emails from this thread, and my colleagues did not > > receive the one I sent 4 hours ago. > > > > > > Any idea what is the problem? > > > > Thanks, > > Freddy > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/6EKS6OYUQK7BK… > > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 522 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Jun '18

17 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/522/ Build Number: 522 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #522 [Milan Zamazal] Make sure complete SS_PATH exists [Barak Korren] Change V1 jobs for the 'jenkins' to not use fc26 [Sandro Bonazzola] ovirt-engine: drop scan_security_and_license job ----------------- Failed Tests: ----------------- All tests passed

1 1

[JIRA] (OVIRT-2204) A user request
by Galit Rosenthal (oVirt JIRA) 17 Jun '18

17 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2204?page=com.atlassian.jira.… ] Galit Rosenthal commented on OVIRT-2204: ---------------------------------------- I have access to the ovirt, I can see the projects/issues for exampe On Sun, Jun 17, 2018 at 11:36 AM, eyal edri (oVirt JIRA) < > A user request > -------------- > > Key: OVIRT-2204 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2204 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Galit Rosenthal > Assignee: infra > > Hi, > I will need a user to *Ovirt Jira system* > *Thanks* > *Galit* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 249 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Jun '18

17 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master… Build Number: 249 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #249 [Andrej Krejcir] HE: Test restarting HE VM ----------------- Failed Tests: ----------------- All tests passed

1 2