Project

General

Profile

Actions

action #51410

closed

Enable automatic test deployment on o3 again once it is deployed with the newest os-autoinst package

Added by nicksinger almost 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
2019-04-30
Due date:
% Done:

0%

Estimated time:

Description

OSD was deployed with the breaking API changes for assert_and_click. To not break tests (we have to merge the test-code changes now for the new API) on either instance we have to disable the cron-job pulling the test-code changes from github.

This ticket exists to make sure we don't forget to enable it again once everything is deployed/merged.


Related issues 1 (0 open1 closed)

Related to openQA Infrastructure - action #50951: Enable transactional updates on all o3 workers again once OBS published the most recent os-autoinst version Resolvednicksinger2019-04-30

Actions
Actions #1

Updated by nicksinger almost 5 years ago

  • Copied from action #50951: Enable transactional updates on all o3 workers again once OBS published the most recent os-autoinst version added
Actions #2

Updated by nicksinger almost 5 years ago

  • Copied from deleted (action #50951: Enable transactional updates on all o3 workers again once OBS published the most recent os-autoinst version )
Actions #3

Updated by nicksinger almost 5 years ago

  • Related to action #50951: Enable transactional updates on all o3 workers again once OBS published the most recent os-autoinst version added
Actions #4

Updated by nicksinger almost 5 years ago

I've commented out:

ariel:/etc # cat cron.d/openqa-update-git 
#-7    * * * *  geekotest     (cd /var/lib/openqa/share/tests/openqa && git pull --rebase origin master)

remove the preceding # to enable the cron again.

Actions #5

Updated by nicksinger almost 5 years ago

  • Status changed from Blocked to Resolved
  • Assignee set to nicksinger

As mentioned in https://progress.opensuse.org/issues/50951#note-4 the openQA-worker package was updated on every o3-worker. Therefore we could enable the two cron-jobs again.

Actions

Also available in: Atom PDF