- Infra - oVirt List Archives

[JIRA] (OVIRT-1393) b
by Barak Korren (oVirt JIRA) 21 May '17

21 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1393?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1393: -------------------------------- Epic Link: OVIRT-400 > b > - > > Key: OVIRT-1393 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1393 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Barak Korren > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1393) b
by Barak Korren (oVirt JIRA) 21 May '17

21 May '17

Barak Korren created OVIRT-1393: ----------------------------------- Summary: b Key: OVIRT-1393 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1393 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Barak Korren Assignee: infra -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1392) Upgrade job config history plugin
by Gil Shinar (oVirt JIRA) 21 May '17

21 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1392?page=com.atlassian.jira.… ] Gil Shinar reassigned OVIRT-1392: --------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Upgrade job config history plugin > --------------------------------- > > Key: OVIRT-1392 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1392 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Evgheni Dereveanchin > > Job config history plugin version 2.12 has a [bug|https://issues.jenkins-ci.org/browse/JENKINS-33289] when clicking on show diffs. > Please upgrade to at least 2.13 (latest preferable). -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1392) Upgrade job config history plugin
by Gil Shinar (oVirt JIRA) 21 May '17

21 May '17

Gil Shinar created OVIRT-1392: --------------------------------- Summary: Upgrade job config history plugin Key: OVIRT-1392 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1392 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra Job config history plugin version 2.12 has a [bug|https://issues.jenkins-ci.org/browse/JENKINS-33289] when clicking on show diffs. Please upgrade to at least 2.13 (latest preferable). -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1391) Add repo injection capabilities to STD-CI
by Barak Korren (oVirt JIRA) 21 May '17

21 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1391?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1391: -------------------------------- Labels: containers mock_runner.sh standard-ci (was: ) > Add repo injection capabilities to STD-CI > ----------------------------------------- > > Key: OVIRT-1391 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1391 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: containers, mock_runner.sh, standard-ci > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. > We want to add to standard-CI ('{{mock-runner.sh}}') the capability to provide a project with information about package repositories that unrelated to the setup of the environment that standard-CI scripts run in. > A projects will specify required repositories by including one or more files that match the pattern “{{automation/$STD_CI_STAGE.\*.yumrepos.\*}}”, where “{{$STG_CI_STAGE}}” is e.g “{{build-system-artifacts}}” and the wildcard sections can be omitted along with the dots that precede them. The file should be in the format of a yum configuration file and include configuration for required yum repositories. To avoid the projects having to maintain URLs for yum repositories, the file may contain configurations without repository URLs specified and with the “skip_if_unavailable” parameter set to “true”. Only the names of the repository configuration sections will be meaningful for the purpose of the CI system. For each such file the CI system will: > # Replace any configuration section that defines the “{{ovirt-<distro-id>}}” repository with one or more configuration sections pointing to repositories from which oVirt packages for the distribution identified by "{{<distro-id>}}" may be obtained. “{{<distro-id>}}" will be a string such as “el7” or “fc25”. To allow avoiding collisions with the released oVirt yum configuration, the “{{ovirt-ci-<repoid>}}” and “{{ovirt-experimental-<repoid>}}” configuration section will be treated the same way. > # Replace any configuration section that defines the “{{ovirt-dependencies-<distro-id>}}” repository with one or more configuration sections pointing to repositories from which oVirt dependency packages need to be obtained. These will include, among others, base operating system packages. The “{{ovirt-ci-dependencies-<repoid>}}” and “{{ovirt-experimental-dependencies-<repoid>}}” configuration section will be treated the same way. > # Run the mirror injection process. Any repository handled by this process will have the the “{{skip_if_unavailable}}” parameter removed if specified (To make the default value of “{{false}}” come into effect). > # Prepend a “{{\[main]}}” section that disables the use of the “{{/etc/yum.repos.d}}” directory. This will allow the file to appended to the "{{/etc/yun.conf}}” file to automatically disable all internet-facing preconfigured repositories. > To allow automation scripts to find the repository files prepared for them, several environment variables will be made available in the Standard-CI runtime environment: > # {{STD_CI_STAGE}}: Will contain the name of the Standard-CI stage, e.g. “{{build-artifacts}}”. > # {{STD_CI_DISTRO}}: Will contain the distribution version identifier (e.g “el7” or “fc25”) of the Standard-CI runtime. > # {{STD_CI_YUMREPOS}}: Will point to an existing “{{*.yumrepos}}” file that most closely matches the current running stage and distribution -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

Change in ds-jenkins-stg[master]: Insert the description of the change.
by review＠gerrit-staging.phx.ovirt.org 21 May '17

21 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Insert the description of the change. ...................................................................... Insert the description of the change. Change-Id: I71bd36edae9efcba79ee001bb20d8a0480d36df9 --- M automation/upstream_sources.yaml 1 file changed, 0 insertions(+), 3 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/38 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I71bd36edae9efcba79ee001bb20d8a0480d36df9 Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in ds-jenkins-stg[master]: Insert the description of the change.
by review＠gerrit-staging.phx.ovirt.org 21 May '17

21 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Insert the description of the change. ...................................................................... Insert the description of the change. Change-Id: I23bf65014b013282cfb61a0d732285f318803f41 --- M automation/upstream_sources.yaml 1 file changed, 0 insertions(+), 3 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/37 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I23bf65014b013282cfb61a0d732285f318803f41 Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in ds-jenkins-stg[master]: Insert the description of the change.
by review＠gerrit-staging.phx.ovirt.org 21 May '17

21 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Insert the description of the change. ...................................................................... Insert the description of the change. Change-Id: I9c80ced54f721c80a8144889be3c96e1e0a20950 --- M automation/upstream_sources.yaml 1 file changed, 3 insertions(+), 0 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/36 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I9c80ced54f721c80a8144889be3c96e1e0a20950 Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #1501 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 21 May '17

21 May '17

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

1 2

Change in ds-jenkins-stg[master]: Insert the description of the change.
by review＠gerrit-staging.phx.ovirt.org 21 May '17

21 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Insert the description of the change. ...................................................................... Insert the description of the change. Change-Id: Ic0163e4fbc00c2836a3434bee950f93d69151ff4 --- M automation/upstream_sources.yaml 1 file changed, 0 insertions(+), 3 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/35 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: Ic0163e4fbc00c2836a3434bee950f93d69151ff4 Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in ds-jenkins-stg[master]: Insert the description of the change.
by review＠gerrit-staging.phx.ovirt.org 21 May '17

21 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Insert the description of the change. ...................................................................... Insert the description of the change. Change-Id: Iac3ff98a17763419192fbec0d08344d026146194 --- M automation/upstream_sources.yaml 1 file changed, 5 insertions(+), 2 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/34 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: Iac3ff98a17763419192fbec0d08344d026146194 Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in us-jenkins-stg3[master]: initializing
by review＠gerrit-staging.phx.ovirt.org 21 May '17

21 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: initializing ...................................................................... initializing Change-Id: I6b17e9c20df31caadb0bd46114345cfcb77f0463 --- A e A f 2 files changed, 0 insertions(+), 0 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/33 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I6b17e9c20df31caadb0bd46114345cfcb77f0463 Gerrit-PatchSet: 1 Gerrit-Project: us-jenkins-stg3 Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in us-jenkins-stg3[master]: initializing
by review＠gerrit-staging.phx.ovirt.org 21 May '17

21 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has posted comments on this change. Change subject: initializing ...................................................................... Patch Set 1: Code-Review+2 Continuous-Integration+1 Verified+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/33 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I6b17e9c20df31caadb0bd46114345cfcb77f0463 Gerrit-PatchSet: 1 Gerrit-Project: us-jenkins-stg3 Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

Change in ds-jenkins-stg[master]: Insert the description of the change.
by review＠gerrit-staging.phx.ovirt.org 21 May '17

21 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Insert the description of the change. ...................................................................... Insert the description of the change. Change-Id: I6fc9184afe2133b9fc789d90d7d646e59341cc88 --- M automation/upstream_sources.yaml 1 file changed, 2 insertions(+), 2 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/32 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I6fc9184afe2133b9fc789d90d7d646e59341cc88 Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in ds-jenkins-stg[master]: Insert the description of the change.
by review＠gerrit-staging.phx.ovirt.org 21 May '17

21 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has posted comments on this change. Change subject: Insert the description of the change. ...................................................................... Patch Set 2: Code-Review+2 Continuous-Integration+1 Verified+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/32 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I6fc9184afe2133b9fc789d90d7d646e59341cc88 Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

[JIRA] (OVIRT-1391) Add repo injection capabilities to STD-CI
by Barak Korren (oVirt JIRA) 21 May '17

21 May '17

Barak Korren created OVIRT-1391: ----------------------------------- Summary: Add repo injection capabilities to STD-CI Key: OVIRT-1391 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1391 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: High This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. We want to add to standard-CI ('{{mock-runner.sh}}') the capability to provide a project with information about package repositories that unrelated to the setup of the environment that standard-CI scripts run in. A projects will specify required repositories by including one or more files that match the pattern “{{automation/$STD_CI_STAGE.\*.yumrepos.\*}}”, where “{{$STG_CI_STAGE}}” is e.g “{{build-system-artifacts}}” and the wildcard sections can be omitted along with the dots that precede them. The file should be in the format of a yum configuration file and include configuration for required yum repositories. To avoid the projects having to maintain URLs for yum repositories, the file may contain configurations without repository URLs specified and with the “skip_if_unavailable” parameter set to “true”. Only the names of the repository configuration sections will be meaningful for the purpose of the CI system. For each such file the CI system will: # Replace any configuration section that defines the “{{ovirt-<distro-id>}}” repository with one or more configuration sections pointing to repositories from which oVirt packages for the distribution identified by "{{<distro-id>}}" may be obtained. “{{<distro-id>}}" will be a string such as “el7” or “fc25”. To allow avoiding collisions with the released oVirt yum configuration, the “{{ovirt-ci-<repoid>}}” and “{{ovirt-experimental-<repoid>}}” configuration section will be treated the same way. # Replace any configuration section that defines the “{{ovirt-dependencies-<distro-id>}}” repository with one or more configuration sections pointing to repositories from which oVirt dependency packages need to be obtained. These will include, among others, base operating system packages. The “{{ovirt-ci-dependencies-<repoid>}}” and “{{ovirt-experimental-dependencies-<repoid>}}” configuration section will be treated the same way. # Run the mirror injection process. Any repository handled by this process will have the the “{{skip_if_unavailable}}” parameter removed if specified (To make the default value of “{{false}}” come into effect). # Prepend a “{{\[main]}}” section that disables the use of the “{{/etc/yum.repos.d}}” directory. This will allow the file to appended to the "{{/etc/yun.conf}}” file to automatically disable all internet-facing preconfigured repositories. To allow automation scripts to find the repository files prepared for them, several environment variables will be made available in the Standard-CI runtime environment: # {{STD_CI_STAGE}}: Will contain the name of the Standard-CI stage, e.g. “{{build-artifacts}}”. # {{STD_CI_DISTRO}}: Will contain the distribution version identifier (e.g “el7” or “fc25”) of the Standard-CI runtime. # {{STD_CI_YUMREPOS}}: Will point to an existing “{{*.yumrepos}}” file that most closely matches the current running stage and distribution -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1391) Add repo injection capabilities to STD-CI
by Barak Korren (oVirt JIRA) 21 May '17

21 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1391?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1391: -------------------------------- Epic Link: OVIRT-400 > Add repo injection capabilities to STD-CI > ----------------------------------------- > > Key: OVIRT-1391 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1391 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. > We want to add to standard-CI ('{{mock-runner.sh}}') the capability to provide a project with information about package repositories that unrelated to the setup of the environment that standard-CI scripts run in. > A projects will specify required repositories by including one or more files that match the pattern “{{automation/$STD_CI_STAGE.\*.yumrepos.\*}}”, where “{{$STG_CI_STAGE}}” is e.g “{{build-system-artifacts}}” and the wildcard sections can be omitted along with the dots that precede them. The file should be in the format of a yum configuration file and include configuration for required yum repositories. To avoid the projects having to maintain URLs for yum repositories, the file may contain configurations without repository URLs specified and with the “skip_if_unavailable” parameter set to “true”. Only the names of the repository configuration sections will be meaningful for the purpose of the CI system. For each such file the CI system will: > # Replace any configuration section that defines the “{{ovirt-<distro-id>}}” repository with one or more configuration sections pointing to repositories from which oVirt packages for the distribution identified by "{{<distro-id>}}" may be obtained. “{{<distro-id>}}" will be a string such as “el7” or “fc25”. To allow avoiding collisions with the released oVirt yum configuration, the “{{ovirt-ci-<repoid>}}” and “{{ovirt-experimental-<repoid>}}” configuration section will be treated the same way. > # Replace any configuration section that defines the “{{ovirt-dependencies-<distro-id>}}” repository with one or more configuration sections pointing to repositories from which oVirt dependency packages need to be obtained. These will include, among others, base operating system packages. The “{{ovirt-ci-dependencies-<repoid>}}” and “{{ovirt-experimental-dependencies-<repoid>}}” configuration section will be treated the same way. > # Run the mirror injection process. Any repository handled by this process will have the the “{{skip_if_unavailable}}” parameter removed if specified (To make the default value of “{{false}}” come into effect). > # Prepend a “{{\[main]}}” section that disables the use of the “{{/etc/yum.repos.d}}” directory. This will allow the file to appended to the "{{/etc/yun.conf}}” file to automatically disable all internet-facing preconfigured repositories. > To allow automation scripts to find the repository files prepared for them, several environment variables will be made available in the Standard-CI runtime environment: > # {{STD_CI_STAGE}}: Will contain the name of the Standard-CI stage, e.g. “{{build-artifacts}}”. > # {{STD_CI_DISTRO}}: Will contain the distribution version identifier (e.g “el7” or “fc25”) of the Standard-CI runtime. > # {{STD_CI_YUMREPOS}}: Will point to an existing “{{*.yumrepos}}” file that most closely matches the current running stage and distribution -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1390) Implement "archive-artifacts" flow for containers in STD-CI
by Barak Korren (oVirt JIRA) 21 May '17

21 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1390?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1390: ----------------------------------- Assignee: Daniel Belenky (was: infra) > Implement "archive-artifacts" flow for containers in STD-CI > ----------------------------------------------------------- > > Key: OVIRT-1390 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1390 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: Daniel Belenky > Priority: High > Labels: standard-ci > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. > We want to implement functionality similar to what "archive-artifacts" gives use for regular files, for containers in standard-CI. > The design as as following: > # An STD-CI script that generated container images need to tag them with the "exported-artifacts" tag. > # After the STD-CI script finishes successfully, the CI system will take the tagged container images and push them the the "{{ovirtinfra}}" account on DockerHub. > # The CI system will tage pushed images with the SHA1 hash of the URL of the Jenkins job build that built the image (Can be found in $BUILD_URL) > # The CI system will output examples for '{{docker pull}}' and '{{docker run}}' command that would be needed to obtain the build image to the build status screen (Using the Groovy post-build plugin) -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1390) Implement "archive-artifacts" flow for containers in STD-CI
by Barak Korren (oVirt JIRA) 21 May '17

21 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1390?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1390: -------------------------------- Description: This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. We want to implement functionality similar to what "archive-artifacts" gives use for regular files, for containers in standard-CI. The design as as following: # An STD-CI script that generated container images need to tag them with the "exported-artifacts" tag. # After the STD-CI script finishes successfully, the CI system will take the tagged container images and push them the the "{{ovirtinfra}}" account on DockerHub. # The CI system will tage pushed images with the SHA1 hash of the URL of the Jenkins job build that built the image (Can be found in $BUILD_URL) # The CI system will output examples for '{{docker pull}}' and '{{docker run}}' command that would be needed to obtain the build image to the build status screen (Using the Groovy post-build plugin) was: This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. We want to implement functionality similar to what "archive-artifacts" gives use for regular files, for containers in standard-CI. The design as as following: # An STD-CI script that generated container images need to tag them with the "exported-artifacts" tag. # After the STD-CI script finishes successfully, the CI system will take the tagged container images and push them the the "ovirtinfra" account on DockerHub. # The CI system will tage pushed images with the SHA1 hash of the URL of the Jenkins job build that built the image (Can be found in $BUILD_URL) # The CI system will output examples for '{{docker pull}}' and '{{docker run}}' command that would be needed to obtain the build image to the build status screen (Using the Groovy post-build plugin) > Implement "archive-artifacts" flow for containers in STD-CI > ----------------------------------------------------------- > > Key: OVIRT-1390 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1390 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: standard-ci > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. > We want to implement functionality similar to what "archive-artifacts" gives use for regular files, for containers in standard-CI. > The design as as following: > # An STD-CI script that generated container images need to tag them with the "exported-artifacts" tag. > # After the STD-CI script finishes successfully, the CI system will take the tagged container images and push them the the "{{ovirtinfra}}" account on DockerHub. > # The CI system will tage pushed images with the SHA1 hash of the URL of the Jenkins job build that built the image (Can be found in $BUILD_URL) > # The CI system will output examples for '{{docker pull}}' and '{{docker run}}' command that would be needed to obtain the build image to the build status screen (Using the Groovy post-build plugin) -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1390) Implement "archive-artifacts" flow for containers in STD-CI
by Barak Korren (oVirt JIRA) 21 May '17

21 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1390?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1390: -------------------------------- Description: This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. We want to implement functionality similar to what "archive-artifacts" gives use for regular files, for containers in standard-CI. The design as as following: # An STD-CI script that generated container images need to tag them with the "exported-artifacts" tag. # After the STD-CI script finishes successfully, the CI system will take the tagged container images and push them the the "ovirtinfra" account on DockerHub. # The CI system will tage pushed images with the SHA1 hash of the URL of the Jenkins job build that built the image (Can be found in $BUILD_URL) # The CI system will output examples for '{{docker pull}}' and '{{docker run}}' command that would be needed to obtain the build image to the build status screen (Using the Groovy post-build plugin) was: This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. We want to implement functionality similar to what "archive-artifacts" gives use for regular files, for containers in standard-CI. The design as as following: # An STD-CI script that generated container images need to tag them with the "exported-artifacts" tag. # After the STD-CI script finishes successfully, the CI system will take the tagged container images and push them the the "ovirtci" account on DockerHub. # The CI system will tage pushed images with the SHA1 hash of the URL of the Jenkins job build that built the image (Can be found in $BUILD_URL) # The CI system will output examples for '{{docker pull}}' and '{{docker run}}' command that would be needed to obtain the build image to the build status screen (Using the Groovy post-build plugin) > Implement "archive-artifacts" flow for containers in STD-CI > ----------------------------------------------------------- > > Key: OVIRT-1390 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1390 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: standard-ci > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. > We want to implement functionality similar to what "archive-artifacts" gives use for regular files, for containers in standard-CI. > The design as as following: > # An STD-CI script that generated container images need to tag them with the "exported-artifacts" tag. > # After the STD-CI script finishes successfully, the CI system will take the tagged container images and push them the the "ovirtinfra" account on DockerHub. > # The CI system will tage pushed images with the SHA1 hash of the URL of the Jenkins job build that built the image (Can be found in $BUILD_URL) > # The CI system will output examples for '{{docker pull}}' and '{{docker run}}' command that would be needed to obtain the build image to the build status screen (Using the Groovy post-build plugin) -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1376) Make mock_runner.sh easier to use locally
by Barak Korren (oVirt JIRA) 21 May '17

21 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1376?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1376: -------------------------------- Summary: Make mock_runner.sh easier to use locally (was: Make mock_runner.sh easer to use locally) > Make mock_runner.sh easier to use locally > ----------------------------------------- > > Key: OVIRT-1376 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1376 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: Low > > Currently to use '{{mock_runner.sh}}', one needs to: > # Install '{{mock}}' (Might require adding some '{{yum}}' repos, also reuquires one to be running RHEL, CentOS or Fedora in the 1st place) > # Add one`s user account to the '{{mock}}' group (requires logoff and logon) > # Clone the '{{jenkins}}' repo > # Use a long set of command line arguments to make '{{mock_runner.sh}}' use the right '{{mock}}' configuration files > All this is making '{{mock_runner.sh}}' hard and unpopular for local use. Also, no knowing one need to do the above leads to strange errors. We can improve this by: > # Making '{{mock_runner.sh}' check that everything is configured correctly and output meaningful warnings otherwise > # Setup the default so that '{{mock_runner.sh}}' knows how the find the right configuration files > # Package '{{mock_runner.sh}}' in one way or another so that one doesn't need to clone a whole repo to install it. > When it comes to packaging we have several options to consider: > * Using an RPM package: > ** Pros: > *** Familiar format > *** Can include '{{mock}}' as a dependency. > ** Cons: > *** One has to use CentOS or Fedora > *** One most have '{{root}}' permissions to install packages > * Using a self-contained executable built with a tool like [pyinstaller|https://pyinstaller.readthedocs.io/en/stable/operating-mode.html]. > ** Pros: > *** Installation is just downloading a single file to a directory in '{{$PATH}}' > ** Cons: > *** One will probably need to install '{{mock}}' and other dependencies manually. > *** '{{pyinstaller}}' is mostly for Python projects, while '{{mock_runner.sh}}' is a shell script. > * Using a Docker container: > ** Pros: > *** Everything can be pre-configured in the container, including '{{mock}}' itself and all needed permissions > *** Can run on any platform that can run Docker > ** Cons: > *** One needs Docker itself to be installed and configured > *** '{{mock}}' may not run well inside a container > *** Everything that is mounted into the mock environment must first be mounted into the container. This will probably require the container to run in privileged mode. This also means that running the container with the right mounts may be a complicated matter. > *** The container image may end up being quite big. -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1390) Implement "archive-artifacts" flow for containers in STD-CI
by Barak Korren (oVirt JIRA) 21 May '17

21 May '17

Barak Korren created OVIRT-1390: ----------------------------------- Summary: Implement "archive-artifacts" flow for containers in STD-CI Key: OVIRT-1390 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1390 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: High This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. We want to implement functionality similar to what "archive-artifacts" gives use for regular files, for containers in standard-CI. The design as as following: # An STD-CI script that generated container images need to tag them with the "exported-artifacts" tag. # After the STD-CI script finishes successfully, the CI system will take the tagged container images and push them the the "ovirtci" account on DockerHub. # The CI system will tage pushed images with the SHA1 hash of the URL of the Jenkins job build that built the image (Can be found in $BUILD_URL) # The CI system will output examples for '{{docker pull}}' and '{{docker run}}' command that would be needed to obtain the build image to the build status screen (Using the Groovy post-build plugin) -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1390) Implement "archive-artifacts" flow for containers in STD-CI
by Barak Korren (oVirt JIRA) 21 May '17

21 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1390?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1390: -------------------------------- Epic Link: OVIRT-400 > Implement "archive-artifacts" flow for containers in STD-CI > ----------------------------------------------------------- > > Key: OVIRT-1390 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1390 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: standard-ci > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. > We want to implement functionality similar to what "archive-artifacts" gives use for regular files, for containers in standard-CI. > The design as as following: > # An STD-CI script that generated container images need to tag them with the "exported-artifacts" tag. > # After the STD-CI script finishes successfully, the CI system will take the tagged container images and push them the the "ovirtci" account on DockerHub. > # The CI system will tage pushed images with the SHA1 hash of the URL of the Jenkins job build that built the image (Can be found in $BUILD_URL) > # The CI system will output examples for '{{docker pull}}' and '{{docker run}}' command that would be needed to obtain the build image to the build status screen (Using the Groovy post-build plugin) -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

Update contact info on the website
by Marc Dequènes (Duck) 21 May '17

21 May '17

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --sXwOabLOqc1oQie2ANAwv0LIvC3aXQkil Content-Type: multipart/mixed; boundary="rGJ8DtXqluq7aaqlvb1QEkC3OtgTMvtMq"; protected-headers="v1" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com> To: oVirt Infra <infra(a)ovirt.org> Message-ID: <ad367d9e-3ffa-24da-577d-fce85b08f0c2(a)redhat.com> Subject: Update contact info on the website --rGJ8DtXqluq7aaqlvb1QEkC3OtgTMvtMq Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Quack, We should really cleanup this page: http://www.ovirt.org/develop/infra/infrastructure/ David Caro left the project, Evegheny and me are missing, and I'm sure the role descriptions do not match reality anymore for some of you. I can do the editorial work if you give me all the changes you wish to see on this thread. \_o< --rGJ8DtXqluq7aaqlvb1QEkC3OtgTMvtMq-- --sXwOabLOqc1oQie2ANAwv0LIvC3aXQkil Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAlkd0iMACgkQVen596wc RD/H1hAAuXn6tIKBPaGv5xFD/tJP7aIXJsy8tUlx0YsgxFjp+GsS109Lj8HwY1HE H5gPwYRTjL/BaHhOowRtH3u7aRPfus1cP7qi9sd+x7+Fxdw74ATiun+limbj24E8 mLyvvy2OrWdEelY54hP419iJe+thkFLams1eAB3tGySCX+T8ZUpHGCvtpJ8dkxfX OcYaM8iVNO0NMH9pjorhFFv8Ghkb4wWwlC+dPQBVpVzXzgnbX/1LpjXSHVb5P8CF ifz1D5xHafJT/7ic9ND1lLRlxympFzGCOOzY5Uw0cV+bPASUOHNsnsRK02kSLCFp vR4RSzG/+ZmandaBZEDCmoJY+wr3JY2JLc5ffaRJa2cvTdm92gRPOqju6MU0qOgA ecuI3JL8tBSiBaXXXU92+tqrr4l1yp9qaN/1vGLh2qA/2iF2hLSq/t6vzqIKYgCO r7h0z5IF7WuwHTQqt/azO6/sgDfMMpk69ozgzFOgAfDZnGCp2/dJ83TYaaihgQvx 2vtFedOWEIcW2TkUoTa9CeHLn7qu9kOhVj56FNwYJsRPiSxRq7arq0F/kJazZzYd exslNIqzMgYK7nHFvc6EloBSPubY9NxMpnYmiR3ewBrbcABeT18ZWVvLfnceJc/O QYAnim5+R30HcugAE1Cwmkv9sLgDfteUQCHFF3M5ZksgI4+4A9Q= =Q99X -----END PGP SIGNATURE----- --sXwOabLOqc1oQie2ANAwv0LIvC3aXQkil--

2 1

oVirt infra daily report - unstable production jobs - 328
by jenkins＠jenkins.phx.ovirt.org 20 May '17

20 May '17

------=_Part_91_1208716722.1495321205992 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/328//artifact/exported-a… Cheers, Jenkins ------=_Part_91_1208716722.1495321205992 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 20/05/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_image-ng-system-tests/">ovirt_4.1_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_91_1208716722.1495321205992--

1 0

[JIRA] (OVIRT-1388) Open Ticket
by Barak Korren (oVirt JIRA) 20 May '17

20 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1388?page=com.atlassian.jira.… ] Barak Korren deleted OVIRT-1388: -------------------------------- > Open Ticket > ----------- > > Key: OVIRT-1388 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1388 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Lucas Martins > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1389) Sanlock Error when importing a POOL
by Barak Korren (oVirt JIRA) 20 May '17

