- Infra - oVirt List Archives

[JIRA] (OVIRT-1493) Update current DR documentation with info on storage setup
by Evgheni Dereveanchin (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1493?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1493: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Update current DR documentation with info on storage setup > ---------------------------------------------------------- > > Key: OVIRT-1493 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1493 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eedri > Assignee: Evgheni Dereveanchin > Priority: Highest > > Following the last outage on oVirt storage servers, it seems that we are missing more info on how to debug and fix issues on the storage service. > current documentation on http://ovirt-infra-docs.readthedocs.io/en/latest/Phoenix_Lab/Storage_Hosts/… only shows configuration but doesn't include troubleshooting like what can we check or do in case any of the services that make the storage work fails. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1494) RCA for PHX Storage outage on 29.06.2017
by Evgheni Dereveanchin (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1494?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1494: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > RCA for PHX Storage outage on 29.06.2017 > ---------------------------------------- > > Key: OVIRT-1494 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1494 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > The PHX storage stopped working around 5:40 GMT today and was brought up manually at 9:12 GMT by shutting down ovirt-storage02 and starting services on the remaining node. > ovirt-storage02 was the active cluster member and some unknown condition triggered a cluster failover attempt. This event however failed with all cluster resources going offline and not coming up on either of the nodes until one of them was shut down completely. > Opening this ticket to analyze logs and confirm what triggered the failover and why it eventually failed. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1494) RCA for PHX Storage outage on 29.06.2017
by Evgheni Dereveanchin (oVirt JIRA) 29 Jun '17

29 Jun '17

Evgheni Dereveanchin created OVIRT-1494: ------------------------------------------- Summary: RCA for PHX Storage outage on 29.06.2017 Key: OVIRT-1494 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1494 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra The PHX storage stopped working around 5:40 GMT today and was brought up manually at 9:12 GMT by shutting down ovirt-storage02 and starting services on the remaining node. ovirt-storage02 was the active cluster member and some unknown condition triggered a cluster failover attempt. This event however failed with all cluster resources going offline and not coming up on either of the nodes until one of them was shut down completely. Opening this ticket to analyze logs and confirm what triggered the failover and why it eventually failed. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1490) Simplify oVirt storage configuration
by Evgheni Dereveanchin (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1490?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1490: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Simplify oVirt storage configuration > ------------------------------------ > > Key: OVIRT-1490 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1490 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: storage > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Priority: Highest > Labels: infra, storage > > Today's outage was a clear reminder that our current storage configuration does not serve us well. We hardly know how to debug it, it seems to not be resistant to the very issues it was supposed to protect against and introduce potential failure scenarios of its own. > I suggest we implement a new storage layout that meets the following criteria: > # Ultimate simplicity at the lower level of the stack. More specifically: > ## The storage severs should be simple NFS or iSCSI servers. No DRBD and no exotic file-systems. > ## Only simple storage will be presented to oVirt for use as storage domains > # Separation of resources between critical services - The 'Jenkins" master for e.g. should not share resources with the "resources" server or anything else.The separation should hold true down to the physical spindle level. > # Duplication of services and use of local storage where possible - this is a longer term effort - but we have some low hanging fruits here like artifactory, where simple DNS/LB-based fail-over between two identical hosts would probably suffice. > # Complexity only where needed and up the stack. For example we can just have the storage for Jenkins be mirrored at the VM level with fail-over to a backup VM. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7397 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

------=_Part_121_563702351.1498676196725 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7397/, Build Number: 7397, Build Status: FAILURE ------=_Part_121_563702351.1498676196725--

1 2

[JIRA] (OVIRT-1490) Simplify oVirt storage configuration
by Barak Korren (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1490?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1490: -------------------------------- Summary: Simplify oVirt storage configuration (was: Simplify oVirt sotrage configuration) > Simplify oVirt storage configuration > ------------------------------------ > > Key: OVIRT-1490 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1490 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: storage > Reporter: Barak Korren > Assignee: infra > Priority: Highest > Labels: infra, storage > > Today's outage was a clear reminder that our current storage configuration does not serve us well. We hardly know how to debug it, it seems to not be resistant to the very issues it was supposed to protect against and introduce potential failure scenarios of its own. > I suggest we implement a new storage layout that meets the following criteria: > # Ultimate simplicity at the lower level of the stack. More specifically: > ## The storage severs should be simple NFS or iSCSI servers. No DRBD and no exotic file-systems. > ## Only simple storage will be presented to oVirt for use as storage domains > # Separation of resources between critical services - The 'Jenkins" master for e.g. should not share resources with the "resources" server or anything else.The separation should hold true down to the physical spindle level. > # Duplication of services and use of local storage where possible - this is a longer term effort - but we have some low hanging fruits here like artifactory, where simple DNS/LB-based fail-over between two identical hosts would probably suffice. > # Complexity only where needed and up the stack. For example we can just have the storage for Jenkins be mirrored at the VM level with fail-over to a backup VM. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #1783 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

------=_Part_60_1314560036.1498592982138 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1783/, Build Number: 1783, Build Status: FAILURE ------=_Part_60_1314560036.1498592982138--

1 8

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #480
by jenkins＠jenkins.phx.ovirt.org 29 Jun '17

29 Jun '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/480/displa…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/13/75913/5:patch --prune > git rev-parse origin/patch^{commit} # timeout=10 > git rev-parse patch^{commit} # timeout=10 Checking out Revision 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f (patch) > git config core.sparsecheckout # timeout=10 > git checkout -f 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f > git rev-list 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson2203138297466724195.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 96, in retrieveAllMD downloading = repo._commonRetrieveDataMD_list(mdtypes) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1609, in _commonRetrieveDataMD_list os.rename(local, local + '.old.tmp') OSError: [Errno 2] No such file or directory Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-1493) Update current DR documentation with info on storage setup
by eedri (oVirt JIRA) 29 Jun '17

29 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1493?page=com.atlassian.jira.… ] eedri updated OVIRT-1493: ------------------------- Epic Link: OVIRT-403 > Update current DR documentation with info on storage setup > ---------------------------------------------------------- > > Key: OVIRT-1493 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1493 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eedri > Assignee: infra > Priority: Highest > > Following the last outage on oVirt storage servers, it seems that we are missing more info on how to debug and fix issues on the storage service. > current documentation on http://ovirt-infra-docs.readthedocs.io/en/latest/Phoenix_Lab/Storage_Hosts/… only shows configuration but doesn't include troubleshooting like what can we check or do in case any of the services that make the storage work fails. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0

[JIRA] (OVIRT-1493) Update current DR documentation with info on storage setup
by eedri (oVirt JIRA) 29 Jun '17

29 Jun '17

eedri created OVIRT-1493: ---------------------------- Summary: Update current DR documentation with info on storage setup Key: OVIRT-1493 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1493 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eedri Assignee: infra Priority: Highest Following the last outage on oVirt storage servers, it seems that we are missing more info on how to debug and fix issues on the storage service. current documentation on http://ovirt-infra-docs.readthedocs.io/en/latest/Phoenix_Lab/Storage_Hosts/… only shows configuration but doesn't include troubleshooting like what can we check or do in case any of the services that make the storage work fails. -- This message was sent by Atlassian JIRA (v1000.1092.0#100053)

1 0