Tim Meusel

And when I run it a second time it passes: https://gist.github.com/bastelfreak/ae524a0064c9ad8e84570e28855ea3bb

@ragingra I'm wondering if this is actually related to the changed environment and not the node_manager version. My customers don't have a production environment and they only deploy one environment,...

I want to point out that I'm able to reproduce this, as described in https://github.com/puppetlabs/puppetlabs-peadm/issues/469#issuecomment-2265685971, but with the v3.21.0 release of PEADM. This issue isn't related to my feature branch...

I tried it again today with a fresh VM and I'm able to reproduce the problem, even with `puppet code deploy peadm --wait`. Modulelist: ``` root@pe /opt/peadmmig # puppet module...

I tried this on a new VM and added the environment to puppet.conf, but that also produces the same error. full output: https://gist.github.com/bastelfreak/25fe80e420537d8b60420914ef6d2161 Afterwards I run `bolt plan run peadm::convert...

I was away for an hour, run bolt again, and this time it just worked. I guess this is a weird timing issue, but I'm not sure yet what would...

ohhhh I maybe found the problem: ## Flow * the control-repo has no production branch or the production branch isn't deployed * A deployment of any other environment triggers r10k/code-manager...

@GSPatton hi, do you have any info when https://github.com/puppetlabs/puppetlabs-peadm/tree/support-custom-environment could be merged & released?

I raised support ticket 01286077 to get a release.

Hi, This issue was raised in July last year. It's blocking upgrades of PEADM for a major customer. Perforce failed to provide a fix in a reasonable time, so we...