20 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1389?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1389: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) > Sanlock Error when importing a POOL > ------------------------------------ > > Key: OVIRT-1389 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1389 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: storage > Reporter: Lucas Martins > Assignee: infra > Priority: Highest > > Hello, > We are facing a big problem and our entire environment is down. > One of our POOL of disk was corrupted, so we tried to clone this pool and turn up in another Ovirt server. However, we are getting a Sanlock error: SanlockException: (-223, 'Sanlock lockspace add failure', 'Sanlock exception'). > Is there a way to rebuild or repare this Sanlock, so we are able to import this POOL that was in another Ovirt server. How we can solve this problem? -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1389) Sanlock Error when importing a POOL
by Barak Korren (oVirt JIRA) 20 May '17

20 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1389?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1389: ------------------------------------- I am sorry this Jira instance is for tracking issues and work that have to do with oVirt's own development and CI infrastructure. It is not a support channel for oVirt itself. Please ask your questions in [mailto:users@ovirt.org] or open a bug in [bugzilla.redhat.com|http://bugzilla.redhat.com] > Sanlock Error when importing a POOL > ------------------------------------ > > Key: OVIRT-1389 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1389 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: storage > Reporter: Lucas Martins > Assignee: infra > Priority: Highest > > Hello, > We are facing a big problem and our entire environment is down. > One of our POOL of disk was corrupted, so we tried to clone this pool and turn up in another Ovirt server. However, we are getting a Sanlock error: SanlockException: (-223, 'Sanlock lockspace add failure', 'Sanlock exception'). > Is there a way to rebuild or repare this Sanlock, so we are able to import this POOL that was in another Ovirt server. How we can solve this problem? -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1389) Sanlock Error when importing a POOL
by Lucas Martins (oVirt JIRA) 20 May '17

