- Infra - oVirt List Archives

[JIRA] (OVIRT-2956) jobs are getting "unauthorized" messages when trying to access Openshift api
by Shlomi Zidmi (oVirt JIRA) 08 Jun '20

08 Jun '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2956?page=com.atlassian.jira.… ] Shlomi Zidmi commented on OVIRT-2956: ------------------------------------- It is possible that the token for accessing openshift api (found in {{std_ci_secrets.yaml}}) is no longer valid, but i am yet to verify that > jobs are getting "unauthorized" messages when trying to access Openshift api > ---------------------------------------------------------------------------- > > Key: OVIRT-2956 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2956 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Shlomi Zidmi > Assignee: infra > > We've got bunch of jobs failing with the following message: > HTTP response body: b'{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}\n' > For example: > https://jenkins.ovirt.org/job/deploy-to-gated-ovirt-master/358/console > https://jenkins.ovirt.org/job/cleanup-gated-ovirt-master/176/console -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100128)

1 0

[JIRA] (OVIRT-2956) jobs are getting "unauthorized" messages when trying to access Openshift api
by Shlomi Zidmi (oVirt JIRA) 08 Jun '20

08 Jun '20

Shlomi Zidmi created OVIRT-2956: ----------------------------------- Summary: jobs are getting "unauthorized" messages when trying to access Openshift api Key: OVIRT-2956 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2956 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Shlomi Zidmi Assignee: infra We've got bunch of jobs failing with the following message: HTTP response body: b'{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}\n' For example: https://jenkins.ovirt.org/job/deploy-to-gated-ovirt-master/358/console https://jenkins.ovirt.org/job/cleanup-gated-ovirt-master/176/console -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100128)

1 0

[CQ]: 108907, 4 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Jun '20

08 Jun '20

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

1 0

[CQ]: 108907, 4 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Jun '20

08 Jun '20

A system test invoked by the "ovirt-4.3" change queue including change 108907,4 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 108955,2 (ovirt-system-tests) 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 108955,2 (ovirt-system-tests) 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/108907/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108955/2 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3503/

1 0

[CQ]: 109499, 1 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Jun '20

08 Jun '20

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

1 0

[CQ]: 109499, 1 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Jun '20

08 Jun '20

A system test invoked by the "ovirt-4.3" change queue including change 109499,1 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 108955,2 (ovirt-system-tests) 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 108955,2 (ovirt-system-tests) 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/109499/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108955/2 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3501/

1 0

[JIRA] (OVIRT-2950) Failing CI
by Evgheni Dereveanchin (oVirt JIRA) 08 Jun '20

08 Jun '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2950?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2950: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Failing CI > ---------- > > Key: OVIRT-2950 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2950 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Lev Veyde > Assignee: Evgheni Dereveanchin > > Hi, > Looks like some jobs, i.e. ovirt-release 4.3 CI fail for some time now: > https://jenkins.ovirt.org/job/ovirt-release_standard-check-patch/458/ > If I understand correctly it now requires and fails on missing > python3-docker images (it was just warning about the missing packages > before IIRC). > Thanks in advance, > -- > Lev Veyde > Senior Software Engineer, RHCE | RHCVA | MCITP > Red Hat Israel > <https://www.redhat.com> > lev(a)redhat.com | lveyde(a)redhat.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100128)

1 0

[JIRA] (OVIRT-2950) Failing CI
by Lev Veyde (oVirt JIRA) 08 Jun '20

08 Jun '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2950?page=com.atlassian.jira.… ] Lev Veyde commented on OVIRT-2950: ---------------------------------- Yes, it still seems to fail: https://jenkins.ovirt.org/job/ovirt-release_standard-check-patch/469/console > Failing CI > ---------- > > Key: OVIRT-2950 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2950 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Lev Veyde > Assignee: infra > > Hi, > Looks like some jobs, i.e. ovirt-release 4.3 CI fail for some time now: > https://jenkins.ovirt.org/job/ovirt-release_standard-check-patch/458/ > If I understand correctly it now requires and fails on missing > python3-docker images (it was just warning about the missing packages > before IIRC). > Thanks in advance, > -- > Lev Veyde > Senior Software Engineer, RHCE | RHCVA | MCITP > Red Hat Israel > <https://www.redhat.com> > lev(a)redhat.com | lveyde(a)redhat.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100128)

