- Infra - oVirt List Archives

[JIRA] (OVIRT-1221) Unavialable projects in Gerrit
by Daniel Belenky (oVirt JIRA) 05 Mar '17

05 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1221?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1221: ---------------------------------- Description: Hi, We've encountered an issue where some projects (we've noticed only ovirt-engine project, but other projects might have been affected too) were unavailable from the gerrit ui. Clone with *ssh* was unavailable, but clone with *git* worked. After restarting the gerrit service, the issue resolved. [^error_log.tgz] We assume that the gerrit-exproll job ran, and maybe because that the ovirt-engine repo is much larger and others, something went wrong. [system_gerrit-exproll jenkins job log|http://jenkins.ovirt.org/job/system_gerrit-exproll/317/console] Attached is the gerrit error_log with the expetions was: Hi, We've encountered an issue where some projects (we've noticed only ovirt-engine project, but other projects might have been affected too) were unavailable from the gerrit ui. Clone with *ssh* was unavailable, but clone with *git* worked. After restarting the gerrit service, the issue resolved. [^error_log.tgz] We assume that the gerrit-exproll job ran, and maybe because that the ovirt-engine repo is much larger and others, something went wrong. [system_gerrit-exproll jenkins job log|http://jenkins.ovirt.org/job/system_gerrit-exproll/317/console] Attached the gerrit error_log with the expetions > Unavialable projects in Gerrit > ------------------------------ > > Key: OVIRT-1221 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1221 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: infra > Attachments: error_log.tgz > > > Hi, > We've encountered an issue where some projects (we've noticed only ovirt-engine project, but other projects might have been affected too) were unavailable from the gerrit ui. > Clone with *ssh* was unavailable, but clone with *git* worked. > After restarting the gerrit service, the issue resolved. [^error_log.tgz] > We assume that the gerrit-exproll job ran, and maybe because that the ovirt-engine repo is much larger and others, something went wrong. > [system_gerrit-exproll jenkins job log|http://jenkins.ovirt.org/job/system_gerrit-exproll/317/console] > Attached is the gerrit error_log with the expetions -- This message was sent by Atlassian JIRA (v1000.789.5#100032)

1 0

[JIRA] (OVIRT-1221) Unavialable projects in Gerrit
by Daniel Belenky (oVirt JIRA) 05 Mar '17

05 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1221?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1221: ---------------------------------- Description: Hi, We've encountered an issue where some projects (we've noticed only ovirt-engine project, but other projects might have been affected too) were unavailable from the gerrit ui. Clone with *ssh* was unavailable, but clone with *git* worked. After restarting the gerrit service, the issue resolved. [^error_log.tgz] We assume that the gerrit-exproll job ran, and maybe because that the ovirt-engine repo is much larger and others, something went wrong. [system_gerrit-exproll jenkins job log|http://jenkins.ovirt.org/job/system_gerrit-exproll/317/console] Attached the gerrit error_log with the expetions was: Hi, We've encountered an issue where some projects (we've noticed only ovirt-engine project, but other projects might have been affected too) were unavailable from the gerrit ui. Clone with *ssh* was unavailable, but clone with *git* worked. After restarting the gerrit service, the issue resolved. We assume that the gerrit-exproll job ran, and maybe because that the ovirt-engine repo is much larger and others, something went wrong. [system_gerrit-exproll jenkins job log|http://jenkins.ovirt.org/job/system_gerrit-exproll/317/console] gerrit error_log wit the exeptions: > Unavialable projects in Gerrit > ------------------------------ > > Key: OVIRT-1221 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1221 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: infra > Attachments: error_log.tgz > > > Hi, > We've encountered an issue where some projects (we've noticed only ovirt-engine project, but other projects might have been affected too) were unavailable from the gerrit ui. > Clone with *ssh* was unavailable, but clone with *git* worked. > After restarting the gerrit service, the issue resolved. [^error_log.tgz] > We assume that the gerrit-exproll job ran, and maybe because that the ovirt-engine repo is much larger and others, something went wrong. > [system_gerrit-exproll jenkins job log|http://jenkins.ovirt.org/job/system_gerrit-exproll/317/console] > Attached the gerrit error_log with the expetions -- This message was sent by Atlassian JIRA (v1000.789.5#100032)

1 0

[JIRA] (OVIRT-1221) Unavialable projects in Gerrit
by Daniel Belenky (oVirt JIRA) 05 Mar '17

05 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1221?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1221: ---------------------------------- Attachment: error_log.tgz > Unavialable projects in Gerrit > ------------------------------ > > Key: OVIRT-1221 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1221 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: infra > Attachments: error_log.tgz > > > Hi, > We've encountered an issue where some projects (we've noticed only ovirt-engine project, but other projects might have been affected too) were unavailable from the gerrit ui. > Clone with *ssh* was unavailable, but clone with *git* worked. > After restarting the gerrit service, the issue resolved. > We assume that the gerrit-exproll job ran, and maybe because that the ovirt-engine repo is much larger and others, something went wrong. > [system_gerrit-exproll jenkins job log|http://jenkins.ovirt.org/job/system_gerrit-exproll/317/console] > gerrit error_log wit the exeptions: -- This message was sent by Atlassian JIRA (v1000.789.5#100032)

1 0

[JIRA] (OVIRT-1221) Unavialable projects in Gerrit
by Daniel Belenky (oVirt JIRA) 05 Mar '17

05 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1221?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1221: ---------------------------------- Description: Hi, We've encountered an issue where some projects (we've noticed only ovirt-engine project, but other projects might have been affected too) were unavailable from the gerrit ui. Clone with *ssh* was unavailable, but clone with *git* worked. After restarting the gerrit service, the issue resolved. We assume that the gerrit-exproll job ran, and maybe because that the ovirt-engine repo is much larger and others, something went wrong. [system_gerrit-exproll jenkins job log|http://jenkins.ovirt.org/job/system_gerrit-exproll/317/console] gerrit error_log wit the exeptions: was: Hi, We've encountered an issue where some projects (we've noticed only ovirt-engine project, but other projects might have been affected too) were unavailable from the gerrit ui. Clone with *ssh* was unavailable, but clone with *git* worked. After restarting the gerrit service, the issue resolved. We assume that the gerrit-exproll job ran, and maybe because that the ovirt-engine repo is much larger and others, something went wrong. [system_gerrit-exproll jenkins job log|http://jenkins.ovirt.org/job/system_gerrit-exproll/317/console] gerrit error_log wit the exeptions: file:///home/dbelenky/wd/error_log.tgz > Unavialable projects in Gerrit > ------------------------------ > > Key: OVIRT-1221 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1221 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: infra > > Hi, > We've encountered an issue where some projects (we've noticed only ovirt-engine project, but other projects might have been affected too) were unavailable from the gerrit ui. > Clone with *ssh* was unavailable, but clone with *git* worked. > After restarting the gerrit service, the issue resolved. > We assume that the gerrit-exproll job ran, and maybe because that the ovirt-engine repo is much larger and others, something went wrong. > [system_gerrit-exproll jenkins job log|http://jenkins.ovirt.org/job/system_gerrit-exproll/317/console] > gerrit error_log wit the exeptions: -- This message was sent by Atlassian JIRA (v1000.789.5#100032)

1 0

[JIRA] (OVIRT-1221) Unavialable projects in Gerrit
by Daniel Belenky (oVirt JIRA) 05 Mar '17

05 Mar '17

Daniel Belenky created OVIRT-1221: ------------------------------------- Summary: Unavialable projects in Gerrit Key: OVIRT-1221 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1221 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Daniel Belenky Assignee: infra Hi, We've encountered an issue where some projects (we've noticed only ovirt-engine project, but other projects might have been affected too) were unavailable from the gerrit ui. Clone with *ssh* was unavailable, but clone with *git* worked. After restarting the gerrit service, the issue resolved. We assume that the gerrit-exproll job ran, and maybe because that the ovirt-engine repo is much larger and others, something went wrong. [system_gerrit-exproll jenkins job log|http://jenkins.ovirt.org/job/system_gerrit-exproll/317/console] gerrit error_log wit the exeptions: file:///home/dbelenky/wd/error_log.tgz -- This message was sent by Atlassian JIRA (v1000.789.5#100032)

1 0

[JIRA] (OVIRT-1220) infra-support emails are not opening tickets
by Gil Shinar (oVirt JIRA) 05 Mar '17

05 Mar '17

Gil Shinar created OVIRT-1220: --------------------------------- Summary: infra-support emails are not opening tickets Key: OVIRT-1220 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1220 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Gil Shinar Assignee: infra -- This message was sent by Atlassian JIRA (v1000.789.5#100032)

1 0

[JIRA] (OVIRT-1219) Pupulate staging jenkins
by Barak Korren (oVirt JIRA) 05 Mar '17

05 Mar '17

Barak Korren created OVIRT-1219: ----------------------------------- Summary: Pupulate staging jenkins Key: OVIRT-1219 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1219 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: Low The staging Jenkins instance currently contains only a few jobs that were created manually. These jobs do not resemble production jobs at all, nor is there any activity going on on that instance that simulates production work. We can populate the staging Jenkins instance with the following steps: # Setup the Gerrit plugin in the staging Jenkins to also listen to events from the production Gerrit. # Create a '{{staging-projects}}' directory on the '{{/jobs/confs}}' directory of the '{{jenkins}}' repo. This way the production YAML job templates can be used to create jobs in the staging Jenkins. # Create a '{{jenkins_master_deploy-configs_merged}}' job for the staging Jenkins that will deploy jobs from the directory mentioned above. The job template should probably be changed so that the name of the dorectory it will take jobs from will come from a global variable defined in the Jenkins server. # Create some Standard-CI dummy projects in the staging Gerrit. Setup jobs to occasionally submit random patches to these projects. -- This message was sent by Atlassian JIRA (v1000.789.5#100032)

1 0

[JIRA] (OVIRT-1219) Pupulate staging jenkins
by Barak Korren (oVirt JIRA) 05 Mar '17

05 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1219?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1219: -------------------------------- Epic Link: OVIRT-400 > Pupulate staging jenkins > ------------------------ > > Key: OVIRT-1219 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1219 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: Low > Labels: jenkins, staging > > The staging Jenkins instance currently contains only a few jobs that were created manually. These jobs do not resemble production jobs at all, nor is there any activity going on on that instance that simulates production work. > We can populate the staging Jenkins instance with the following steps: > # Setup the Gerrit plugin in the staging Jenkins to also listen to events from the production Gerrit. > # Create a '{{staging-projects}}' directory on the '{{/jobs/confs}}' directory of the '{{jenkins}}' repo. This way the production YAML job templates can be used to create jobs in the staging Jenkins. > # Create a '{{jenkins_master_deploy-configs_merged}}' job for the staging Jenkins that will deploy jobs from the directory mentioned above. The job template should probably be changed so that the name of the dorectory it will take jobs from will come from a global variable defined in the Jenkins server. > # Create some Standard-CI dummy projects in the staging Gerrit. Setup jobs to occasionally submit random patches to these projects. -- This message was sent by Atlassian JIRA (v1000.789.5#100032)

1 0

Unable to browse engine patches on gerrit
by Arik Hadas 05 Mar '17

05 Mar '17

Hi, There's an error while trying to browse patches in gerrit. It seems specific to patches for ovirt-engine, as patches for vdsm can be browsed just fine. For example, trying to open https://gerrit.ovirt.org/#/c/73140/ returns error 500. Please check. Thanks in advance.

2 1

[JIRA] (OVIRT-1218) Merge infra-docs into the 'jenkins' repo
by Barak Korren (oVirt JIRA) 05 Mar '17

05 Mar '17

Barak Korren created OVIRT-1218: ----------------------------------- Summary: Merge infra-docs into the 'jenkins' repo Key: OVIRT-1218 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1218 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra The 'jenkins' repo currently contains no documentation. The 'infra-docs' contains only docs, most of which deal with stuff that is in the 'jenkins' repo. Both repos are maintained by the exact same people (The oVirt infra team). Therefore it makes sense to unify these repos. Pros: * Easier discovery of docs for people looking to contribute to the 'jenkins' repo. * Can now enforce including documentation for new features in 'jenkins' repo. * Less repos to maintain for the infra team. -- This message was sent by Atlassian JIRA (v1000.789.5#100032)

1 0