No such file or directory @ rb_sysopen - /etc/systemd/system/virtproxyd-tls.socket in container-puppet-nova_libvirt

Bug #2013330 reported by Ananya Banerjee
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Won't Fix
Critical
Unassigned

Bug Description

periodic-tripleo-ci-centos-9-ovb-3ctlr_1comp_1supp-featureset039-master and periodic-tripleo-ci-centos-9-ovb-3ctlr_1comp_1supp-featureset064-master are failing overcloud deploy

FATAL | Manage Puppet containers (generate config) for step 1 | overcloud-novacompute-0 | error={"changed": false, "msg": "Failed containers: container-puppet-nova_libvirt"}

https://logserver.rdoproject.org/74/47974/5/check/periodic-tripleo-ci-centos-9-ovb-3ctlr_1comp_1supp-featureset039-master/8fbba80/logs/overcloud-novacompute-0/var/log/containers/stdouts/container-puppet-nova_libvirt.log.txt.gz

https://logserver.rdoproject.org/74/47974/6/check/periodic-tripleo-ci-centos-9-ovb-3ctlr_1comp_1supp-featureset039-master/704feb8/logs/undercloud/home/zuul/overcloud_deploy.log.txt.gz

We are seeing this from 2023-03-29 03:57:24

Changed in tripleo:
status: New → Triaged
milestone: none → zed-1
importance: Undecided → Critical
tags: added: ci promotion-blocker
Revision history for this message
Ananya Banerjee (frenzyfriday) wrote : Re: OVB jobs in master (fs64 and fs39) are failing after task Manage container systemd services and cleanup old systemd healthchecks in overcloud deploy

In the logs I don not see it moving to task https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/deployment/podman/podman-baremetal-ansible.yaml#L158
probably that is where the jobs is failing

summary: - OVB jobs in master (fs64 and fs39) are failing task Manage container
- systemd services and cleanup old systemd healthchecks in overcloud
- deploy
+ OVB jobs in master (fs64 and fs39) are failing after task Manage
+ container systemd services and cleanup old systemd healthchecks in
+ overcloud deploy
description: updated
Revision history for this message
Ananya Banerjee (frenzyfriday) wrote :
Revision history for this message
Ananya Banerjee (frenzyfriday) wrote :

2023-03-30T09:17:49.509723014+00:00 stderr F <13>Mar 30 09:17:49 puppet-user: Error: /Stage[main]/Nova::Migration::Libvirt/File_line[virtproxyd-tls.socket ListenStream]: Could not evaluate: No such file or directory @ rb_sysopen - /etc/systemd/system/virtproxyd-tls.socket

https://logserver.rdoproject.org/74/47974/6/check/periodic-tripleo-ci-centos-9-ovb-3ctlr_1comp_1supp-featureset039-master/704feb8/logs/overcloud-novacompute-0/var/log/containers/stdouts/container-puppet-nova_libvirt.log.txt.gz

summary: - OVB jobs in master (fs64 and fs39) are failing after task Manage
- container systemd services and cleanup old systemd healthchecks in
- overcloud deploy
+ No such file or directory @ rb_sysopen - /etc/systemd/system/virtproxyd-
+ tls.socket in container-puppet-nova_libvirt
description: updated
Revision history for this message
Takashi Kajinami (kajinamit) wrote :

This is the issue caused by recent change in puppet-nova which fixed incomplete settings.
 https://review.opendev.org/c/openstack/puppet-nova/+/878541

We can probably fix the problem, but IMO we should stop monitoring master jobs because TripleO master is being abandoned.

Revision history for this message
Marios Andreou (marios-b) wrote (last edit ):
Revision history for this message
Takashi Kajinami (kajinamit) wrote (last edit ):

This is probably fixed by https://review.opendev.org/c/openstack/puppet-nova/+/879145, though it's no longer needed as we agree abandoning all master jobs.

Revision history for this message
Marios Andreou (marios-b) wrote :

Yeah @Takashi as posted in [1] the ci team has started the process of removing the master periodic rdo lines [2]

I am going to mark the bug as "won't fix" for the cix tracking.

[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-March/033080.html
[2] https://review.rdoproject.org/r/c/config/+/48074

Changed in tripleo:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.