Elana Hashman

Can you point me to a specific package to test this behaviour? When you say 1.x, did you test with 1.10 or an earlier release?

Thanks for the cc @njsmith, is it possible to move this issue to the auditwheel repo?

I'm not a manylinux admin so I can't transfer it :( @dstufft can you please move this issue to auditwheel?

The other thing that comes to mind for this: if we mangle the symbols, then won't we have to go back into the Python code that uses them and change...

Feel free to make a PR for this, but I can't guarantee any fast turnaround times on review.

@saschagrunert I think we are heading into spaghetti territory for job configs. We currently have 8 image configs and 7 ignition files. Surely every single one isn't significantly different? Is...

are we sure? the latest run failed: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/92316/pull-kubernetes-node-kubelet-serial-crio-cgroupv1/1491479336685932544/ ``` I0209 18:43:12.996] unable to create gce instance with running docker daemon for image fedora-coreos-35-20220116-3-0-gcp-x86-64. instance n1-standard-2-fedora-coreos-35-20220116-3-0-gcp-x86-64-2c22c0ee not running docker/containerd/crio daemon -...

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/92316/pull-kubernetes-node-kubelet-serial-crio-cgroupv1/1499826327681765376/ Still failing :\

Still doesn't appear to be working https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/92316/pull-kubernetes-node-kubelet-serial-crio-cgroupv2/1506314449798041600/

This might get closed by the k/k PR, but we need to still update the cri-o jobs to set the env var.