20 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1389?page=com.atlassian.jira.… ] Lucas Martins updated OVIRT-1389: --------------------------------- Description: Hello, We are facing a big problem and our entire environment is down. One of our POOL of disk was corrupted, so we tried to clone this pool and turn up in another Ovirt server. However, we are getting a Sanlock error: SanlockException: (-223, 'Sanlock lockspace add failure', 'Sanlock exception'). Is there a way to rebuild or repare this Sanlock, so we are able to import this POOL that was in another Ovirt server. How we can solve this problem? was: Hello, We are facing a big problem and our entire environment is down. One of our POOL of disk was corrupted, so we tried to clone this pool and up in another Ovirt server. However, we are getting a Sanlock error: SanlockException: (-223, 'Sanlock lockspace add failure', 'Sanlock exception'). Is there a way to rebuild or repare this Sanlock, so we are able to import this POOL that was in another Ovirt server. How we can solve this problem? > Sanlock Error when importing a POOL > ------------------------------------ > > Key: OVIRT-1389 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1389 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: storage > Reporter: Lucas Martins > Assignee: infra > Priority: Highest > > Hello, > We are facing a big problem and our entire environment is down. > One of our POOL of disk was corrupted, so we tried to clone this pool and turn up in another Ovirt server. However, we are getting a Sanlock error: SanlockException: (-223, 'Sanlock lockspace add failure', 'Sanlock exception'). > Is there a way to rebuild or repare this Sanlock, so we are able to import this POOL that was in another Ovirt server. How we can solve this problem? -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1389) Sanlock Error when importing a POOL
by Lucas Martins (oVirt JIRA) 20 May '17

