Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop Ubuntu 16.04 from PIDFILE_COMPATIBLE_IMAGES #103

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

evgeni
Copy link
Member

@evgeni evgeni commented Oct 5, 2023

16.04 is long EOL

Copy link
Member

@ekohl ekohl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm cautious with dropping things when they don't break anything else. Perhaps when CentOS 7 goes EOL we can drop the whole "compatible images" part.

@evgeni
Copy link
Member Author

evgeni commented Oct 5, 2023

As for CentOS, the latest quay.io/centos/centos:centos7 seem to be working fine with systemd and pidfile (see https://github.com/voxpupuli/puppet-zabbix/actions/runs/6417557882/job/17423602472?pr=899), so I wonder if we should bump that too?

@ekohl
Copy link
Member

ekohl commented Oct 5, 2023

Are you sure the systemd unit file still uses PIDFile there? Perhaps the root cause in Docker is fixed? I see CentOS 8 times out on spinning up the machine, so that's not a real failure due to PIDFile.

@evgeni
Copy link
Member Author

evgeni commented Oct 5, 2023

[root@centos8-stream ~]# systemctl cat zabbix-server |grep PIDF
PIDFile=/var/run/zabbix/zabbix_server.pid

Pretty sure it does :)

@ekohl
Copy link
Member

ekohl commented Oct 5, 2023

Ok, so now I wonder if CentOS 8 would also work. If so, the real cause in Docker may be fixed and the whole workaround could be dropped.

@evgeni
Copy link
Member Author

evgeni commented Oct 5, 2023

How/where would I test this?
Re-running the test I linked still ends up in a timeout (https://github.com/voxpupuli/puppet-zabbix/actions/runs/6417557882/job/17425689790)
While other tests using c8s containers work fine: https://github.com/theforeman/puppet-foreman/actions/runs/6414499477/job/17415005261

@evgeni
Copy link
Member Author

evgeni commented Oct 5, 2023

Amazing. The linked run was from tonight. I re-ran it, and it ends up in a timeout: https://github.com/theforeman/puppet-foreman_proxy/actions/runs/6414497675/job/17426050721

What. The. Hell.

@evgeni
Copy link
Member Author

evgeni commented Oct 5, 2023

And now it passed out of all sudden. So maybe this workaround is not needed anymore.

@ekohl
Copy link
Member

ekohl commented Oct 5, 2023

We can confirm that with other module that have the pidfile workaround. We don't appear to apply it a lot:

$ rg pidfile modules/voxpupuli/*/.sync.yml
modules/voxpupuli/puppet-zabbix/.sync.yml
15:  pidfile_workaround: CentOS,Ubuntu

modules/voxpupuli/puppet-proxysql/.sync.yml
3:  pidfile_workaround: CentOS

modules/voxpupuli/puppet-openldap/.sync.yml
3:  pidfile_workaround: CentOS

modules/voxpupuli/puppet-mongodb/.sync.yml
5:  pidfile_workaround: CentOS,Ubuntu

modules/voxpupuli/puppet-hiera/.sync.yml
2:  pidfile_workaround: CentOS

modules/voxpupuli/puppet-chrony/.sync.yml
9:  pidfile_workaround: CentOS

@ekohl
Copy link
Member

ekohl commented Oct 5, 2023

Well, PRs are up so we'll see what CI says.

@ekohl
Copy link
Member

ekohl commented Oct 5, 2023

Results are mixed, but certainly still needed in places.

@bastelfreak
Copy link
Member

@evgeni can you rebase please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants