[JIRA] (OVIRT-3079) [FIRING:1] InstanceUnreachable ovirt-srv24.phx.ovirt.org kubernetes-nodes-exporter (amd64 linux true sriov-nic ovirt-srv24.phx.ovirt.org true r430 true primary true bare-metal ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-3079:
Resolution: Fixed
Status: Done (was: To Do)
The server had to be restarted, therefore the alert
> [FIRING:1] InstanceUnreachable ovirt-srv24.phx.ovirt.org
> kubernetes-nodes-exporter (amd64 linux true sriov-nic
> ovirt-srv24.phx.ovirt.org true r430 true primary true bare-metal ci)
> ---
>
> Key: OVIRT-3079
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3079
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ovirt-srv24.phx.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - deploy_sriov_passthrough_cni = true
> - hardwareSupport = sriov-nic
> - instance = ovirt-srv24.phx.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ovirt-srv24.phx.ovirt.org
> - logging_infra_fluentd = true
> - model = r430
> - node_role_kubernetes_io_compute = true
> - region = primary
> - sriov_nic = true
> - type = bare-metal
> - zone = ci
> Annotations:
> - description = ovirt-srv24.phx.ovirt.org of job kubernetes-nodes-exporter
> has been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100154)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/XBQ7KRJ3KC3XIVWONCANSEUGWCMAW7U2/
[JIRA] (OVIRT-3078) [FIRING:1] InstanceUnreachable ovirt-srv24.phx.ovirt.org kubernetes-nodes-exporter (amd64 linux true sriov-nic ovirt-srv24.phx.ovirt.org true r430 true primary true bare-metal ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-3078:
Resolution: Fixed
Status: Done (was: To Do)
Had to restart the node due to networking issues.
> [FIRING:1] InstanceUnreachable ovirt-srv24.phx.ovirt.org
> kubernetes-nodes-exporter (amd64 linux true sriov-nic
> ovirt-srv24.phx.ovirt.org true r430 true primary true bare-metal ci)
> ---
>
> Key: OVIRT-3078
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3078
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ovirt-srv24.phx.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - deploy_sriov_passthrough_cni = true
> - hardwareSupport = sriov-nic
> - instance = ovirt-srv24.phx.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ovirt-srv24.phx.ovirt.org
> - logging_infra_fluentd = true
> - model = r430
> - node_role_kubernetes_io_compute = true
> - region = primary
> - sriov_nic = true
> - type = bare-metal
> - zone = ci
> Annotations:
> - description = ovirt-srv24.phx.ovirt.org of job kubernetes-nodes-exporter
> has been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100154)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/BK5OKM5X2V67O4DOD6JFPKU6QEWB77YF/
[JIRA] (OVIRT-3074) Long filenames chopped in directory index
[ https://ovirt-jira.atlassian.net/browse/OVIRT-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shlomi Zidmi updated OVIRT-3074: Assignee: (was: ) Resolution: Fixed Status: Done (was: To Do) Hi, As requested, long filenames are no longer being chopped by httpd. > Long filenames chopped in directory index > - > > Key: OVIRT-3074 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3074 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Yedidyah Bar David >Assignee: Shlomi Zidmi > > Hi all, > Can you please configure stuff so that [1] will show full file names? > If that's apache httpd, should be doable by adding to conf (e.g. > .htaccess or somewhere in /etc/httpd): > IndexOptions NameWidth=* > Thanks and best regards, > [1] https://templates.ovirt.org/yum/ > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100153) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/QUKUMRXPHGJI2PCXDJMJX2GT3NNYF5XU/
[JIRA] (OVIRT-3073) Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg conf to common
[ https://ovirt-jira.atlassian.net/browse/OVIRT-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shlomi Zidmi updated OVIRT-3073: Assignee: (was: ) Status: In Progress (was: To Do) > Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg > conf to common > > > Key: OVIRT-3073 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3073 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Yedidyah Bar David >Assignee: Shlomi Zidmi > > On Mon, Dec 14, 2020 at 12:21 PM Code Review wrote: > > > > From Jenkins CI : > > > > Jenkins CI has posted comments on this change. ( > > https://gerrit.ovirt.org/c/ovirt-engine/+/112414 ) > > > > Change subject: packaging: setup: Move engine-specific pg conf to common > > .. > > > > > > Patch Set 4: Continuous-Integration-1 > > > > Build Failed > > > > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/9236/ : > > FAILURE > 12:21:32 + > usrc=/home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > 12:21:32 + [[ -x > /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > ]] > 12:21:32 + > /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > --log -d get > 12:21:32 /usr/bin/env: ‘python’: No such file or directory > Any idea? > This is a result of manual 'ci test'. Automatic check-patch on the > same patch did succeed. > Thanks, > > > > > > -- > > To view, visit https://gerrit.ovirt.org/c/ovirt-engine/+/112414 > > To unsubscribe, or for help writing mail filters, visit > > https://gerrit.ovirt.org/settings > > > > Gerrit-Project: ovirt-engine > > Gerrit-Branch: master > > Gerrit-Change-Id: I8af2e259389fef59251a69c6443e3e440b93a843 > > Gerrit-Change-Number: 112414 > > Gerrit-PatchSet: 4 > > Gerrit-Owner: Yedidyah Bar David > > Gerrit-Reviewer: Asaf Rachmani > > Gerrit-Reviewer: Evgeny Slutsky > > Gerrit-Reviewer: Gal Zaidman > > Gerrit-Reviewer: Jenkins CI > > Gerrit-Reviewer: Lev Veyde > > Gerrit-Reviewer: Sandro Bonazzola > > Gerrit-Reviewer: Yedidyah Bar David > > Gerrit-Reviewer: gerrit-hooks > > Gerrit-Comment-Date: Mon, 14 Dec 2020 10:21:34 + > > Gerrit-HasComments: No > > Gerrit-Has-Labels: Yes > > Gerrit-MessageType: comment > > > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100152) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/JCPDMLREPY4NGRJHO5DRRRW3CE5DYSJH/
[JIRA] (OVIRT-3073) Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg conf to common
[ https://ovirt-jira.atlassian.net/browse/OVIRT-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40982#comment-40982 ] Shlomi Zidmi commented on OVIRT-3073: - Hey, As Ehud mentioned, we’ve deployed new el8 workers instead of some old fedoras. These workers had python3 installed, but not configured as default for some reason. I’ve fixed that so it should at least pass the broken python error, but since these are new workers it’s possible that some other adjustments would be needed. Please try again and let us know if you encounter any other issues. > Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg > conf to common > > > Key: OVIRT-3073 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3073 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Yedidyah Bar David >Assignee: infra > > On Mon, Dec 14, 2020 at 12:21 PM Code Review wrote: > > > > From Jenkins CI : > > > > Jenkins CI has posted comments on this change. ( > > https://gerrit.ovirt.org/c/ovirt-engine/+/112414 ) > > > > Change subject: packaging: setup: Move engine-specific pg conf to common > > .. > > > > > > Patch Set 4: Continuous-Integration-1 > > > > Build Failed > > > > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/9236/ : > > FAILURE > 12:21:32 + > usrc=/home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > 12:21:32 + [[ -x > /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > ]] > 12:21:32 + > /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > --log -d get > 12:21:32 /usr/bin/env: ‘python’: No such file or directory > Any idea? > This is a result of manual 'ci test'. Automatic check-patch on the > same patch did succeed. > Thanks, > > > > > > -- > > To view, visit https://gerrit.ovirt.org/c/ovirt-engine/+/112414 > > To unsubscribe, or for help writing mail filters, visit > > https://gerrit.ovirt.org/settings > > > > Gerrit-Project: ovirt-engine > > Gerrit-Branch: master > > Gerrit-Change-Id: I8af2e259389fef59251a69c6443e3e440b93a843 > > Gerrit-Change-Number: 112414 > > Gerrit-PatchSet: 4 > > Gerrit-Owner: Yedidyah Bar David > > Gerrit-Reviewer: Asaf Rachmani > > Gerrit-Reviewer: Evgeny Slutsky > > Gerrit-Reviewer: Gal Zaidman > > Gerrit-Reviewer: Jenkins CI > > Gerrit-Reviewer: Lev Veyde > > Gerrit-Reviewer: Sandro Bonazzola > > Gerrit-Reviewer: Yedidyah Bar David > > Gerrit-Reviewer: gerrit-hooks > > Gerrit-Comment-Date: Mon, 14 Dec 2020 10:21:34 + > > Gerrit-HasComments: No > > Gerrit-Has-Labels: Yes > > Gerrit-MessageType: comment > > > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100152) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/7ZMVZ2QIQYPZYDPLEU6KQNVOFBXMGYC5/
[JIRA] (OVIRT-3063) gtar Cannot write: Input/output error (was: Change in ovirt-system-tests[master]: pytest: he: Port 008_restart_he_vm.py to pytest)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40964#comment-40964
]
Shlomi Zidmi commented on OVIRT-3063:
-
Looks like no other Jenkins instance uses this node. Also {{ virsh lists --all
}} produces no output so i guess there’s nothing to clean.
I’ll re-trigger the job manually to see what happens to the files
> gtar Cannot write: Input/output error (was: Change in
> ovirt-system-tests[master]: pytest: he: Port 008_restart_he_vm.py to pytest)
> --
>
> Key: OVIRT-3063
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3063
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Yedidyah Bar David
>Assignee: Shlomi Zidmi
> Attachments: errors.txt
>
>
> Hi all,
> On Tue, Nov 24, 2020 at 8:54 PM Code Review wrote:
> >
> > From Jenkins CI :
> >
> > Jenkins CI has posted comments on this change.
> >
> > Change subject: pytest: he: Port 008_restart_he_vm.py to pytest
> > ..
> >
> >
> > Patch Set 12: Continuous-Integration-1
> >
> > Build Failed
> >
> > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14018/
> > : FAILURE
> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14018//artifact/check-patch.he-basic_suite_master.el8.x86_64/mock_logs/script/stdout_stderr.log
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Extract appliance to
> local VM directory]
> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "dest":
> "/var/tmp/localvm3i6cjs21", "extract_results": {"cmd":
> ["/usr/bin/gtar", "--extract", "-C", "/var/tmp/localvm3i6cjs21", "-z",
> "--show-transformed-names", "--sparse", "-f",
> "/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova"],
> "err": "/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot write: Input/output error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot utime: Input/output error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot change ownership to uid 0, gid 0: Input/output
> error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot change mode to rwxr-xr-x: Input/output error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d.meta:
> Cannot open: Input/output error\n/usr/bin/gtar: Exiting with failure
> status due to previous errors\n", "out": "", "rc": 2}, "handler":
> "TgzArchive", "msg": "failed to unpack
> /usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova
> to /var/tmp/localvm3i6cjs21", "src":
> "/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova"}
> Other such failures already happened several times recently. Perhaps
> some disk-space issue? Or something similar?
> Thanks,
> >
> >
> > --
> > To view, visit https://gerrit.ovirt.org/112273
> > To unsubscribe, visit https://gerrit.ovirt.org/settings
> >
> > Gerrit-Project: ovirt-system-tests
> > Gerrit-Branch: master
> > Gerrit-MessageType: comment
> > Gerrit-Change-Id: Ib510a1624ac5baad0f637a96919c5fd6040e89aa
> > Gerrit-Change-Number: 112273
> > Gerrit-PatchSet: 12
> > Gerrit-Owner: Yedidyah Bar David
> > Gerrit-Reviewer: Anonymous Coward (1001916)
> > Gerrit-Reviewer: Anton Marchukov
> > Gerrit-Reviewer: Dafna Ron
> > Gerrit-Reviewer: Dusan Fodor
> > Gerrit-Reviewer: Gal Ben Haim
> > Gerrit-Reviewer: Galit Rosenthal
> > Gerrit-Reviewer: Jenkins CI
> > Gerrit-Reviewer: Marcin Sobczyk
> > Gerrit-Reviewer: Yedidyah Bar David
> > Gerrit-Comment-Date: Tue, 24 Nov 2020 18:54:46 +
> > Gerrit-HasComments: No
> >
> --
> Didi
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100152)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/6AVESO6HBFU7H2QVOBKPQRUZOJISWMTY/
[JIRA] (OVIRT-3063) gtar Cannot write: Input/output error (was: Change in ovirt-system-tests[master]: pytest: he: Port 008_restart_he_vm.py to pytest)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40961#comment-40961
]
Shlomi Zidmi edited comment on OVIRT-3063 at 12/1/20 1:54 PM:
--
There are bunch of file/directory not found errors from around the time the
build was running:
{noformat}Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30
17:09:44.569+: 1776625: error : virDirOpenInternal:2936 : cannot open
directory
'/home/jenkins/workspace/ovirt-appliance_ovirt-4.3_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.569+:
1776625: error : storageDriverAutostartCallback:209 : internal error: Failed to
autostart storage pool 'engine-appliance-4': cannot open directory
'/home/jenkins/workspace/ovirt-appliance_ovirt-4.3_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.569+:
1776625: error : virDirOpenInternal:2936 : cannot open directory
'/home/jenkins/workspace/ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.569+:
1776625: error : storageDriverAutostartCallback:209 : internal error: Failed to
autostart storage pool 'engine-appliance-2': cannot open directory
'/home/jenkins/workspace/ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.570+:
1776625: error : virDirOpenInternal:2936 : cannot open directory
'/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/ovirt-node-ng':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.570+:
1776625: error : storageDriverAutostartCallback:209 : internal error: Failed to
autostart storage pool 'ovirt-node-ng': cannot open directory
'/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/ovirt-node-ng':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.570+:
1776625: error : virDirOpenInternal:2936 : cannot open directory
'/home/jenkins/workspace/ovirt-system-tests_he-node-ng-suite-4.2/ovirt-system-tests/ovirt-node':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.570+:
1776625: error : storageDriverAutostartCallback:209 : internal error: Failed to
autostart storage pool 'ovirt-node-2': cannot open directory
'/home/jenkins/workspace/ovirt-system-tests_he-node-ng-suite-4.2/ovirt-system-tests/ovirt-node':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.570+:
1776625: error : virDirOpenInternal:2936 : cannot open directory
'/home/jenkins/workspace/ovirt-system-tests_standard-check-patch/ovirt-system-tests/ovirt-node':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.570+:
1776625: error : storageDriverAutostartCallback:209 : internal error: Failed to
autostart storage pool 'ovirt-node': cannot open directory
'/home/jenkins/workspace/ovirt-system-tests_standard-check-patch/ovirt-system-tests/ovirt-node':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.570+:
1776625: error : virDirOpenInternal:2936 : cannot open directory
'/home/jenkins/workspace/ovirt-appliance_ovirt-4.1-snapshot_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance':
No such file or directory{noformat}
Attaching a .txt file with all errors
[^errors.txt]
was (Author: szidmi):
There are bunch of file/directory not found errors from around the time the
build was running:
{noformat}Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30
17:09:44.569+: 1776625: error : virDirOpenInternal:2936 : cannot open
directory
'/home/jenkins/workspace/ovirt-appliance_ovirt-4.3_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.569+:
1776625: error : storageDriverAutostartCallback:209 : internal error: Failed to
autostart storage pool 'engine-appliance-4': cannot open directory
'/home/jenkins/workspace/ovirt-appliance_ovirt-4.3_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.569+:
1776625: error : virDirOpenInternal:2936 : cannot open directory
'/home/jenkins/workspace/ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance':
No such file or director
[JIRA] (OVIRT-3063) gtar Cannot write: Input/output error (was: Change in ovirt-system-tests[master]: pytest: he: Port 008_restart_he_vm.py to pytest)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40961#comment-40961
]
Shlomi Zidmi commented on OVIRT-3063:
-
There are bunch of file/directory not found errors from around the time the
build was running:
{noformat}Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30
17:09:44.569+: 1776625: error : virDirOpenInternal:2936 : cannot open
directory
'/home/jenkins/workspace/ovirt-appliance_ovirt-4.3_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.569+:
1776625: error : storageDriverAutostartCallback:209 : internal error: Failed to
autostart storage pool 'engine-appliance-4': cannot open directory
'/home/jenkins/workspace/ovirt-appliance_ovirt-4.3_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.569+:
1776625: error : virDirOpenInternal:2936 : cannot open directory
'/home/jenkins/workspace/ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.569+:
1776625: error : storageDriverAutostartCallback:209 : internal error: Failed to
autostart storage pool 'engine-appliance-2': cannot open directory
'/home/jenkins/workspace/ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.570+:
1776625: error : virDirOpenInternal:2936 : cannot open directory
'/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/ovirt-node-ng':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.570+:
1776625: error : storageDriverAutostartCallback:209 : internal error: Failed to
autostart storage pool 'ovirt-node-ng': cannot open directory
'/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/ovirt-node-ng':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.570+:
1776625: error : virDirOpenInternal:2936 : cannot open directory
'/home/jenkins/workspace/ovirt-system-tests_he-node-ng-suite-4.2/ovirt-system-tests/ovirt-node':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.570+:
1776625: error : storageDriverAutostartCallback:209 : internal error: Failed to
autostart storage pool 'ovirt-node-2': cannot open directory
'/home/jenkins/workspace/ovirt-system-tests_he-node-ng-suite-4.2/ovirt-system-tests/ovirt-node':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.570+:
1776625: error : virDirOpenInternal:2936 : cannot open directory
'/home/jenkins/workspace/ovirt-system-tests_standard-check-patch/ovirt-system-tests/ovirt-node':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.570+:
1776625: error : storageDriverAutostartCallback:209 : internal error: Failed to
autostart storage pool 'ovirt-node': cannot open directory
'/home/jenkins/workspace/ovirt-system-tests_standard-check-patch/ovirt-system-tests/ovirt-node':
No such file or directory
Nov 30 17:09:44 ovirt-srv22 libvirtd[1776609]: 2020-11-30 17:09:44.570+:
1776625: error : virDirOpenInternal:2936 : cannot open directory
'/home/jenkins/workspace/ovirt-appliance_ovirt-4.1-snapshot_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance':
No such file or directory{noformat}
> gtar Cannot write: Input/output error (was: Change in
> ovirt-system-tests[master]: pytest: he: Port 008_restart_he_vm.py to pytest)
> --
>
> Key: OVIRT-3063
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3063
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Yedidyah Bar David
>Assignee: Shlomi Zidmi
>
> Hi all,
> On Tue, Nov 24, 2020 at 8:54 PM Code Review wrote:
> >
> > From Jenkins CI :
> >
> > Jenkins CI has posted comments on this change.
> >
> > Change subject: pytest: he: Port 008_restart_he_vm.py to pytest
> > ..
> >
> >
> > Patch Set 12: Continuous-Integration-1
> >
> > Build Failed
> >
> > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14018/
> > : FAILURE
> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14018//artifact/check-patch.he-basic_suite_master.el8.x86_64/mock_logs/script/stdout_stderr.log
[JIRA] (OVIRT-3063) gtar Cannot write: Input/output error (was: Change in ovirt-system-tests[master]: pytest: he: Port 008_restart_he_vm.py to pytest)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40960#comment-40960
]
Shlomi Zidmi commented on OVIRT-3063:
-
I took ovirt-srv22 back offline. This node has 900GB disk and uses only 90GB,
so I guess disk space is not the issue. I’ll further check in the logs to see
if we can find something suspicious there
> gtar Cannot write: Input/output error (was: Change in
> ovirt-system-tests[master]: pytest: he: Port 008_restart_he_vm.py to pytest)
> --
>
> Key: OVIRT-3063
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3063
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Yedidyah Bar David
>Assignee: Shlomi Zidmi
>
> Hi all,
> On Tue, Nov 24, 2020 at 8:54 PM Code Review wrote:
> >
> > From Jenkins CI :
> >
> > Jenkins CI has posted comments on this change.
> >
> > Change subject: pytest: he: Port 008_restart_he_vm.py to pytest
> > ..
> >
> >
> > Patch Set 12: Continuous-Integration-1
> >
> > Build Failed
> >
> > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14018/
> > : FAILURE
> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14018//artifact/check-patch.he-basic_suite_master.el8.x86_64/mock_logs/script/stdout_stderr.log
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Extract appliance to
> local VM directory]
> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "dest":
> "/var/tmp/localvm3i6cjs21", "extract_results": {"cmd":
> ["/usr/bin/gtar", "--extract", "-C", "/var/tmp/localvm3i6cjs21", "-z",
> "--show-transformed-names", "--sparse", "-f",
> "/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova"],
> "err": "/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot write: Input/output error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot utime: Input/output error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot change ownership to uid 0, gid 0: Input/output
> error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot change mode to rwxr-xr-x: Input/output error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d.meta:
> Cannot open: Input/output error\n/usr/bin/gtar: Exiting with failure
> status due to previous errors\n", "out": "", "rc": 2}, "handler":
> "TgzArchive", "msg": "failed to unpack
> /usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova
> to /var/tmp/localvm3i6cjs21", "src":
> "/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova"}
> Other such failures already happened several times recently. Perhaps
> some disk-space issue? Or something similar?
> Thanks,
> >
> >
> > --
> > To view, visit https://gerrit.ovirt.org/112273
> > To unsubscribe, visit https://gerrit.ovirt.org/settings
> >
> > Gerrit-Project: ovirt-system-tests
> > Gerrit-Branch: master
> > Gerrit-MessageType: comment
> > Gerrit-Change-Id: Ib510a1624ac5baad0f637a96919c5fd6040e89aa
> > Gerrit-Change-Number: 112273
> > Gerrit-PatchSet: 12
> > Gerrit-Owner: Yedidyah Bar David
> > Gerrit-Reviewer: Anonymous Coward (1001916)
> > Gerrit-Reviewer: Anton Marchukov
> > Gerrit-Reviewer: Dafna Ron
> > Gerrit-Reviewer: Dusan Fodor
> > Gerrit-Reviewer: Gal Ben Haim
> > Gerrit-Reviewer: Galit Rosenthal
> > Gerrit-Reviewer: Jenkins CI
> > Gerrit-Reviewer: Marcin Sobczyk
> > Gerrit-Reviewer: Yedidyah Bar David
> > Gerrit-Comment-Date: Tue, 24 Nov 2020 18:54:46 +
> > Gerrit-HasComments: No
> >
> --
> Didi
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100152)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/CEZZY2G32AMBAEU67NJFVXVWG6MWRRHV/
[JIRA] (OVIRT-3063) gtar Cannot write: Input/output error (was: Change in ovirt-system-tests[master]: pytest: he: Port 008_restart_he_vm.py to pytest)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40955#comment-40955
]
Shlomi Zidmi commented on OVIRT-3063:
-
Looks like recent builds ran without this error. Taking ovirt-srv22 back online
to see how it behaves
> gtar Cannot write: Input/output error (was: Change in
> ovirt-system-tests[master]: pytest: he: Port 008_restart_he_vm.py to pytest)
> --
>
> Key: OVIRT-3063
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3063
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
>Reporter: Yedidyah Bar David
>Assignee: Shlomi Zidmi
>
> Hi all,
> On Tue, Nov 24, 2020 at 8:54 PM Code Review wrote:
> >
> > From Jenkins CI :
> >
> > Jenkins CI has posted comments on this change.
> >
> > Change subject: pytest: he: Port 008_restart_he_vm.py to pytest
> > ..
> >
> >
> > Patch Set 12: Continuous-Integration-1
> >
> > Build Failed
> >
> > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14018/
> > : FAILURE
> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14018//artifact/check-patch.he-basic_suite_master.el8.x86_64/mock_logs/script/stdout_stderr.log
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Extract appliance to
> local VM directory]
> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "dest":
> "/var/tmp/localvm3i6cjs21", "extract_results": {"cmd":
> ["/usr/bin/gtar", "--extract", "-C", "/var/tmp/localvm3i6cjs21", "-z",
> "--show-transformed-names", "--sparse", "-f",
> "/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova"],
> "err": "/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot write: Input/output error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot utime: Input/output error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot change ownership to uid 0, gid 0: Input/output
> error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot change mode to rwxr-xr-x: Input/output error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d.meta:
> Cannot open: Input/output error\n/usr/bin/gtar: Exiting with failure
> status due to previous errors\n", "out": "", "rc": 2}, "handler":
> "TgzArchive", "msg": "failed to unpack
> /usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova
> to /var/tmp/localvm3i6cjs21", "src":
> "/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova"}
> Other such failures already happened several times recently. Perhaps
> some disk-space issue? Or something similar?
> Thanks,
> >
> >
> > --
> > To view, visit https://gerrit.ovirt.org/112273
> > To unsubscribe, visit https://gerrit.ovirt.org/settings
> >
> > Gerrit-Project: ovirt-system-tests
> > Gerrit-Branch: master
> > Gerrit-MessageType: comment
> > Gerrit-Change-Id: Ib510a1624ac5baad0f637a96919c5fd6040e89aa
> > Gerrit-Change-Number: 112273
> > Gerrit-PatchSet: 12
> > Gerrit-Owner: Yedidyah Bar David
> > Gerrit-Reviewer: Anonymous Coward (1001916)
> > Gerrit-Reviewer: Anton Marchukov
> > Gerrit-Reviewer: Dafna Ron
> > Gerrit-Reviewer: Dusan Fodor
> > Gerrit-Reviewer: Gal Ben Haim
> > Gerrit-Reviewer: Galit Rosenthal
> > Gerrit-Reviewer: Jenkins CI
> > Gerrit-Reviewer: Marcin Sobczyk
> > Gerrit-Reviewer: Yedidyah Bar David
> > Gerrit-Comment-Date: Tue, 24 Nov 2020 18:54:46 +
> > Gerrit-HasComments: No
> >
> --
> Didi
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100152)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/RUEQO4HN2L4FBAD2G63HT6HC3TNISMMF/
[JIRA] (OVIRT-3063) gtar Cannot write: Input/output error (was: Change in ovirt-system-tests[master]: pytest: he: Port 008_restart_he_vm.py to pytest)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40948#comment-40948
]
Shlomi Zidmi commented on OVIRT-3063:
-
Thanks for the extra info. I checked the build you shared
([https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14022/|https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14022/])
and it looks like once again ovirt-srv22 is involved (check-patch-el8 ran on
it).
Also i can confirm the issue appeared on another node as well - ovirt-srv21:
[https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_standard-check-patch/detail/ovirt-system-tests_standard-check-patch/14074/pipeline/150/|https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_standard-check-patch/detail/ovirt-system-tests_standard-check-patch/14074/pipeline/150/]
So it seems like multiple nodes are involved in these failures.
> gtar Cannot write: Input/output error (was: Change in
> ovirt-system-tests[master]: pytest: he: Port 008_restart_he_vm.py to pytest)
> --
>
> Key: OVIRT-3063
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3063
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
>Reporter: Yedidyah Bar David
>Assignee: infra
>
> Hi all,
> On Tue, Nov 24, 2020 at 8:54 PM Code Review wrote:
> >
> > From Jenkins CI :
> >
> > Jenkins CI has posted comments on this change.
> >
> > Change subject: pytest: he: Port 008_restart_he_vm.py to pytest
> > ..
> >
> >
> > Patch Set 12: Continuous-Integration-1
> >
> > Build Failed
> >
> > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14018/
> > : FAILURE
> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14018//artifact/check-patch.he-basic_suite_master.el8.x86_64/mock_logs/script/stdout_stderr.log
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Extract appliance to
> local VM directory]
> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "dest":
> "/var/tmp/localvm3i6cjs21", "extract_results": {"cmd":
> ["/usr/bin/gtar", "--extract", "-C", "/var/tmp/localvm3i6cjs21", "-z",
> "--show-transformed-names", "--sparse", "-f",
> "/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova"],
> "err": "/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot write: Input/output error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot utime: Input/output error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot change ownership to uid 0, gid 0: Input/output
> error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot change mode to rwxr-xr-x: Input/output error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d.meta:
> Cannot open: Input/output error\n/usr/bin/gtar: Exiting with failure
> status due to previous errors\n", "out": "", "rc": 2}, "handler":
> "TgzArchive", "msg": "failed to unpack
> /usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova
> to /var/tmp/localvm3i6cjs21", "src":
> "/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova"}
> Other such failures already happened several times recently. Perhaps
> some disk-space issue? Or something similar?
> Thanks,
> >
> >
> > --
> > To view, visit https://gerrit.ovirt.org/112273
> > To unsubscribe, visit https://gerrit.ovirt.org/settings
> >
> > Gerrit-Project: ovirt-system-tests
> > Gerrit-Branch: master
> > Gerrit-MessageType: comment
> > Gerrit-Change-Id: Ib510a1624ac5baad0f637a96919c5fd6040e89aa
> > Gerrit-Change-Number: 112273
> > Gerrit-PatchSet: 12
> > Gerrit-Owner: Yedidyah Bar David
> > Gerrit-Reviewer: Anonymous Coward (1001916)
> > Gerrit-Reviewer: Anton Marchukov
> > Gerrit-Reviewer: Dafna Ron
> > Gerrit-Reviewer: Dusan Fodor
> > Gerrit-Reviewer: Gal Ben Haim
> > Gerrit-Reviewer: Galit Rosenthal
> > Gerrit-Reviewer: Jenkins CI
> > Gerrit-Reviewer: Marcin Sobczyk
> > Gerrit-Reviewer: Yedidyah Bar David
> > Gerrit-Comment-Date: Tue, 24 Nov 2020 18:54:46 +
> > Gerrit-HasComments: No
> >
> --
> Didi
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100151)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/commu
[JIRA] (OVIRT-3063) gtar Cannot write: Input/output error (was: Change in ovirt-system-tests[master]: pytest: he: Port 008_restart_he_vm.py to pytest)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40943#comment-40943
]
Shlomi Zidmi commented on OVIRT-3063:
-
I’m still reviewing this issue. I don’t think that’s a disk space issue since
only 15% of the disk is being used. Also no info is returned from dmesg
regarding any errrors/failures.
For now I’ve disabled the node (ovirt-srv22) on Jenkins until we figure this out
> gtar Cannot write: Input/output error (was: Change in
> ovirt-system-tests[master]: pytest: he: Port 008_restart_he_vm.py to pytest)
> --
>
> Key: OVIRT-3063
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3063
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
>Reporter: Yedidyah Bar David
>Assignee: infra
>
> Hi all,
> On Tue, Nov 24, 2020 at 8:54 PM Code Review wrote:
> >
> > From Jenkins CI :
> >
> > Jenkins CI has posted comments on this change.
> >
> > Change subject: pytest: he: Port 008_restart_he_vm.py to pytest
> > ..
> >
> >
> > Patch Set 12: Continuous-Integration-1
> >
> > Build Failed
> >
> > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14018/
> > : FAILURE
> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/14018//artifact/check-patch.he-basic_suite_master.el8.x86_64/mock_logs/script/stdout_stderr.log
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Extract appliance to
> local VM directory]
> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "dest":
> "/var/tmp/localvm3i6cjs21", "extract_results": {"cmd":
> ["/usr/bin/gtar", "--extract", "-C", "/var/tmp/localvm3i6cjs21", "-z",
> "--show-transformed-names", "--sparse", "-f",
> "/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova"],
> "err": "/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot write: Input/output error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot utime: Input/output error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot change ownership to uid 0, gid 0: Input/output
> error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d:
> Cannot change mode to rwxr-xr-x: Input/output error\n/usr/bin/gtar:
> images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d.meta:
> Cannot open: Input/output error\n/usr/bin/gtar: Exiting with failure
> status due to previous errors\n", "out": "", "rc": 2}, "handler":
> "TgzArchive", "msg": "failed to unpack
> /usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova
> to /var/tmp/localvm3i6cjs21", "src":
> "/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova"}
> Other such failures already happened several times recently. Perhaps
> some disk-space issue? Or something similar?
> Thanks,
> >
> >
> > --
> > To view, visit https://gerrit.ovirt.org/112273
> > To unsubscribe, visit https://gerrit.ovirt.org/settings
> >
> > Gerrit-Project: ovirt-system-tests
> > Gerrit-Branch: master
> > Gerrit-MessageType: comment
> > Gerrit-Change-Id: Ib510a1624ac5baad0f637a96919c5fd6040e89aa
> > Gerrit-Change-Number: 112273
> > Gerrit-PatchSet: 12
> > Gerrit-Owner: Yedidyah Bar David
> > Gerrit-Reviewer: Anonymous Coward (1001916)
> > Gerrit-Reviewer: Anton Marchukov
> > Gerrit-Reviewer: Dafna Ron
> > Gerrit-Reviewer: Dusan Fodor
> > Gerrit-Reviewer: Gal Ben Haim
> > Gerrit-Reviewer: Galit Rosenthal
> > Gerrit-Reviewer: Jenkins CI
> > Gerrit-Reviewer: Marcin Sobczyk
> > Gerrit-Reviewer: Yedidyah Bar David
> > Gerrit-Comment-Date: Tue, 24 Nov 2020 18:54:46 +
> > Gerrit-HasComments: No
> >
> --
> Didi
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100151)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/UAE53SYT47ONV5HNNRO6LHNPOTJ3QYFK/
[JIRA] (OVIRT-3053) [FIRING:1] LowDiskSpace_NodeExporter_v1_0 resources.ovirt.org:9100 ovirt-resources (/dev/mapper/resources_lvm-data ext4 /srv/resources)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-3053:
Resolution: Fixed
Status: Done (was: To Do)
DIsk now has a sufficient amount of free space
> [FIRING:1] LowDiskSpace_NodeExporter_v1_0 resources.ovirt.org:9100
> ovirt-resources (/dev/mapper/resources_lvm-data ext4 /srv/resources)
> ---
>
> Key: OVIRT-3053
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3053
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="LowDiskSpace_NodeExporter_v1_0",instance="resources.ovirt.org:9100",job="ovirt-resources"}
>
> Labels:
> - alertname = LowDiskSpace_NodeExporter_v1_0
> - device = /dev/mapper/resources_lvm-data
> - fstype = ext4
> - instance = resources.ovirt.org:9100
> - job = ovirt-resources
> - mountpoint = /srv/resources
> Annotations:
> - description = resources.ovirt.org:9100 of job ovirt-resources has less
> than 10% free disk space
> Source:
> http://prometheus-0:9090/graph?g0.expr=node_filesystem_free_bytes+%2F+node_filesystem_size_bytes%7Bdevice%21%3D%22tmpfs%22%7D+%3C+0.2&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100149)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/MWR6MGWUDXPPR6L74MMYMTQ3ZVA53HQO/
[JIRA] (OVIRT-3051) [FIRING:1] LowDiskSpace_NodeExporter_v1_0 resources.ovirt.org:9100 ovirt-resources (/dev/mapper/resources_lvm-data ext4 /srv/resources)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-3051:
Resolution: Fixed
Status: Done (was: To Do)
This alert was fired before the cleanup occurred.
Let's re-adjust the alert rule to wait for a longer period of time before
firing the alert.
> [FIRING:1] LowDiskSpace_NodeExporter_v1_0 resources.ovirt.org:9100
> ovirt-resources (/dev/mapper/resources_lvm-data ext4 /srv/resources)
> ---
>
> Key: OVIRT-3051
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3051
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="LowDiskSpace_NodeExporter_v1_0",instance="resources.ovirt.org:9100",job="ovirt-resources"}
>
> Labels:
> - alertname = LowDiskSpace_NodeExporter_v1_0
> - device = /dev/mapper/resources_lvm-data
> - fstype = ext4
> - instance = resources.ovirt.org:9100
> - job = ovirt-resources
> - mountpoint = /srv/resources
> Annotations:
> - description = resources.ovirt.org:9100 of job ovirt-resources has less
> than 10% free disk space
> Source:
> http://prometheus-0:9090/graph?g0.expr=node_filesystem_free_bytes+%2F+node_filesystem_size_bytes%7Bdevice%21%3D%22tmpfs%22%7D+%3C+0.2&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100149)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/3E57QIVCZXGQUESBOPNP3DYNP3E6B25O/
[JIRA] (OVIRT-3040) [FIRING:1] InstanceUnreachable ibm-srv03.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv03.ovirt.org true external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40873#comment-40873
]
Shlomi Zidmi commented on OVIRT-3040:
-
Node is back online and reachable, however something went wrong with it
yesterday and caused it to crash. I’m investigating what was the root cause for
this.
> [FIRING:1] InstanceUnreachable ibm-srv03.ovirt.org kubernetes-nodes-exporter
> (amd64 linux ibm-srv03.ovirt.org true external bare-metal-external ci)
> ---
>
> Key: OVIRT-3040
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3040
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv03.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv03.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv03.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv03.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100149)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/ZEIK4JZJWAHPBASOG7D7G24XHTVBJWWL/
[JIRA] (OVIRT-3027) [FIRING:1] LowDiskSpace_NodeExporter_v1_0 templates.ovirt.org:9100 templates-server (/dev/mapper/templates-kubevirt xfs /var/www/html/kubevirt)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40844#comment-40844
]
Shlomi Zidmi commented on OVIRT-3027:
-
The volume which stores all Kubevirt’s images on templates server is using 96GB
out of 110GB possible.
By looking at the following from Kubevirt’s repo:
[https://github.com/kubevirt/common-templates/blob/master/automation/test.sh#L110|https://github.com/kubevirt/common-templates/blob/master/automation/test.sh#L110]
[https://github.com/kubevirt/common-templates/blob/master/automation/test.sh#L138|https://github.com/kubevirt/common-templates/blob/master/automation/test.sh#L138]
I can see the image “win01.img“ is not being used and is not listed with all
other windows images. If that’s the case we can delete it and free up 25GB.
[~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] could you please
confirm this?
> [FIRING:1] LowDiskSpace_NodeExporter_v1_0 templates.ovirt.org:9100
> templates-server (/dev/mapper/templates-kubevirt xfs /var/www/html/kubevirt)
> ---
>
> Key: OVIRT-3027
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3027
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="LowDiskSpace_NodeExporter_v1_0",instance="templates.ovirt.org:9100",job="templates-server"}
>
> Labels:
> - alertname = LowDiskSpace_NodeExporter_v1_0
> - device = /dev/mapper/templates-kubevirt
> - fstype = xfs
> - instance = templates.ovirt.org:9100
> - job = templates-server
> - mountpoint = /var/www/html/kubevirt
> Annotations:
> - description = templates.ovirt.org:9100 of job templates-server has less
> than 10% free disk space
> Source:
> http://prometheus-0:9090/graph?g0.expr=node_filesystem_free_bytes+%2F+node_filesystem_size_bytes%7Bdevice%21%3D%22tmpfs%22%7D+%3C+0.2&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100147)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/B6EXJGYFGGGF3FCZ3MQYNSCO6DGDN7J6/
[JIRA] (OVIRT-3017) the /boot partition is almost 100% full on some of our IBM BM
Shlomi Zidmi created OVIRT-3017: --- Summary: the /boot partition is almost 100% full on some of our IBM BM Key: OVIRT-3017 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3017 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Shlomi Zidmi Assignee: infra /boot needs to be cleaned up before it goes 100% full -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100146) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/KARP3BTW4R67MJ66PICOL6VMR2B4RBGV/
[JIRA] (OVIRT-2997) [FIRING:1] InstanceUnreachable ibm-srv04.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv04.ovirt.org true external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2997:
Resolution: Fixed
Status: Done (was: To Do)
Closing as the node has been stable for few weeks now
> [FIRING:1] InstanceUnreachable ibm-srv04.ovirt.org kubernetes-nodes-exporter
> (amd64 linux ibm-srv04.ovirt.org true external bare-metal-external ci)
> ---
>
> Key: OVIRT-2997
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2997
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv04.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv04.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv04.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv04.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100146)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
[JIRA] (OVIRT-3002) [FIRING:1] InstanceUnreachable ibm-srv02.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv02.ovirt.org true external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-3002:
Resolution: Fixed
Status: Done (was: To Do)
Closing as the node has been stable for few weeks now
> [FIRING:1] InstanceUnreachable ibm-srv02.ovirt.org kubernetes-nodes-exporter
> (amd64 linux ibm-srv02.ovirt.org true external bare-metal-external ci)
> ---
>
> Key: OVIRT-3002
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3002
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv02.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv02.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv02.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv02.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100146)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
[JIRA] (OVIRT-3003) [FIRING:1] InstanceUnreachable ibm-srv06.ovirt.org kubernetes-nodes-exporter (amd64 linux true true ibm-srv06.ovirt.org true external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-3003:
Resolution: Fixed
Status: Done (was: To Do)
Closing as the node has been stable for few weeks now
> [FIRING:1] InstanceUnreachable ibm-srv06.ovirt.org kubernetes-nodes-exporter
> (amd64 linux true true ibm-srv06.ovirt.org true external bare-metal-external
> ci)
> -
>
> Key: OVIRT-3003
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3003
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv06.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - cachenode = true
> - ci_kubevirt_io_cachenode = true
> - instance = ibm-srv06.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv06.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv06.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100146)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
[JIRA] (OVIRT-2998) [FIRING:1] InstanceUnreachable ibm-srv07.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv07.ovirt.org external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2998:
Resolution: Done
Status: Done (was: To Do)
> [FIRING:1] InstanceUnreachable ibm-srv07.ovirt.org kubernetes-nodes-exporter
> (amd64 linux ibm-srv07.ovirt.org external bare-metal-external ci)
> --
>
> Key: OVIRT-2998
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2998
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv07.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv07.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv07.ovirt.org
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv07.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100145)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/H3V2Y3YJ7QUFUAGHXZDUQMIOFYHA2ITU/
[JIRA] (OVIRT-3000) [FIRING:1] InstanceUnreachable ibm-srv08.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv08.ovirt.org external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-3000:
Resolution: Done
Status: Done (was: To Do)
> [FIRING:1] InstanceUnreachable ibm-srv08.ovirt.org kubernetes-nodes-exporter
> (amd64 linux ibm-srv08.ovirt.org external bare-metal-external ci)
> --
>
> Key: OVIRT-3000
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3000
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv08.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv08.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv08.ovirt.org
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv08.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100145)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/POPV6NR2SMKX7DTSFJG7DV2EHG4TTRBA/
[JIRA] (OVIRT-3001) [FIRING:1] InstanceUnreachable ibm-srv09.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv09.ovirt.org true external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-3001:
Resolution: Done
Status: Done (was: To Do)
> [FIRING:1] InstanceUnreachable ibm-srv09.ovirt.org kubernetes-nodes-exporter
> (amd64 linux ibm-srv09.ovirt.org true external bare-metal-external ci)
> ---
>
> Key: OVIRT-3001
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3001
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv09.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv09.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv09.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv09.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100145)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/HYAWPFZRXV5ZM55AIP5C6GHRDY6E2JLN/
[JIRA] (OVIRT-2996) [FIRING:1] InstanceUnreachable ibm-srv02.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv02.ovirt.org true external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2996:
Resolution: Fixed
Status: Done (was: To Do)
This was cause due to /var/lib/origin being 100% full.
We are now monitoring the disks and investigating the root cause, as we still
don't know why the origin-node service crashes
> [FIRING:1] InstanceUnreachable ibm-srv02.ovirt.org kubernetes-nodes-exporter
> (amd64 linux ibm-srv02.ovirt.org true external bare-metal-external ci)
> ---
>
> Key: OVIRT-2996
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2996
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv02.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv02.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv02.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv02.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100144)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/NDTFB2P6CDKA7BFYL6WQVVD5USG2YGSO/
[JIRA] (OVIRT-2991) [FIRING:1] InstanceUnreachable ibm-srv05.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv05.ovirt.org true external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2991:
Status: To Do (was: In Progress)
> [FIRING:1] InstanceUnreachable ibm-srv05.ovirt.org kubernetes-nodes-exporter
> (amd64 linux ibm-srv05.ovirt.org true external bare-metal-external ci)
> ---
>
> Key: OVIRT-2991
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2991
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv05.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv05.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv05.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv05.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100142)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/LO2P6EUGMMRCAV2F3GVLKKUHMVETNRHF/
[JIRA] (OVIRT-2992) [FIRING:1] TestAlert
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2992:
Resolution: Fixed
Status: Done (was: To Do)
> [FIRING:1] TestAlert
> -
>
> Key: OVIRT-2992
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2992
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels: ALERT{alertname="TestAlert"}
>
> Labels:
> - alertname = TestAlert
> - label1 = value1
> Annotations:
> Source:
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100142)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/WKUGPBMGXIKCJXO3CUANQ2LNWHMS2TZK/
[JIRA] (OVIRT-2994) Occasionally we see alerts on dead node-exporters on OpenShift nodes
Shlomi Zidmi created OVIRT-2994: --- Summary: Occasionally we see alerts on dead node-exporters on OpenShift nodes Key: OVIRT-2994 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2994 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Shlomi Zidmi Assignee: infra Priority: Low We need to check what is happening behind the scenes when node-exporters are crashing and probably other containers too. Most times OpenShift is able to recover automatically, yet sometimes we have to fix it manually. Creating a ticket for investigating this issue -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100142) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/UGFRLF47FRE4RCJMH7EEVZGQTYPJQJ44/
[JIRA] (OVIRT-2991) [FIRING:1] InstanceUnreachable ibm-srv05.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv05.ovirt.org true external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2991:
Resolution: Fixed
Status: Done (was: To Do)
> [FIRING:1] InstanceUnreachable ibm-srv05.ovirt.org kubernetes-nodes-exporter
> (amd64 linux ibm-srv05.ovirt.org true external bare-metal-external ci)
> ---
>
> Key: OVIRT-2991
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2991
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv05.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv05.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv05.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv05.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100141)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/2ZDTB4Y2XHVO2E5PKR6ZGDQS7PZ3TXQM/
[JIRA] (OVIRT-2991) [FIRING:1] InstanceUnreachable ibm-srv05.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv05.ovirt.org true external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi reopened OVIRT-2991:
-
> [FIRING:1] InstanceUnreachable ibm-srv05.ovirt.org kubernetes-nodes-exporter
> (amd64 linux ibm-srv05.ovirt.org true external bare-metal-external ci)
> ---
>
> Key: OVIRT-2991
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2991
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv05.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv05.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv05.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv05.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100141)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/C2JLVU6HIMEK6DADKAMFHAMQQLCVUZWB/
[JIRA] (OVIRT-2989) [FIRING:1] InstanceUnreachable ibm-srv03.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv03.ovirt.org true external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2989:
Resolution: Fixed
Status: Done (was: To Do)
> [FIRING:1] InstanceUnreachable ibm-srv03.ovirt.org kubernetes-nodes-exporter
> (amd64 linux ibm-srv03.ovirt.org true external bare-metal-external ci)
> ---
>
> Key: OVIRT-2989
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2989
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv03.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv03.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv03.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv03.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100141)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/H6VCQTAQKIQ726FJXUENCABBEMPHFUFB/
[JIRA] (OVIRT-2990) [FIRING:1] InstanceUnreachable ibm-srv04.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv04.ovirt.org true external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2990:
Resolution: Fixed
Status: Done (was: To Do)
> [FIRING:1] InstanceUnreachable ibm-srv04.ovirt.org kubernetes-nodes-exporter
> (amd64 linux ibm-srv04.ovirt.org true external bare-metal-external ci)
> ---
>
> Key: OVIRT-2990
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2990
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv04.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv04.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv04.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv04.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100141)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/4WVAFQZXAZSL7EFA5W3JL25ZMGLUWXAN/
[JIRA] (OVIRT-2987) [FIRING:1] InstanceUnreachable ibm-srv06.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv06.ovirt.org true external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2987:
Resolution: Fixed
Status: Done (was: To Do)
> [FIRING:1] InstanceUnreachable ibm-srv06.ovirt.org kubernetes-nodes-exporter
> (amd64 linux ibm-srv06.ovirt.org true external bare-metal-external ci)
> ---
>
> Key: OVIRT-2987
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2987
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv06.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv06.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv06.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv06.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100141)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/OAYZUANRMMTNP4KUG3OLJWQDQFYR6I66/
[JIRA] (OVIRT-2988) [FIRING:1] InstanceUnreachable ibm-srv02.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv02.ovirt.org true external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2988:
Resolution: Fixed
Status: Done (was: To Do)
> [FIRING:1] InstanceUnreachable ibm-srv02.ovirt.org kubernetes-nodes-exporter
> (amd64 linux ibm-srv02.ovirt.org true external bare-metal-external ci)
> ---
>
> Key: OVIRT-2988
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2988
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv02.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv02.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv02.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv02.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100141)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/E2PF4TR27VRMYNJ2LZ3FDSKBYVVFG4CV/
[JIRA] (OVIRT-2986) [FIRING:1] InstanceUnreachable ibm-srv01.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv01.ovirt.org true external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2986:
Resolution: Fixed
Status: Done (was: To Do)
> [FIRING:1] InstanceUnreachable ibm-srv01.ovirt.org kubernetes-nodes-exporter
> (amd64 linux ibm-srv01.ovirt.org true external bare-metal-external ci)
> ---
>
> Key: OVIRT-2986
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2986
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels:
> ALERT{alertname="InstanceUnreachable",instance="ibm-srv01.ovirt.org",job="kubernetes-nodes-exporter"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv01.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv01.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv01.ovirt.org of job kubernetes-nodes-exporter has
> been possibly down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100141)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/UCLLJ6J4ZFLZ2GSCQTZGEKCWMHVR2VMM/
[JIRA] (OVIRT-2980) [FIRING:1] TestAlert
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2980:
Resolution: Fixed
Status: Done (was: To Do)
> [FIRING:1] TestAlert
> -
>
> Key: OVIRT-2980
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2980
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels: ALERT{alertname="TestAlert"}
>
> Labels:
> - alertname = TestAlert
> - url = simple_url.com
> Annotations:
> Source:
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100140)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/IXCKU4OT5PYLLKCCYC2ICE6NHRIDECUS/
[JIRA] (OVIRT-2977) [FIRING:1] TestAlert
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi closed OVIRT-2977.
---
Resolution: Fixed
> [FIRING:1] TestAlert
> -
>
> Key: OVIRT-2977
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2977
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels: ALERT{alertname="TestAlert"}
>
> Labels:
> - alertname = TestAlert
> - label1 = value1
> Annotations:
> Source:
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100134)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/A2C3OT3WOTAMQZ3T7PZYH35AN4YZX6N6/
[JIRA] (OVIRT-2979) a new project on jira for jiralert test tickets
Shlomi Zidmi created OVIRT-2979: --- Summary: a new project on jira for jiralert test tickets Key: OVIRT-2979 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2979 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Shlomi Zidmi Assignee: infra Priority: Low This ticket is for creating a dummy project on Jira that could be linked with Jiralert. Such a project would be helpful in testing different use cases. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100134) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/6YEJBGOLQED6XKFV4653IPXAW3AC7OWM/
[JIRA] (OVIRT-2977) [FIRING:1] TestAlert
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40649#comment-40649
]
Shlomi Zidmi commented on OVIRT-2977:
-
This ticket is for examining how Jiralert acts when there is already an open
ticket with the same alert, but different labels and values
> [FIRING:1] TestAlert
> -
>
> Key: OVIRT-2977
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2977
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels: ALERT{alertname="TestAlert"}
>
> Labels:
> - alertname = TestAlert
> - label1 = value1
> Annotations:
> Source:
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100134)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/5BTZQATEUXZIMPZSNAQAHE4FCDLTPHEZ/
[JIRA] (OVIRT-2977) [FIRING:1] TestAlert
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2977:
Status: In Progress (was: To Do)
> [FIRING:1] TestAlert
> -
>
> Key: OVIRT-2977
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2977
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels: ALERT{alertname="TestAlert"}
>
> Labels:
> - alertname = TestAlert
> - label1 = value1
> Annotations:
> Source:
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100134)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/Z6HM5RNXQY7EPPCOLRQXYTWQ47QKYFL2/
[JIRA] (OVIRT-2974) Tickets aren't created for fired alerts in Prometheus
Shlomi Zidmi created OVIRT-2974: --- Summary: Tickets aren't created for fired alerts in Prometheus Key: OVIRT-2974 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2974 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Shlomi Zidmi Assignee: infra There is a broken node_exporter on one of openshift nodes (shift-n12), however we haven't been notified about it with a ticket. For some reason, even though all application are running (Prometheus, Alertmanager, Jiralert) no ticket has been created for the broken exporter. Opening a ticket for investigating the issue -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100133) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/QYTIAGJF7423YHWY5VWYI5TTQ6E2AOWT/
[JIRA] (OVIRT-2973) [FIRING:1] TestAlert
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2973:
Resolution: Fixed
Status: Done (was: To Do)
Making sure jiralert is functioning properly
> [FIRING:1] TestAlert
> -
>
> Key: OVIRT-2973
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2973
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels: ALERT{alertname="TestAlert"}
>
> Labels:
> - alertname = TestAlert
> - key = value
> Annotations:
> Source:
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100133)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/FUPKC7L5ZMGMPSSF5DBCTI6O3WJ46TZA/
[JIRA] (OVIRT-2972) resources.ovirt.org ran out of space for artifact publishing
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40636#comment-40636
]
Shlomi Zidmi commented on OVIRT-2972:
-
Actually we are monitoring [resources.ovirt.org|http://resources.ovirt.org] in
Prometheus, and should have caught this on time
!prom.png|width=83.34%!
Looking at the alert rules defined, i see the following:
{noformat}node_filesystem_free_bytes
/ node_filesystem_size_bytes{device!="tmpfs"} < 0.1{noformat}
The blue line (/dev/sdb - mounted on /home/jenkins) in the picture is slightly
above 0.1, and that’s why no alerts were fired. I’ll readjust the threshold so
that Prometheus would be able to catch similar issues sooner next time.
> resources.ovirt.org ran out of space for artifact publishing
>
>
> Key: OVIRT-2972
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2972
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Evgheni Dereveanchin
>Assignee: infra
> Attachments: image-20200720-083159.png, prom.png
>
>
> This weekend Nagios sent disk space alerts for the /home/jenkins on
> resources.ovirt.org
> AFAIR this is used as intermediate artifact storage for publishing and
> shouldn't fill up that much. Logging a ticket to investigate the root cause.
> The partition is free again now so this is not blocking anything right now.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100133)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GCEF7PM4O43IYGDBGZSYWSBVX255V5CG/
[JIRA] (OVIRT-2956) jobs are getting "unauthorized" messages when trying to access Openshift api
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi reassigned OVIRT-2956:
---
Assignee: Shlomi Zidmi (was: infra)
> 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: Shlomi Zidmi
>
> 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)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/4V5GZ4VEKDN5KX75BCPHA2G5VNCS7ZC4/
[JIRA] (OVIRT-2956) jobs are getting "unauthorized" messages when trying to access Openshift api
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40568#comment-40568
]
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)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/7TZQKFD3YHLRKX2WL5QU6KUHQDHVNW6T/
[JIRA] (OVIRT-2956) jobs are getting "unauthorized" messages when trying to access Openshift api
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)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/HJTN6WHHQLPDYYFRLYMNUCSI7M42HCHF/
[JIRA] (OVIRT-2954) "ignoring unsafe symlink" messages while syncing oVirt content
Shlomi Zidmi created OVIRT-2954: --- Summary: "ignoring unsafe symlink" messages while syncing oVirt content Key: OVIRT-2954 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2954 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Shlomi Zidmi Assignee: infra Priority: Low One of oVirt's mirrors encountered these messages while syncing content: ignoring unsafe symlink "ovirt-master-snapshot/iso" -> "/var/www/html/repos/ovirt/tested/master/iso" ignoring unsafe symlink "yum-repo/ovirt-release-master.rpm" -> "/var/www/html/pub/ovirt-master-snapshot/rpm/el8/noarch/ovirt-release-master-4.4.0-0.3.master.20200526011129.gitbb3bf5a.el8.noarch.rpm" ignoring unsafe symlink "yum-repo/ovirt-release42-snapshot.rpm" -> "/var/www/html/pub/ovirt-4.2-snapshot/rpm/el7/noarch/ovirt-release42-snapshot-4.2.8-1.el7.noarch.rpm" ignoring unsafe symlink "yum-repo/ovirt-release43-snapshot.rpm" -> "/var/www/html/pub/ovirt-4.3-snapshot/rpm/el7/noarch/ovirt-release43-snapshot-4.3.10.1-0.0.master.20200423025322.git7a4b609.el7.noarch.rpm" Probably snapshots should not be found on our repos, so let's see if they can be removed. Otherwise, let's fix that so our mirrors won't see these messages again -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100128) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GWIMVWTPX54CZZ6AJVWSJCRB3MLRUDUY/
[JIRA] (OVIRT-2948) [FIRING:1] InstanceUnreachable (amd64 linux shift-m02.phx.ovirt.org kubernetes-nodes-exporter shift-m02.phx.ovirt.org true true infra default)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi reassigned OVIRT-2948:
---
Assignee: Shlomi Zidmi (was: infra)
> [FIRING:1] InstanceUnreachable (amd64 linux shift-m02.phx.ovirt.org
> kubernetes-nodes-exporter shift-m02.phx.ovirt.org true true infra default)
> --
>
> Key: OVIRT-2948
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2948
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: Shlomi Zidmi
> Labels: ALERT{alertname="InstanceUnreachable"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = shift-m02.phx.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = shift-m02.phx.ovirt.org
> - logging_infra_fluentd = true
> - node_role_kubernetes_io_master = true
> - region = infra
> - zone = default
> Annotations:
> - description = shift-m02.phx.ovirt.org of job kubernetes-nodes-exporter has
> been down for more than 10 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100127)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/CV3FGT3WKCO2IBKPYKVSRB6O3HUCJ77D/
[JIRA] (OVIRT-2945) modify the alert_old_patches script to post additional information when it sends emails
Shlomi Zidmi created OVIRT-2945: --- Summary: modify the alert_old_patches script to post additional information when it sends emails Key: OVIRT-2945 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2945 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Shlomi Zidmi Assignee: infra Priority: Low Currently emails only contain URLs for the relevant patches. It could be nice if the script would be able to also send the subject of each patch for example, or anything that can be useful for the reader. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100127) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/VWV76GOO4WCT5A6V7KHOPMAGT7VQCQCW/
[JIRA] (OVIRT-2945) modify the alert_old_patches script to post additional information when it sends emails
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shlomi Zidmi reassigned OVIRT-2945: --- Assignee: Shlomi Zidmi (was: infra) > modify the alert_old_patches script to post additional information when it > sends emails > > > Key: OVIRT-2945 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2945 > Project: oVirt - virtualization made easy > Issue Type: Improvement >Reporter: Shlomi Zidmi >Assignee: Shlomi Zidmi >Priority: Low > > Currently emails only contain URLs for the relevant patches. > It could be nice if the script would be able to also send the subject of each > patch for example, or anything that can be useful for the reader. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100127) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/EBWSX5BDY2MHFF3BLUWLRP4MCCWABAML/
[JIRA] (OVIRT-2944) RE: [ftpcom] oVirt mirror out of sync
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shlomi Zidmi reassigned OVIRT-2944: --- Assignee: Shlomi Zidmi (was: infra) > RE: [ftpcom] oVirt mirror out of sync > - > > Key: OVIRT-2944 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2944 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Erwin Bronkhorst - Studenten Net Twente >Assignee: Shlomi Zidmi > > Hello Shlomi, hello infrastructure support team, > > We have recently noticed you are quite out of sync with mirroring oVirt > > content (last synced more than a year ago). > Thank you for bringing this issue to our attention. A while ago, we migrated > to a new server and a new maintainer for the oVirt mirror, and something went > definitely wrong in these processes. Sorry for the inconvenience. > I think the major issue is that the public key that you have added is not in > use anymore by us. > Could you please replace the old key (for the mirror at > ftp://ftp.snt.utwente.nl (Studenten Net Twente)) with this one? > ssh-rsa > B3NzaC1yc2EDAQABAAACAQDcEujUQ3DLIGiuOCg0ZlLqZhQY/uHFw2O9cMY6SrlG11tZ0oiwk6+x8dZsBN0kAN7zd1IIOo4+E0cMYUrkiwj6dzVc/oKY9RtTCOKhmqq1tnPxKSpOXY+CZxm7e63uVx8CpVjhj/lOMnfL3jzyBbNfURsSgY+6edSkDGzy3ptaXBDlrVI4F5+2rjKI3VgflshjUUZo1Di22snnZ5zoB8tT/Q8MBMjnMtQcPqjPL/VgfbgKwFfgLOnZtXzTnAjMK14IA5XLN9PCrPtEajRM8mtesqkYSMoZ1KqKPGwZspIijKrnoYNeKjkZxZAq9xijboj4GboHxsKRxckaw686qrfpPdPHNrgtKZZNxO5RB+/tgNLBM1l0g/9rEAN2Pvytg2Ifahk20oEodCzW1qsCBWl6+4NwV8iW87rgN+AgibNg/QmEd2SKNHAhOldEPFpHQqDRHo6ZJY5XbOEepK/ti3UOzV/mQ4u1PnKpZBoqWmM9MWBOEMZP7Ems4DHR5vdAvYs8TrzgTasoOe/MkFZ9FZ31XRL4loyPU9gid06ENA+Yc9xyRssUtjNsQfCNV+enSzbMBr4FvWmSoJNoVbQyi3tj13emflBqP+rROpeG7mgol+aP49z3RW56wOS0dhFqg8AXRyp1QLld/rJXzb3UH5l7WTXhX7DCuySezxhEyi1lGw== > ftp...@ftp.snt.utwente.nl > Then I will try to set-up our scripting in order to get the mirror in sync as > soon as possible. > Kind regards, > Erwin Bronkhorst > FTPCom Studenten Net Twente > Van: Shlomi Zidmi > Verzonden: dinsdag 19 mei 2020 19:01 > Aan: ftp...@snt.utwente.nl > Onderwerp: [ftpcom] oVirt mirror out of sync > Hello from the oVirt infrastructure team, > We have recently noticed you are quite out of sync with mirroring oVirt > content (last synced more than a year ago). > If you are still interested in mirroring oVirt, please keep your mirror up to > date with our public content. > Otherwise, please let us know and you will be removed from our mirror list: > https://www.ovirt.org/community/get-involved/repository-mirrors.html > Thanks, > Shlomi > > oVirt community -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100127) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/CW52NXMIQPLPYPXWO2G3QLY5FYUU2SN6/
[JIRA] (OVIRT-2942) [FIRING:1] MirrorIsOutOfSync (raw.githubusercontent.com:80 oVirt-mirrors-health http://ftp.snt.utwente.nl/pub/software/ovirt)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi reassigned OVIRT-2942:
---
Assignee: Shlomi Zidmi (was: infra)
> [FIRING:1] MirrorIsOutOfSync (raw.githubusercontent.com:80
> oVirt-mirrors-health http://ftp.snt.utwente.nl/pub/software/ovirt)
> -
>
> Key: OVIRT-2942
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2942
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: Shlomi Zidmi
> Labels: ALERT{alertname="MirrorIsOutOfSync"}
>
> Labels:
> - alertname = MirrorIsOutOfSync
> - instance = raw.githubusercontent.com:80
> - job = oVirt-mirrors-health
> - url = http://ftp.snt.utwente.nl/pub/software/ovirt
> Annotations:
> - description = http://ftp.snt.utwente.nl/pub/software/ovirt (measured by
> oVirt-mirrors-health) has not been synced in the past two days.
> Source:
> http://prometheus-0:9090/graph?g0.expr=mirror_health_check+%3E+172800&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100126)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/SHJK537UBR73OEYG7TTAE2D3B7RUK645/
[JIRA] (OVIRT-2933) [FIRING:1] LowPercentageOfAvailDiskSpace (amd64 linux rootfs rootfs shift-n12.phx.ovirt.org kubernetes-nodes-exporter shift-n12.phx.ovirt.org / true primary vm ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi reassigned OVIRT-2933:
---
Assignee: Shlomi Zidmi (was: infra)
> [FIRING:1] LowPercentageOfAvailDiskSpace (amd64 linux rootfs rootfs
> shift-n12.phx.ovirt.org kubernetes-nodes-exporter shift-n12.phx.ovirt.org /
> true primary vm ci)
> ---
>
> Key: OVIRT-2933
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2933
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: Shlomi Zidmi
> Labels: ALERT{alertname="LowPercentageOfAvailDiskSpace"}
>
> Labels:
> - alertname = LowPercentageOfAvailDiskSpace
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - device = rootfs
> - fstype = rootfs
> - instance = shift-n12.phx.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = shift-n12.phx.ovirt.org
> - mountpoint = /
> - node_role_kubernetes_io_compute = true
> - region = primary
> - type = vm
> - zone = ci
> Annotations:
> - description = shift-n12.phx.ovirt.org (measured by
> kubernetes-nodes-exporter) has low percentage of avaiable disk space
> (16.1776291934924) over 60 minutes.
> - summary = shift-n12.phx.ovirt.org - Low percentage of available disk space
> Source:
> http://prometheus-0:9090/graph?g0.expr=node_filesystem_free%7Bdevice%3D%22rootfs%22%7D+%2F+node_filesystem_size%7Bdevice%3D%22rootfs%22%7D+%2A+100+%3C+25&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/QE26JB52MHPNYALXO2LKICDSMI6IALW7/
[JIRA] (OVIRT-2893) [FIRING:1] LowPercentageOfAvailDiskSpace (amd64 linux rootfs rootfs shift-n11.phx.ovirt.org kubernetes-nodes-exporter shift-n11.phx.ovirt.org / true primary vm ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi reassigned OVIRT-2893:
---
Assignee: Shlomi Zidmi (was: infra)
> [FIRING:1] LowPercentageOfAvailDiskSpace (amd64 linux rootfs rootfs
> shift-n11.phx.ovirt.org kubernetes-nodes-exporter shift-n11.phx.ovirt.org /
> true primary vm ci)
> ---
>
> Key: OVIRT-2893
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2893
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: Shlomi Zidmi
> Labels: ALERT{alertname="LowPercentageOfAvailDiskSpace"}
>
> Labels:
> - alertname = LowPercentageOfAvailDiskSpace
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - device = rootfs
> - fstype = rootfs
> - instance = shift-n11.phx.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = shift-n11.phx.ovirt.org
> - mountpoint = /
> - node_role_kubernetes_io_compute = true
> - region = primary
> - type = vm
> - zone = ci
> Annotations:
> - description = shift-n11.phx.ovirt.org (measured by
> kubernetes-nodes-exporter) has low percentage of avaiable disk space
> (22.22544650884642) over 5 minutes.
> - summary = shift-n11.phx.ovirt.org - Low percentage of available disk space
> Source:
> http://prometheus-0:9090/graph?g0.expr=node_filesystem_free%7Bdevice%3D%22rootfs%22%7D+%2F+node_filesystem_size%7Bdevice%3D%22rootfs%22%7D+%2A+100+%3C+25&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/6PZDEG35E2JONP66HIADYB6ZZPPNOA4B/
[JIRA] (OVIRT-2932) [FIRING:1] TestAlert
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2932:
Resolution: Done
Status: Done (was: To Do)
Test
> [FIRING:1] TestAlert
> -
>
> Key: OVIRT-2932
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2932
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels: ALERT{alertname="TestAlert"}
>
> Labels:
> - alertname = TestAlert
> - key = value
> Annotations:
> Source:
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/JJHCP5P24Z4BBFC6OOKO7I2XH4UPY5N2/
[JIRA] (OVIRT-2931) [FIRING:1] TooManyOpenFileDescriptors (amd64 linux ibm-srv05.ovirt.org kubernetes-nodes-exporter ibm-srv05.ovirt.org true external bare-metal-external ci)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi reassigned OVIRT-2931:
---
Assignee: Shlomi Zidmi (was: infra)
> [FIRING:1] TooManyOpenFileDescriptors (amd64 linux ibm-srv05.ovirt.org
> kubernetes-nodes-exporter ibm-srv05.ovirt.org true external
> bare-metal-external ci)
> --
>
> Key: OVIRT-2931
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2931
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: Shlomi Zidmi
> Labels: ALERT{alertname="TooManyOpenFileDescriptors"}
>
> Labels:
> - alertname = TooManyOpenFileDescriptors
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = ibm-srv05.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = ibm-srv05.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = external
> - type = bare-metal-external
> - zone = ci
> Annotations:
> - description = ibm-srv05.ovirt.org (measured by kubernetes-nodes-exporter)
> is holding too many open files (21.952) over 2 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=node_filefd_allocated+%2F+1000+%3E+20&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/QQZKTNERNQ6LKYGILRCL2ONLGDXMKW4R/
[JIRA] (OVIRT-2928) [FIRING:1] TestAlert
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2928:
Resolution: Fixed
Status: Done (was: To Do)
test
> [FIRING:1] TestAlert
> -
>
> Key: OVIRT-2928
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2928
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels: ALERT{alertname="TestAlert"}
>
> Labels:
> - alertname = TestAlert
> - key = value
> Annotations:
> Source:
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/OXVDXXK63UIJMI5WKGOE2S26T7LSQVT6/
[JIRA] (OVIRT-2927) [FIRING:1] TestAlert
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2927:
Resolution: Done
Status: Done (was: To Do)
test
> [FIRING:1] TestAlert
> -
>
> Key: OVIRT-2927
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2927
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels: ALERT{alertname="TestAlert"}
>
> Labels:
> - alertname = TestAlert
> - key = value
> Annotations:
> Source:
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/O4CZDC2CASSQY2MFL4Q7OBPMK3CLDGVY/
[JIRA] (OVIRT-2926) [FIRING:1] TestAlert
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2926:
Resolution: Fixed
Status: Done (was: To Do)
so far tickets have been created using a dedicated VM that runs Jiralert.
This ticket however was created using a deployment of Jiralert in OpenShift.
> [FIRING:1] TestAlert
> -
>
> Key: OVIRT-2926
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2926
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels: ALERT{alertname="TestAlert"}
>
> Labels:
> - alertname = TestAlert
> - key = value
> Annotations:
> Source:
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/2FOSO2V6GTGCKDRU5YDVSDTXCAYCFFPB/
[JIRA] (OVIRT-2918) sync_mirror for ovirt-master-centos-advanced-virtualization-el8 is failing
Shlomi Zidmi created OVIRT-2918: --- Summary: sync_mirror for ovirt-master-centos-advanced-virtualization-el8 is failing Key: OVIRT-2918 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2918 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Shlomi Zidmi Assignee: infra Priority: Low recently we've created a job for syncing a new mirror: https://jenkins.ovirt.org/job/system-sync_mirrors-ovirt-master-centos-advanced-virtualization-el8-x86_64/ this job has been failing since its creation. [~accountid:557058:3a069952-633d-482c-90ab-2451cac6751a] is the repo managed by you? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100125) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GOR7X3KLLW3D3DKQQKWZUNSPP5NZCFXG/
[JIRA] (OVIRT-2912) [FIRING:1] InstanceUnreachable (amd64 linux shift-n08.phx.ovirt.org kubernetes-nodes-exporter shift-n08.phx.ovirt.org true primary logs)
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2912:
Assignee: Shlomi Zidmi (was: infra)
Resolution: Fixed
Status: Done (was: To Do)
Resolved.
Port 9100 was blocked on shift-n08.phx.ovirt.org and Prometheus was not able to
scrape data.
> [FIRING:1] InstanceUnreachable (amd64 linux shift-n08.phx.ovirt.org
> kubernetes-nodes-exporter shift-n08.phx.ovirt.org true primary logs)
>
>
> Key: OVIRT-2912
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2912
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: Shlomi Zidmi
> Labels: ALERT{alertname="InstanceUnreachable"}
>
> Labels:
> - alertname = InstanceUnreachable
> - beta_kubernetes_io_arch = amd64
> - beta_kubernetes_io_os = linux
> - instance = shift-n08.phx.ovirt.org
> - job = kubernetes-nodes-exporter
> - kubernetes_io_hostname = shift-n08.phx.ovirt.org
> - node_role_kubernetes_io_compute = true
> - region = primary
> - zone = logs
> Annotations:
> - description = shift-n08.phx.ovirt.org of job kubernetes-nodes-exporter has
> been down for more than 1 minutes.
> Source:
> http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-exporter%22%7D+%3D%3D+0&g0.tab=1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/SWYF5RUITZ3MXDSNC6VWQ543ZBA2TKEJ/
[JIRA] (OVIRT-2913) [FIRING:1] TestAlert
[
https://ovirt-jira.atlassian.net/browse/OVIRT-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shlomi Zidmi updated OVIRT-2913:
Resolution: Done
Status: Done (was: To Do)
Test. Issue was created by AlertManager
> [FIRING:1] TestAlert
> -
>
> Key: OVIRT-2913
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2913
> Project: oVirt - virtualization made easy
> Issue Type: Bug
>Reporter: Alertmanager_Bot
>Assignee: infra
> Labels: ALERT{alertname="TestAlert"}
>
> Labels:
> - alertname = TestAlert
> - key = value
> Annotations:
> Source:
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100125)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/SAXTO6EYUIGDWTVA24S55X4734DVUCAY/
[JIRA] (OVIRT-2901) some sync_mirror jobs fail due to cache error of another repo
Shlomi Zidmi created OVIRT-2901: --- Summary: some sync_mirror jobs fail due to cache error of another repo Key: OVIRT-2901 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2901 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Shlomi Zidmi Assignee: infra Priority: Low In the recent days some sync_mirror jobs have been failing with the following error: Error setting up repositories: Error making cache directory: /home/jenkins/mirrors_cache/centos-qemu-ev-release-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-qemu-ev-release-el7' As an example, a build of fedora-updates-fc29 failed with this error: https://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc29-x86_64/1544/console -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100124) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/LKXWJQXWYITHJO2BJSY7QGKVFIAFIVIE/
[JIRA] (OVIRT-2895) Fwd: mirrors.phx.ovirt.org is down
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40245#comment-40245 ] Shlomi Zidmi commented on OVIRT-2895: - I’ve re-run the sync-mirrors job for centos-base-el8 and it seems like the missing packages were downloaded this time. For example, the package mentioned above “yum-utils-40.0.8-3“ is located under: /var/www/html/repos/yum/centos-base-el8/base/Packages/yum-utils-4.0.8-3.el8.noarch.rpm So either the problem is now resolved, or we are facing some other issue. [~accountid:5aa0f39f5a4d022884128a0f] any luck with re-running the patch? > Fwd: mirrors.phx.ovirt.org is down > -- > > Key: OVIRT-2895 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2895 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Anton Marchukov >Assignee: infra > > Forwarding to infra-support to open a ticket. > -- Forwarded message - > From: Yedidyah Bar David > Date: Thu, Apr 2, 2020 at 4:31 PM > Subject: mirrors.phx.ovirt.org is down > To: infra > Both from my laptop and e.g.: > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/6729/ > 17:23:21 + yum install '--disablerepo=*' > --enablerepo=ovirt-master-tested-el8,centos-base-el8,centos-appstream-el8,centos-powertools-el8,epel-el8,ovirt-master-glusterfs-7-el8,ovirt-master-virtio-win-latest-el8,ovirt-master-copr-sbonazzo-collection-el8,ovirt-master-copr:copr.fedorainfracloud.org: > sac:gluster-ansible-el8,ovirt-master-copr:copr.fedorainfracloud.org: > mdbarroso:ovsdbapp-el8,ovirt-master-copr-nmstate-0.2-el8,ovirt-master-copr-NetworkManager-1.22-el8,ovirt-master-centos-advanced-virtualization-el8,ovirt-master-centos-ovirt44-el8 > -y yum-utils > 17:23:21 Error: Error downloading packages: > 17:23:21 Status code: 404 for > http://mirrors.phx.ovirt.org/repos/yum/centos-base-el8/base/Packages/yum-utils-4.0.8-3.el8.noarch.rpm > Known problem? > -- > Didi > ___ > Infra mailing list -- infra@ovirt.org > To unsubscribe send an email to infra-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/BPER52OO73BBJW22W4UCEYKWCEQRI77M/ > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100123) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/CLHHLXDI3MJ34RP4Z3QDXCOE7OR7V6DM/
[JIRA] (OVIRT-2886) sync_mirrors jobs are failing due to reposync failure
Shlomi Zidmi created OVIRT-2886: --- Summary: sync_mirrors jobs are failing due to reposync failure Key: OVIRT-2886 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2886 Project: oVirt - virtualization made easy Issue Type: Task Components: CI Mirrors Reporter: Shlomi Zidmi Assignee: infra Jobs are failing with the following error: Error setting up repositories: failure: repodata/repomd.xml from centos-ovirt-4.3-testing-el7: [Errno 256] No more mirrors to try. http://cbs.centos.org/repos/virt7-ovirt-43-testing/x86_64/os/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100122) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/DR6IH6JHF42O64ZIPSM4WFAT2Y5LC3RW/
[JIRA] (OVIRT-2856) Requesting merge rights to ovirt-engine-sdk-ruby
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shlomi Zidmi updated OVIRT-2856: Assignee: Shlomi Zidmi (was: infra) Resolution: Done Status: Done (was: To Do) Done > Requesting merge rights to ovirt-engine-sdk-ruby > > > Key: OVIRT-2856 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2856 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: Ori Liel >Assignee: Shlomi Zidmi > > I need merge (+2) rights to ovirt-engine-sdk-ruby, as I am becoming a > maintainer of this project. > This request is approved by my manager Martin Perina and the existing > maintainers of this project, Ondra Machacek and Boris Odnopozov -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/DU7SILKHEK3CM7V3KLA2JWZ4FGUTIRUG/
