- Infra - oVirt List Archives

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

08 Jul '18

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

1 0

Change in stdci-staging[master]: Dummy change to test nod allocation
by review＠gerrit-staging.phx.ovirt.org 08 Jul '18

08 Jul '18

From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/169 ) Change subject: Dummy change to test nod allocation ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/169 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stdci-staging Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Ibf51dc6db9a33094ad0bae6d2f0089d547cd5b8c Gerrit-Change-Number: 169 Gerrit-PatchSet: 1 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Sun, 08 Jul 2018 12:55:38 +0000 Gerrit-HasComments: No

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 102 - Failure!
by jenkins＠jenkins.phx.ovirt.org 08 Jul '18

08 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/10… Build Number: 102 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #102 [Sandro Bonazzola] master: consume qemu-kvm-ev test builds ----------------- Failed Tests: ----------------- All tests passed

1 4

[JIRA] (OVIRT-2134) Investigate why HC suites fail on slaves with *-IBRS CPU
by Gal Ben Haim (oVirt JIRA) 08 Jul '18

08 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2134?page=com.atlassian.jira.… ] Gal Ben Haim reassigned OVIRT-2134: ----------------------------------- Assignee: Gal Ben Haim (was: infra) > Investigate why HC suites fail on slaves with *-IBRS CPU > -------------------------------------------------------- > > Key: OVIRT-2134 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2134 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: Gal Ben Haim > > The HC suites work just fine on "ovirt-srv05.phx.ovirt.org". while failing on "ovirt-srv21.phx.ovirt.org" and "ovirt-srv18.phx.ovirt.org". > One thing that I've noticed is the difference between the CPU types on those slaves: > ovirt-srv05.phx.ovirt.org - IvyBridge > ovirt-srv21.phx.ovirt.org and ovirt-srv18.phx.ovirt.org - Haswell-noTSX-IBRS > Together with [1], I have a strong feeling that this is the issue. > [1] - https://gerrit.ovirt.org/#/c/90542/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2282) use SSH keys from gerrit for infra users
by Barak Korren (oVirt JIRA) 08 Jul '18

08 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2282?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-2282 at 7/8/18 11:50 AM: -------------------------------------------------------------- {quote} just my set of thoughts, if we have an automation management product, why not utilize it? {quote} Because there is a huge overhead to doing so and very little, if any, benefit. In this case it will also significantly reduce system reliability, for the cron job to work all you need is: # Cron to be configured # The script to run # A network connection to Gerrit With Ansible OTOH you need: # A way to trigger it - as you mention, but this is a Gerrit group, there is no built-in mechanism for triggering when it is changed, so now you'll need some kind of (Jenkins?) job to poll it. # A host to run Ansible from # Network connectivity and SSH permissions from this host to all other hosts # # Network connectivity and SSH permissions from this host to Gerrit # An inventory you need to maintain (as you mention), or build more automation around. So many moving parts you'd need to create and maintain... and then you expect it to be reliable enough that youre ability to login will depend on it... really I can't see how Ansible makes sense here., was (Author: bkorren(a)redhat.com) {quote} just my set of thoughts, if we have an automation management product, why not utilize it? {quote} Because there is a huge overhead to doing so and very little, if any, benefit. In this case it will also significantly reduce system reliability, for the cron job to work all you need is: # Cron to be configured # The script to run # A network connection to Gerrit With Ansible OTOH you need: # A way to trigger it - as you mention, but this is a Gerrit group, there is no built-in mechanism for triggering when it is changed, so now you'll need some kind of (Jenkins?) job to poll it. # A host to run Ansible from # Network connectivity and SSH permissions from this host to all other hosts # An inventory you need to maintain (as you mention), or build more automation around. So many moving parts you'd need to create and maintain... and then you expect it to be reliable enough that youre ability to login will depend on it... really I can't see how Ansible makes sense here., > use SSH keys from gerrit for infra users > ---------------------------------------- > > Key: OVIRT-2282 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2282 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > Opening ticket to discuss possibility of managing user accounts through gerrit as it has SSH pubkeys defined. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2282) use SSH keys from gerrit for infra users
by Barak Korren (oVirt JIRA) 08 Jul '18

