February 2019 - Infra - oVirt List Archives

[JIRA] (OVIRT-768) Decomission of MD5 Password Hashes for Infra Users
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-768?page=com.atlassian.jira.p… ] Anton Marchukov updated OVIRT-768: ---------------------------------- Resolution: Won't Fix Status: Done (was: To Do) > Decomission of MD5 Password Hashes for Infra Users > -------------------------------------------------- > > Key: OVIRT-768 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-768 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Anton Marchukov > Assignee: infra > > During the work of moving password parameters from foreman to internal > hiera I noted that there are some users that still have their passwords > hashed by MD5 algorithm. > MD5 has known crypto research that make it no longer suitable for storing > passwords securely: > https://en.wikipedia.org/wiki/MD5#Security (and corresponding links). > While the hashes are stored in internal repo it is still shared and prone > to information leaks. We should ask all users to rehash their passwords > with SHA-512 and when it is done we can remove MD5 exception > in site/ovirt_infra/manifests/user.pp so MD5 hashed passwords are no > longer accepted. > The current list of users left is available in infra-hiera repo. > -- > Anton Marchukov > Senior Software Engineer - RHEV CI - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-638) Tune Gerrit
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-638?page=com.atlassian.jira.p… ] Anton Marchukov updated OVIRT-638: ---------------------------------- Resolution: Won't Fix Status: Done (was: To Do) We will tune gerrit based on tickets listing specific problems. > Tune Gerrit > ----------- > > Key: OVIRT-638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-638 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Priority: Low > > We should probably tune Gerrit to take proper advantage of the bigger server we now have. > This could be useful: > http://ctf-dev-environment-vagrant.s3.amazonaws.com/Gerrit-Performance-Tuni… > Few notable details: > # Most RAM on the new server is currently taken by the FS cache instead of the Gerrit Java processes. > # It seems that the Gerrit can do Git garbage collection on its own, and do so more efficiently then doing so with the Git command line. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-497) [docs] Add documents on what's on the ci-tools repo and how it gets there
by Anton Marchukov (oVirt JIRA) 15 Feb '19

15 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-497?page=com.atlassian.jira.p… ] Anton Marchukov updated OVIRT-497: ---------------------------------- Resolution: Won't Fix Status: Done (was: To Do) > [docs] Add documents on what's on the ci-tools repo and how it gets there > ------------------------------------------------------------------------- > > Key: OVIRT-497 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-497 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: David Caro Estevez > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

oVirt infra daily report - unstable production jobs - 736
by jenkins＠jenkins.phx.ovirt.org 15 Feb '19

15 Feb '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/736//artifact/exported-a… Cheers, Jenkins

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 14 Feb '19

14 Feb '19

Failed to run project_setup.sh for: #3593 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-134z9.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 14 Feb '19

14 Feb '19

Failed to run project_setup.sh for: #3593 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-bvsbl.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 14 Feb '19

14 Feb '19

Failed to run project_setup.sh for: #3593 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-cl3ld.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 14 Feb '19

14 Feb '19

Failed to run project_setup.sh for: #3593 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-bg17w.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 14 Feb '19

14 Feb '19

Failed to run project_setup.sh for: #3591 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-wrmnr.

1 0

[CQ]: 97767, 1 (ovirt-vmconsole) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Feb '19

14 Feb '19

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

1 0