Role Broken, possible external package removed

[ryanlelek]

Error:

TASK [nodesource.node : Install Node.js] ***************************************
fatal: [MYDOMAIN.COM]: FAILED! => {"cache_update_time": 1455109514, "cache_updated": true, "changed": false, "failed": true, "msg": "'/usr/bin/apt-get -y -o "Dpkg::Options::=--force-confdef" -o "Dpkg::Options::=--force-confold" install 'nodejs=4.2_'' failed: E: Version '4.2_' for 'nodejs' was not found\n", "stderr": "E: Version '4.2*' for 'nodejs' was not found\n", "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\n", "stdout_lines": ["Reading package lists...", "Building dependency tree...", "Reading state information..."]}

[vjpr]

+1 Same issue here.

[ryanlelek]

@vjpr, wanted to make sure you saw the submitted PR. Update defaults/main.yml to have 4.3 as the node version instead of 4.2 and you'll be back up and running

If you're on Mac, ansible roles are stored in /usr/local/etc/ansible/roles

[vjpr]

@ryanlelek Thanks! I used your fix already :)

[gillesdemey]

Thanks @ryanlelek, patched this on my machine for now!

[vjpr]

@wolfeidau But what if you want to use version 4.2? The nodejs_version seems broken, or should be documented better.

[wolfeidau]

@vjpr I am hoping that @rvagg can shed some light on the removal of 4.2 from the repository.

I am not sure if it has been archived.

[chrislea]

The issue is that when the 4.3 release was pushed out to the repo, it unregistered any earlier releases in the 4.x line. So if you do the standard apt-get update and then apt-cache search nodejs now, you'll just see the 4.3 entry.

The earlier versions are there, you'd just have to link directly to the URL IE:

https://deb.nodesource.com/node_4.x/pool/main/n/nodejs/nodejs_4.2.6-1nodesource1~trusty1_amd64.deb

assuming you are using Ubuntu Trusty.

[vjpr]

Thanks @chrislea.

So this role should probably be updated to support linking directly to exact versions. I prefer to lock down exact Node.js versions, and upgrade all at once.

And the fix of changing nodejs_version to 4.3 will break when 4.4 is out...so lets keep this issue open @wolfeidau?

EDIT

Seems there's some discussion about this in #5 already, so thats fine.

[wolfeidau]

Yeah I am guessing I will have to add some sort of escape hatch to work around this.

@chrislea is there a reason it is setup this way?

Cheers

[chrislea]

The reason it works this way is that the reprepro command which manages the repo files for all of this and updates them when you add / remove packages doesn't support multiple versions. It will just use whatever the newest one is. Launchpad PPA repos work the same way.

We're looking at changing our tooling so that the repo will show multiple versions, but that's fairly low on the priority list right now internally if I'm being honest.

All that said, one of the major points of the 4.x release line is that being an LTS release, it's never going to break API compatibility when a new version comes out. So you should be totally safe updating to whatever the newest version is at any time without fear of it causing problems. Pinning to a specific version isn't necessary. And frankly, it could be a Bad Thing (tm) if you pinned a version like that. This most recent 4.3 release is a security release that you should definitely want to update to.

[makmanalp]

Welp, looks like we hit it for 4.4:

E: Version '4.3*' for 'nodejs' was not found

[makmanalp]

Looks like the repo is updated so all I needed to do was to remove / reinstall the role. For some reason ansible-galaxy remove didn't work. Workaround was reinstalling with:

sudo -H ansible-galaxy install --force nodesource.node,master