20 May '17

Lucas Martins created OVIRT-1389: ------------------------------------ Summary: Sanlock Error when importing a POOL Key: OVIRT-1389 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1389 Project: oVirt - virtualization made easy Issue Type: Bug Components: storage Reporter: Lucas Martins Assignee: infra Priority: Highest Hello, We are facing a big problem and our entire environment is down. One of our POOL of disk was corrupted, so we tried to clone this pool and up in another Ovirt server. However, we are getting a Sanlock error: SanlockException: (-223, 'Sanlock lockspace add failure', 'Sanlock exception'). Is there a way to rebuild or repare this Sanlock, so we are able to import this POOL that was in another Ovirt server. How we can solve this problem? -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1389) Sanlock Error when importing a POOL
by Lucas Martins (oVirt JIRA) 20 May '17

20 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1389?page=com.atlassian.jira.… ] Lucas Martins updated OVIRT-1389: --------------------------------- Epic Link: OVIRT-403 > Sanlock Error when importing a POOL > ------------------------------------ > > Key: OVIRT-1389 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1389 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: storage > Reporter: Lucas Martins > Assignee: infra > Priority: Highest > > Hello, > We are facing a big problem and our entire environment is down. > One of our POOL of disk was corrupted, so we tried to clone this pool and up in another Ovirt server. However, we are getting a Sanlock error: SanlockException: (-223, 'Sanlock lockspace add failure', 'Sanlock exception'). > Is there a way to rebuild or repare this Sanlock, so we are able to import this POOL that was in another Ovirt server. How we can solve this problem? -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