08 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2282?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2282: ------------------------------------- {quote} just my set of thoughts, if we have an automation management product, why not utilize it? {quote} Because there is a huge overhead to doing so and very little, if any, benefit. In this case it will also significantly reduce system reliability, for the cron job to work all you need is: # Cron to be configured # The script to run # A network connection to Gerrit With Ansible OTOH you need: # A way to trigger it - as you mention, but this is a Gerrit group, there is no built-in mechanism for triggering when it is changed, so now you'll need some kind of (Jenkins?) job to poll it. # A host to run Ansible from # Network connectivity and SSH permissions from this host to all other hosts # An inventory you need to maintain (as you mention), or build more automation around. So many moving parts you'd need to create and maintain... and then you expect it to be reliable enough that youre ability to login will depend on it... really I can't see how Ansible makes sense here., > use SSH keys from gerrit for infra users > ---------------------------------------- > > Key: OVIRT-2282 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2282 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > Opening ticket to discuss possibility of managing user accounts through gerrit as it has SSH pubkeys defined. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[CQ]: 92823,2 (vdsm) failed "ovirt-4.2" system tests
by oVirt Jenkins 08 Jul '18

08 Jul '18

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

3 3

[JIRA] (OVIRT-2282) use SSH keys from gerrit for infra users
by Ehud Yonasi (oVirt JIRA) 08 Jul '18

08 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2282?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2282: ------------------------------------ I think we should use ansible playbook to run the script 1) use ansible playbook to run the scripts (req user for ssh, maybe we can use jenkins / secret file) 2) trigger the playbook each time that file changes (/etc/group ?), if so run a script that checks if infra-group was changed. 3) to maintain the inventory, we can use a jenkins job that checks on a daily basis if new hosts were added or use other triggers, and if so push a change to inventory and trigger the playbook. just my set of thoughts, if we have an automation management product, why not utilize it? > use SSH keys from gerrit for infra users > ---------------------------------------- > > Key: OVIRT-2282 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2282 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > Opening ticket to discuss possibility of managing user accounts through gerrit as it has SSH pubkeys defined. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[ CQ Failure Report ] [ RHV Master - ds vdsm ] [ 07-07-2018 ] [ post-004_basic_sanity.py ]
by Ehud Yonasi 08 Jul '18

08 Jul '18

Link to suspected patches: https://gerrit.ovirt.org/#/c/92694/ Link to the job: https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhv-master_c… Link to all logs: https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhv-master_c… (Relevant) error snippet from the log: <error> 2018-07-07 09:47:23,755-04 WARN [org.ovirt.engine.core.bll.AddVmFromScratchCommand] (default task-23) [] Validation of action 'AddVmFromScratch' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__VM,ACTION_TYPE_FAILED_NAME_ALREADY_USED 2018-07-07 09:47:23,756-04 INFO [org.ovirt.engine.core.bll.AddVmFromScratchCommand] (default task-23) [] Lock freed to object 'EngineLock:{exclusiveLocks='[vm0=VM_NAME]', sharedLocks=''}' 2018-07-07 09:47:23,774-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-23) [] method: runAction, params: [AddVmFromScratch, AddVmParameters:{commandId='720f8857-26e1-4ce2-8afd-6297372a27e9', user='null', commandType='Unknown', vmId='a8064ee0-dc9f-47cc-b211-29d2e8b14873'}], timeElapsed: 121ms 2018-07-07 09:47:23,781-04 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-23) [] Operation Failed: [Cannot add VM. The VM name is already in use, please choose a unique name and try again.] </error>

1 0

[JIRA] (OVIRT-2282) use SSH keys from gerrit for infra users
by Barak Korren (oVirt JIRA) 08 Jul '18

08 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2282?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2282: ------------------------------------- As discussed in an infra meeting the approach I think we should take here is to: # Have a group in Gerrit that defines who the infra team members are # Have a shell script that lists members of that group (can be done with {{ssh ... gerrit ls-members}}) and ## either: ### Create local accounts for those members ### Download SSH public keys from Gerrit and install in those accounts ### setup password-less sudo for those accounts ## or: ### Download SSH public keys from Gerrit and install in the root acocunt # Run that shell script from cron every 30 minutes on all slaves. # Setup this script and cron job on the slave via cloud-init. # On non-slave hosts we can choose to setup the script and cron job Discussion about why IMO it should be a script and not Ansible/Puppet/Some other thing: # This needs to be run locally on every slave - so doing this with a tool will require having that tool be pre-installed on the slave. # Arguments for using a tool may include the reasoning that it may be easier to add more functionality over time if we use a tool. My counter argument is that we're very much unlikely to add any more functionality, as most if not all other changes we may wish to make to a slave can affect the CI systems and therefore are better done in sync with it via {{globale_setup.sh}}, etc. > use SSH keys from gerrit for infra users > ---------------------------------------- > > Key: OVIRT-2282 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2282 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > Opening ticket to discuss possibility of managing user accounts through gerrit as it has SSH pubkeys defined. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0