- Infra - oVirt List Archives

[JIRA] (OVIRT-1535) Docker cleanup fails to clean non-named/non-tagged images
by Daniel Belenky (oVirt JIRA) 13 Jul '17

13 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1535?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1535: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Docker cleanup fails to clean non-named/non-tagged images > --------------------------------------------------------- > > Key: OVIRT-1535 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1535 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: Daniel Belenky > Priority: Highest > > In a case where a docker image is being built, it generates layers which are unnamed and untagged. This causes the cleanup script to fail when trying to clean them. > An example of such a failure can be found [here|http://jenkins.ovirt.org/job/ovirt-containers_master_check-patch-el7-x…] > The quick fix would be to ignore those trailing layers or alternatively detect them and remove them by image id. Imo, the second option is safer because every 'trailing layer' like that may get large (1GB+). > The long-term solution would be to implement some sort of garbage collector for orphaned layers. > I've found an open ticket [1] with some optional solutions, still need to see if they fit for our use case. If not, maybe consider implementing something similar. > [1] [github|https://github.com/docker/docker-registry/issues/223] -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1535) Docker cleanup fails to clean non-named/non-tagged images
by Daniel Belenky (oVirt JIRA) 13 Jul '17

13 Jul '17

Daniel Belenky created OVIRT-1535: ------------------------------------- Summary: Docker cleanup fails to clean non-named/non-tagged images Key: OVIRT-1535 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1535 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: infra Priority: Highest In a case where a docker image is being built, it generates layers which are unnamed and untagged. This causes the cleanup script to fail when trying to clean them. An example of such a failure can be found [here|http://jenkins.ovirt.org/job/ovirt-containers_master_check-patch-el7-x…] The quick fix would be to ignore those trailing layers or alternatively detect them and remove them by image id. Imo, the second option is safer because every 'trailing layer' like that may get large (1GB+). The long-term solution would be to implement some sort of garbage collector for orphaned layers. I've found an open ticket [1] with some optional solutions, still need to see if they fit for our use case. If not, maybe consider implementing something similar. [1] [github|https://github.com/docker/docker-registry/issues/223] -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7555 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Jul '17

13 Jul '17

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

1 12

[CQ]: 78103, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Jul '17

13 Jul '17

A system test invoked by the "ovirt-master" change queue including change 78103,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79246,7 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 79246,7 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/78103/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/79246/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1285/

1 0

[CQ]: 79230, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Jul '17

13 Jul '17

A system test invoked by the "ovirt-master" change queue including change 79230,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79246,7 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 79246,7 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/79230/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/79246/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1283/

1 0

[CQ]: 79022, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Jul '17

13 Jul '17

A system test invoked by the "ovirt-master" change queue including change 79022,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79246,7 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 79246,7 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/79022/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/79246/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1282/

1 0

Can't upgrade F25 to F26 because of repoman?
by Yaniv Kaul 13 Jul '17

13 Jul '17

Last metadata expiration check: 0:00:24 ago on Wed Jul 12 15:01:00 2017. Error: package repoman-2.0.29-1.fc25.noarch requires python-argparse, but none of the providers can be installed. package python-2.7.13-2.fc25.x86_64 requires python-libs(x86-64) = 2.7.13-2.fc25, but none of the providers can be installed. package repoman-2.0.29-1.fc25.noarch requires python-argparse, but none of the providers can be installed

4 6

[CQ]: 79246,7 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 13 Jul '17

13 Jul '17

Change 79246,7 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/79246/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1271/

2 2

[CQ]: 79252, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Jul '17

13 Jul '17

A system test invoked by the "ovirt-master" change queue including change 79252,8 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 79246,7 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 79246,7 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/79252/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/79246/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1277/

1 0

[JIRA] (OVIRT-1527) Make Change-Id clickable
by Yedidyah Bar David (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1527?page=com.atlassian.jira.… ] Yedidyah Bar David commented on OVIRT-1527: ------------------------------------------- On Wed, Jul 12, 2017 at 5:16 PM, Barak Korren (oVirt JIRA) We have 2.13.8, they have 2.11.4. -- Didi > Make Change-Id clickable > ------------------------ > > Key: OVIRT-1527 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1527 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Yedidyah Bar David > Assignee: infra > Priority: Low > > In openstack's gerrit, e.g. [1], the "Change-Id:" in the commit > message is clickable, and pressing it searches for patches including > it (e.g. in other branches). Might be useful for oVirt too. > [1] https://review.openstack.org/471802 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0