- Infra - oVirt List Archives

[JIRA] (OVIRT-1671) change admin password on PHX engine
by Evgheni Dereveanchin (oVirt JIRA) 25 Sep '17

25 Sep '17

This is a multi-part message in MIME format... ------------=_1506329861-22026-458 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Evgheni Dereveanchin created OVIRT-1671: ------------------------------------------- Summary: change admin password on PHX engine Key: OVIRT-1671 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1671 Project: oVirt - virtualization made easy Issue Type: Task Components: Hosting Reporter: Evgheni Dereveanchin Assignee: infra since oVirt now supports local user account, the admin@internal user shouold only be used in emergency cases. Opening this ticket to change this password and create users for team members instead. As we have an HE environment, care must be taken to ensure the change doesn't break HE agents. -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100061) ------------=_1506329861-22026-458 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Evgheni Dereveanchin created OVIRT-1671:</h3> <pre> Summary: change admin password on PHX engine Key: OVIRT-1671 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1671 Project: oVirt - virtualization made easy Issue Type: Task Components: Hosting Reporter: Evgheni Dereveanchin Assignee: infra</pre> <p>since oVirt now supports local user account, the admin@internal user shouold only be used in emergency cases. Opening this ticket to change this password and create users for team members instead.</p> <p>As we have an HE environment, care must be taken to ensure the change doesn't break HE agents.</p> <p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100061)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1506329861-22026-458--

1 0

[CQ]: 81835, 11 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Sep '17

25 Sep '17

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

1 0

[CQ]: 81834, 11 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Sep '17

25 Sep '17

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

1 0

[CQ]: 81833, 11 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Sep '17

25 Sep '17

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

1 0

[JIRA] (OVIRT-1670) Use cleanup_slave.sh and globale_setup.sh on pipeline loader nodes
by Barak Korren (oVirt JIRA) 25 Sep '17

25 Sep '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1670?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1670: ----------------------------------- Assignee: Barak Korren (was: infra) > Use cleanup_slave.sh and globale_setup.sh on pipeline loader nodes > ------------------------------------------------------------------ > > Key: OVIRT-1670 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1670 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Labels: change-queue, jenkins, standard-ci > > Pipeline loader nodes are the nodes (slaves) used to loader pipeline code and sometimes also perform some logic. > The '{{global_setup.sh}}' and '{{global_cleanup.sh}}' scripts are designed to run on all nodes and prepare them for running jobs. > Since the pipeline loader nodes are allocated and used differently then typical nodes that run STDCI logic, the '{{global_setup.sh}}' and '{{global_cleanup.sh}}' scripts were not used on them so far. > This has caused some issues, like for example change-queue logic failing when manual changes were made to slaves. > It is desirable to use the same setup and cleanup logic for all nodes regardless of what they run. > Within the scope of this task, we'll also remove the custom node setup logic in the change-queue jobs and move it to '{{global-setup.sh}}' where it aught to be. > This ticket is a blocker to OVIRT-1486 ATM because the custom node setup code in the change-queue jobs prevents other jobs from running parts of the change-queue logic. -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100061)

1 0

[JIRA] (OVIRT-1670) Use cleanup_slave.sh and globale_setup.sh on pipeline loader nodes
by Barak Korren (oVirt JIRA) 25 Sep '17

25 Sep '17

Barak Korren created OVIRT-1670: ----------------------------------- Summary: Use cleanup_slave.sh and globale_setup.sh on pipeline loader nodes Key: OVIRT-1670 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1670 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Pipeline loader nodes are the nodes (slaves) used to loader pipeline code and sometimes also perform some logic. The '{{global_setup.sh}}' and '{{global_cleanup.sh}}' scripts are designed to run on all nodes and prepare them for running jobs. Since the pipeline loader nodes are allocated and used differently then typical nodes that run STDCI logic, the '{{global_setup.sh}}' and '{{global_cleanup.sh}}' scripts were not used on them so far. This has caused some issues, like for example change-queue logic failing when manual changes were made to slaves. It is desirable to use the same setup and cleanup logic for all nodes regardless of what they run. Within the scope of this task, we'll also remove the custom node setup logic in the change-queue jobs and move it to '{{global-setup.sh}}' where it aught to be. This ticket is a blocker to OVIRT-1486 ATM because the custom node setup code in the change-queue jobs prevents other jobs from running parts of the change-queue logic. -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100061)

1 0

[JIRA] (OVIRT-1670) Use cleanup_slave.sh and globale_setup.sh on pipeline loader nodes
by Barak Korren (oVirt JIRA) 25 Sep '17

25 Sep '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1670?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1670: -------------------------------- Epic Link: OVIRT-400 > Use cleanup_slave.sh and globale_setup.sh on pipeline loader nodes > ------------------------------------------------------------------ > > Key: OVIRT-1670 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1670 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue, jenkins, standard-ci > > Pipeline loader nodes are the nodes (slaves) used to loader pipeline code and sometimes also perform some logic. > The '{{global_setup.sh}}' and '{{global_cleanup.sh}}' scripts are designed to run on all nodes and prepare them for running jobs. > Since the pipeline loader nodes are allocated and used differently then typical nodes that run STDCI logic, the '{{global_setup.sh}}' and '{{global_cleanup.sh}}' scripts were not used on them so far. > This has caused some issues, like for example change-queue logic failing when manual changes were made to slaves. > It is desirable to use the same setup and cleanup logic for all nodes regardless of what they run. > Within the scope of this task, we'll also remove the custom node setup logic in the change-queue jobs and move it to '{{global-setup.sh}}' where it aught to be. > This ticket is a blocker to OVIRT-1486 ATM because the custom node setup code in the change-queue jobs prevents other jobs from running parts of the change-queue logic. -- This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100061)

1 0

[CQ]: 81832, 11 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Sep '17

25 Sep '17

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

1 0

[CQ]: 81831, 11 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Sep '17

25 Sep '17

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

1 0

[CQ]: 81830, 11 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Sep '17

25 Sep '17

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

1 0