1 0

[JIRA] (OVIRT-2950) Failing CI
by Evgheni Dereveanchin (oVirt JIRA) 08 Jun '20

08 Jun '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2950?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2950: --------------------------------------------- This is some kind of a yum error where no repos are enabled. Comparing the outputs of “yum repolist“ and “yum repolist --all“ should reveal more info. There may also be an issue parsing yum.conf which could be causing this. Is this issue still in place? > Failing CI > ---------- > > Key: OVIRT-2950 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2950 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Lev Veyde > Assignee: infra > > Hi, > Looks like some jobs, i.e. ovirt-release 4.3 CI fail for some time now: > https://jenkins.ovirt.org/job/ovirt-release_standard-check-patch/458/ > If I understand correctly it now requires and fails on missing > python3-docker images (it was just warning about the missing packages > before IIRC). > Thanks in advance, > -- > Lev Veyde > Senior Software Engineer, RHCE | RHCVA | MCITP > Red Hat Israel > <https://www.redhat.com> > lev(a)redhat.com | lveyde(a)redhat.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100128)

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 76 - Failure!
by jenkins＠jenkins.phx.ovirt.org 08 Jun '20

08 Jun '20

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 76 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #76 [Dominik Holler] basic-suite-master: remove skipping test_hotplug_nic ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.100_basic_ui_sanity_pytest.test_virtual_machines[firefox] Error Message: TimeoutException: Message: Wait until VM list view is displayed failed Stack Trace: ovirt_driver = <test_utils.navigation.driver.Driver object at 0x7f22bac92b90> setup_virtual_machines = None save_screenshot = <function save at 0x7f22bac80938> save_page_source = <function save at 0x7f22bac80b90> def test_virtual_machines(ovirt_driver, setup_virtual_machines, save_screenshot, save_page_source): try: webadmin_menu = WebAdminLeftMenu(ovirt_driver) > vm_list_view = webadmin_menu.open_vm_list_view() ../basic-suite-master/test-scenarios/100_basic_ui_sanity_pytest.py:271: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ../basic-suite-master/test_utils/page_objects/WebAdminLeftMenu.py:22: in open_vm_list_view vm_list_view.wait_for_displayed() ../basic-suite-master/test_utils/page_objects/Displayable.py:14: in wait_for_displayed self.ovirt_driver.wait_until('Wait until ' + self.get_displayable_name() + ' is displayed failed', self.is_displayed) ../basic-suite-master/test_utils/navigation/driver.py:282: in wait_until self._wait_until(message, testlib.SHORT_TIMEOUT, condition_method, *args) ../basic-suite-master/test_utils/navigation/driver.py:288: in _wait_until WebDriverWait(self.driver, timeout).until(ConditionClass(condition_method, *args), message) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <selenium.webdriver.support.wait.WebDriverWait (session="95b15f6f-e37b-43cc-b54a-728f000e3317")> method = <test_utils.navigation.driver.ConditionClass object at 0x7f22ba4374d0> message = 'Wait until VM list view is displayed failed' def until(self, method, message=''): """Calls the method provided with the driver as an argument until the \ return value is not False.""" screen = None stacktrace = None end_time = time.time() + self._timeout while True: try: value = method(self._driver) if value: return value except self._ignored_exceptions as exc: screen = getattr(exc, 'screen', None) stacktrace = getattr(exc, 'stacktrace', None) time.sleep(self._poll) if time.time() > end_time: break > raise TimeoutException(message, screen, stacktrace) E TimeoutException: Message: Wait until VM list view is displayed failed ../.local/lib/python2.7/site-packages/selenium/webdriver/support/wait.py:80: TimeoutException

1 1