July 2018 - Infra - Ovirt List Archives

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2338?page=com.atlassian.jir... ] Dafna Ron updated OVIRT-2338: ----------------------------- Labels: ost_failures ost_infra (was: ) > resources got stuck > ------------------- > > Key: OVIRT-2338 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2338 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Emil Natan > Assignee: infra > Labels: ost_failures, ost_infra > > resources.ovirt.org got stuck. Initially we received different nagios alerts about number of processes and filesystems usage, but the root cause was "Socket timeout after 10 seconds". There was not ssh connectivity, so reset of the VM through the engine UI helped to get it running again. > The issue affected few CQ tests. > Possible improvement could be to set watchdog to automatically reboot the VM if it gets stuck. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2338) resources got stuck

by Emil Natan (oVirt JIRA)

Emil Natan created OVIRT-2338: --------------------------------- Summary: resources got stuck Key: OVIRT-2338 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2338 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Emil Natan Assignee: infra resources.ovirt.org got stuck. Initially we received different nagios alerts about number of processes and filesystems usage, but the root cause was "Socket timeout after 10 seconds". There was not ssh connectivity, so reset of the VM through the engine UI helped to get it running again. The issue affected few CQ tests. Possible improvement could be to set watchdog to automatically reboot the VM if it gets stuck. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

6 years, 4 months

1
0
0 / 0

[CQ]: 92835, 2 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests

by oVirt Jenkins

Change 92835,2 (ovirt-hosted-engine-setup) 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/92835/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8694/

6 years, 4 months

2
1
0 / 0

[CQ]: 82352, 28 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

6 years, 4 months

2
1
0 / 0

Build failed in Jenkins: deploy-to_ovirt-4.2_tested #1773

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/deploy-to_ovirt-4.2_tested/1773/display/redi...> ------------------------------------------ Started by upstream project "ovirt-release_4.2_build-artifacts-el7-x86_64" build number 356 originally caused by: Started by timer [EnvInject] - Loading node environment variables. Building remotely on vm0139.workers-phx.ovirt.org (phx fc28 nested) in workspace <http://jenkins.ovirt.org/job/deploy-to_ovirt-4.2_tested/ws/> [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-DupUy9XRUwVy/agent.30722 SSH_AGENT_PID=30724 [ssh-agent] Started. $ ssh-add <http://jenkins.ovirt.org/job/deploy-to_ovirt-4.2_tested/ws/@tmp/private_k...> Identity added: <http://jenkins.ovirt.org/job/deploy-to_ovirt-4.2_tested/ws/@tmp/private_k...> (<http://jenkins.ovirt.org/job/deploy-to_ovirt-4.2_tested/ws/@tmp/private_k...)> [ssh-agent] Using credentials deploy-ovirt-experimental (SSH key for deploying to the tested repo) [deploy-to_ovirt-4.2_tested] $ /bin/bash -xe /tmp/jenkins1093368437180442068.sh + [[ http://jenkins.ovirt.org/job/ovirt-release_4.2_build-artifacts-el7-x86_64... == '' ]] + queue_name=ovirt-4.2 + ssh -o StrictHostKeyChecking=no deploy-ovirt-experimental(a)resources.ovirt.org + echo repo-extra-dir:4.2 + echo http://jenkins.ovirt.org/job/ovirt-release_4.2_build-artifacts-el7-x86_64... Pseudo-terminal will not be allocated because stdin is not a terminal. ssh_exchange_identification: read: Connection reset by peer Build step 'Execute shell' marked build as failure $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 30724 killed; [ssh-agent] Stopped.

6 years, 4 months

1
1
0 / 0

[JIRA] (OVIRT-2335) Ensure SPICE traffic to PHX engine is not blocked by firewalls

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2335?page=com.atlassian.jir... ] Barak Korren updated OVIRT-2335: -------------------------------- Epic Link: OVIRT-2337 > Ensure SPICE traffic to PHX engine is not blocked by firewalls > -------------------------------------------------------------- > > Key: OVIRT-2335 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2335 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > In case we get locke out of servers, SPICE is our only option, only it seems to not work at all for now. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2335) Ensure SPICE traffic to PHX engine is not blocked by firewalls

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2335?page=com.atlassian.jir... ] Barak Korren updated OVIRT-2335: -------------------------------- Epic Link: OVIRT-2337 > Ensure SPICE traffic to PHX engine is not blocked by firewalls > -------------------------------------------------------------- > > Key: OVIRT-2335 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2335 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > In case we get locke out of servers, SPICE is our only option, only it seems to not work at all for now. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2336) Ensure the serial console for production VMs is reacahble

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2336?page=com.atlassian.jir... ] Barak Korren updated OVIRT-2336: -------------------------------- Epic Link: OVIRT-2337 > Ensure the serial console for production VMs is reacahble > --------------------------------------------------------- > > Key: OVIRT-2336 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2336 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: High > > Make sure everyone can reach the serial console for the production VMs (And know how to do it) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2336) Ensure the serial console for production VMs is reacahble

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2336?page=com.atlassian.jir... ] Barak Korren updated OVIRT-2336: -------------------------------- Epic Link: OVIRT-2337 > Ensure the serial console for production VMs is reacahble > --------------------------------------------------------- > > Key: OVIRT-2336 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2336 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: High > > Make sure everyone can reach the serial console for the production VMs (And know how to do it) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100089)

6 years, 4 months

1
0
0 / 0

[CQ]: 92782, 3 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

6 years, 4 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra July 2018