---
tags:
  - puppet
---
Updated the ref in Puppetfile to yoga-eol instead of unmaintained/yoga.

Stap 1: `librarian-puppet install --verbose`.
Stap 2: `librarian-puppet update openstack-neutron --verbose`.

Check puppet-neutron `metadata.json` This is where dependency information lives. According to the gitlab readme it is also possible that this lives in `Modulefile` or `Puppetfile`.

Verbose info gives:
```
[Librarian] Failed to resolve puppetlabs-stdlib (>= 4.18.0, < 7.0.0) <(no source specified)> (from <nil>)
```

Erik determined this is due to `puppet-yum` by inspecting the lock file and checking who sets those requirements.
```
puppet master*​ ≡
❯ rg '>= 4.18.0, < 7.0.0' Puppetfile.lock
68:      puppetlabs-stdlib (>= 4.18.0, < 7.0.0)
```
```
    1    │ puppet-yum (4.3.0)
    1    │ │ puppetlabs-concat (>= 1.2.5, < 7.0.0)
   68    │ │ puppetlabs-stdlib (>= 4.18.0, < 7.0.0)
```

It turns out that this version of `puppet-yum` came from `elastic-elastic_stack` which came in turn from `elastic-logstash`.
We found that `elastic-logstash` has been deprecated, so we cannot upgrade this dependency. It is replaced by `puppet-logstash`.

```
puppet master ≡5s
❯ rg puppet-yum Puppetfile.lock
8:      puppet-yum (>= 0.9.6, < 5.0.0)
66:    puppet-yum (4.3.0)

hx Puppetfile.lock
    elastic-elastic_stack (6.3.2)
      puppet-yum (>= 0.9.6, < 5.0.0)

```

Changing the dependency from `elastic-logstash` to `puppet-logstash`, also brings issue.

At the end our hacky resolution is to update the commit hash in `Puppetfile.lock` and push that. Possible only because we didn't change any dependencies in `openstack-neutron`.