[JIRA] (OVIRT-1388) Open Ticket
by Lucas Martins (oVirt JIRA) 20 May '17

20 May '17

Lucas Martins created OVIRT-1388: ------------------------------------ Summary: Open Ticket Key: OVIRT-1388 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1388 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Lucas Martins Assignee: infra Open Ticket -- This message was sent by Atlassian JIRA (v1000.990.2#100044)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #354
by jenkins＠jenkins.phx.ovirt.org 19 May '17

19 May '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/354/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/hudson6356985958618745924.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 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1434, in _latestRepoXML oxml = self._saveOldRepoXML(local) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1292, in _saveOldRepoXML shutil.copy2(local, old_local) File "/usr/lib64/python2.7/shutil.py", line 131, in copy2 copystat(src, dst) File "/usr/lib64/python2.7/shutil.py", line 98, in copystat os.utime(dst, (st.st_atime, st.st_mtime)) OSError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/centos-updates-el6/repomd.xml.old.tmp' Build step 'Execute shell' marked build as failure

1 1

oVirt infra daily report - unstable production jobs - 327
by jenkins＠jenkins.phx.ovirt.org 19 May '17

19 May '17

------=_Part_82_1661972752.1495234807384 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/327//artifact/exported-a… Cheers, Jenkins ------=_Part_82_1661972752.1495234807384 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 19/05/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/">system-sync_mirrors-epel-el6-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_82_1661972752.1495234807384--

1 0

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #1343 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 19 May '17

19 May '17

------=_Part_79_337235844.1495198613941 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/1343/ Build Name: 1343 ovirt-engine-api-model (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/77027 - title: Fix VmCdromsService::Add interface return method - project: ovirt-engine-api-model - branch: master - author: Ondra Machacek <omachace(a)redhat.com> ------=_Part_79_337235844.1495198613941--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6741 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 19 May '17

19 May '17

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

1 10

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #1330 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 19 May '17

19 May '17

------=_Part_71_1133242356.1495186112393 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/1330/ Build Name: 1330 ovirt-engine-api-model (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/77013 - title: fixed wrong @since annotations - project: ovirt-engine-api-model - branch: master - author: Martin Mucha <mmucha(a)redhat.com> ------=_Part_71_1133242356.1495186112393--

1 1

oVirt infra daily report - unstable production jobs - 326
by jenkins＠jenkins.phx.ovirt.org 18 May '17

18 May '17

------=_Part_49_898673317.1495148406951 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/326//artifact/exported-a… Cheers, Jenkins ------=_Part_49_898673317.1495148406951 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 18/05/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_image-ng-system-tests/">ovirt_4.1_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_49_898673317.1495148406951--

1 0

oVirt website Builder upgrade
by Marc Dequènes (Duck) 18 May '17

18 May '17

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ktbanndmGMpWHCxgKWCSc1SB7VEMPLPwT Content-Type: multipart/mixed; boundary="CGI8lBSR8G62qSkgOSEQU007fKcdCe6wE"; protected-headers="v1" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com> To: oVirt Infra <infra(a)ovirt.org>, Brian Proffitt <bproffit(a)redhat.com>, Yaniv Kaul <ykaul(a)redhat.com> Message-ID: <df407ec0-9b33-17b1-fb96-6908a0d0b287(a)redhat.com> Subject: oVirt website Builder upgrade --CGI8lBSR8G62qSkgOSEQU007fKcdCe6wE Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Quack, The Builder was rebuilded on a recent environment with magical Ansible rules[1] on a new OSCI VM in the Community Cage. It was previously on OS1 which is doomed to disappear, and the former VM was shutdown more and more often which was a real pain (probably as an incentive to go away= ). [1] https://gitlab.com/osas/community-cage-infra-ansible The current system is cleaner and maintenance will be easier. I'm monitoring it closely, but if you find any problem do not hesitate contacting me. \_o< --CGI8lBSR8G62qSkgOSEQU007fKcdCe6wE-- --ktbanndmGMpWHCxgKWCSc1SB7VEMPLPwT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAlkdyqwACgkQVen596wc RD9Zjg//QT7vBdtVo4ahbniViscshM3ZMrBRDrtd6Y9eUd2dLd6Yunc7H1DKAeP1 /DNY1+P5h3WuRryrNoE4lMXTbmLVGV2PeqfBVdxLsSPdOn2TAV6yS/IpupnxcnRT CwXCvmHu5UZEX2dQWfos8PTVPl7XdUOgsgDagmM3Fk1KS1A6//DIsct35QFOrhsj +3VvfWsWptu8j9G/a3CIpwNdC7pO14atFK8zFMcc/OulqQdKeGvjN9bPHnY30dz8 L3NCB74kcFFWykz/4u7GJUvRt0UKOWzDSOTlMlOq5Yv/V1afEqpy0YXSYi+wVFOr LWsPpHyUSPNsccHoUT2uWmKdjHyRKUG10okqgE3OL7uJ6hIKWsA4gD640JDC9uJY T/2Gm/nFgEqXvJQoEVDVlFLvDTZ3oygU62UZ3JkxJ6isjsy8dPrSreuLPs7RTeFT 7HJj4Xp1QjgnwJlmfwjrvrfUfJMYlgpXfYvonsZbH9dO/UXobMUbpYqldC6feOY0 xJ8lC1qx3Yygr8IcTtPGVeJ7Q5MiZ6q2jvkZH7IW/W0NrAk3ll7CwiO1tQN06Ue2 c/JC3CbFTA7pdR+TdjaefvL2Mm+d+uKfBUphG52sJVL9YDODZ6tbi2u72un7PjoP SXqZvpzq21adfK3iMA6kUzUjP/aeOlVCyKmV3lolTxCNE3GYkM0= =KD3Z -----END PGP SIGNATURE----- --ktbanndmGMpWHCxgKWCSc1SB7VEMPLPwT--

1 0

Change in ds-jenkins-stg[master]: Insert the description of the change.
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Insert the description of the change. ...................................................................... Insert the description of the change. Change-Id: I29c27866b6c05ed1df05546b2c333deeb5e5af1d --- M automation/upstream_sources.yaml 1 file changed, 3 insertions(+), 3 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/31 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I29c27866b6c05ed1df05546b2c333deeb5e5af1d Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #1306 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 18 May '17

18 May '17

------=_Part_41_788042276.1495119586402 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/1306/ Build Name: 1306 ovirt-engine (3.6) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/76290 - title: core: Adding pretty name to OS version format - project: ovirt-engine - branch: ovirt-engine-3.6 - author: Eli Mesika <emesika(a)redhat.com> ------=_Part_41_788042276.1495119586402--

1 0

Change in ds-jenkins-stg[master]: fix
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: fix ...................................................................... fix Change-Id: I03925bcbdedd4387bf770b5458031057c7f1682d --- M data/git-push-url-map.yaml 1 file changed, 2 insertions(+), 2 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/30 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I03925bcbdedd4387bf770b5458031057c7f1682d Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in ds-jenkins-stg[master]: fix
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has posted comments on this change. Change subject: fix ...................................................................... Patch Set 2: Code-Review+2 Continuous-Integration+1 Verified+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/30 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I03925bcbdedd4387bf770b5458031057c7f1682d Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

Change in ds-jenkins-stg[master]: Insert the description of the change.
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Insert the description of the change. ...................................................................... Insert the description of the change. Change-Id: I229f3d4f9257ba4298d5f4bd3455bcecabcf3b0b --- M automation/upstream_sources.yaml 1 file changed, 2 insertions(+), 2 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/29 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I229f3d4f9257ba4298d5f4bd3455bcecabcf3b0b Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in ds-jenkins-stg[master]: Insert the description of the change.
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has posted comments on this change. Change subject: Insert the description of the change. ...................................................................... Patch Set 2: Code-Review+2 Continuous-Integration+1 Verified+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/29 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I229f3d4f9257ba4298d5f4bd3455bcecabcf3b0b Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

Change in ds-jenkins-stg[master]: Add map file
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Add map file ...................................................................... Add map file Change-Id: I7910277bb9034084ca62518b798927893bec5b2b --- A data/git-push-url-map.yaml 1 file changed, 4 insertions(+), 0 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/28 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I7910277bb9034084ca62518b798927893bec5b2b Gerrit-PatchSet: 2 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in ds-jenkins-stg[master]: Add map file
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has posted comments on this change. Change subject: Add map file ...................................................................... Patch Set 1: Code-Review+2 Continuous-Integration+1 Verified+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/28 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I7910277bb9034084ca62518b798927893bec5b2b Gerrit-PatchSet: 1 Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

Change in us-jenkins-stg2[master]: Adding map file
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has submitted this change and it was merged. Change subject: Adding map file ...................................................................... Adding map file Change-Id: If46b920ba66e7756b66cef9b70c6fe5043fd4f48 --- A data/git-push-url-map.yaml 1 file changed, 4 insertions(+), 0 deletions(-) Approvals: Gil Shinar: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/27 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: If46b920ba66e7756b66cef9b70c6fe5043fd4f48 Gerrit-PatchSet: 1 Gerrit-Project: us-jenkins-stg2 Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in us-jenkins-stg2[master]: Adding map file
by review＠gerrit-staging.phx.ovirt.org 18 May '17

18 May '17

>From Gil Shinar <gshinar(a)redhat.com>: Gil Shinar has posted comments on this change. Change subject: Adding map file ...................................................................... Patch Set 1: Code-Review+2 Continuous-Integration+1 Verified+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/27 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: If46b920ba66e7756b66cef9b70c6fe5043fd4f48 Gerrit-PatchSet: 1 Gerrit-Project: us-jenkins-stg2 Gerrit-Branch: master Gerrit-Owner: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Gil Shinar <gshinar(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

[JIRA] (OVIRT-1387) change gateway IP on PHX HE hypervisors
by Evgheni Dereveanchin (oVirt JIRA) 18 May '17

18 May '17

Evgheni Dereveanchin created OVIRT-1387: ------------------------------------------- Summary: change gateway IP on PHX HE hypervisors Key: OVIRT-1387 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1387 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra We have an incorrect gateway set in HA configs of ovirt-srv01, ovirt-srv02 and ovirt-srv03v which can cause issues like the ones described in OVIRT-1369 During the next host update window we need to edit /etc/ovirt-hosted-engine/hosted-engine.conf and change the gateway before rebooting. This has to be done in global maintenance to avoid unnecessary Engine restarts. -- This message was sent by Atlassian JIRA (v1000.967.1#100042)

1 0