Skip to content
This repository has been archived by the owner. It is now read-only.

Cannot Create NodeJS Cartridges :: SCL Error #5629

Closed
kevinconaway opened this Issue Jul 18, 2014 · 10 comments

Comments

Projects
None yet
2 participants
@kevinconaway
Copy link
Contributor

kevinconaway commented Jul 18, 2014

When creating a new NodeJS app, I receive the following error from the server:

Unable to open /etc/scl/prefixes/v8314!

Tracked this down to:

https://github.com/openshift/origin-server/blob/master/cartridges/openshift-origin-cartridge-nodejs/lib/nodejs_context#L9

I'm not completely familiar with how scl works but from reading the man page and the error, it looks like the line should be:

/usr/bin/scl enable nodejs010 "$1" ;;

instead of

/usr/bin/scl enable v8314 nodejs010 "$1" ;;

I updated the set-configuration call below in a similar fashion. Making those changes allowed me to successfully create a nodejs app.

@Miciah

This comment has been minimized.

Copy link
Contributor

Miciah commented Jul 18, 2014

This looks related to https://bugzilla.redhat.com/show_bug.cgi?id=1104922, which added v8314 to that scl enable command because NodeJS requires V8 from the v8314 collection.

Do you have the v8314-runtime package installed? If not, does installing it resolve the problem you are seeing?

We may need to fix some package dependencies to avoid this problem.

@kevinconaway

This comment has been minimized.

Copy link
Contributor Author

kevinconaway commented Jul 18, 2014

I'm pretty green WRT OpenShift. How would I check if I have the package installed? I searched for that descriptor with yum but didn't see anything.

@Miciah

This comment has been minimized.

Copy link
Contributor

Miciah commented Jul 18, 2014

Check with rpm -q v8314-runtime. It will either return the package name with the version number of the installed package, or it will tell you "package v8314-runtime is not installed."

If the scl enable nodejs010 command is working for you, then presumably you were able to install the nodejs010 collection, which means you should be able to install the v8314 collection as well, using yum install v8314-runtime.

@kevinconaway

This comment has been minimized.

Copy link
Contributor Author

kevinconaway commented Jul 18, 2014

Looks like its not installed:

[root@broker tmp]# rpm -q v8314-runtime
package v8314-runtime is not installed

I tried installing it with yum but its not in any of the configured repos

[root@broker tmp]# yum install v8314-runtime
Loaded plugins: fastestmirror, priorities, versionlock
Repository 'jenkins-repo' is missing name in configuration, using id
Repository 'openshift-deps' is missing name in configuration, using id
Repository 'openshift-origin' is missing name in configuration, using id
Loading mirror speeds from cached hostfile

  • base: ftpmirror.your.org
  • epel: mirror.symnds.com
  • extras: mirrors.advancedhosters.com
  • updates: mirror.symnds.com
    296 packages excluded due to repository priority protections
    Setting up Install Process
    No package v8314-runtime available
@Miciah

This comment has been minimized.

Copy link
Contributor

Miciah commented Jul 18, 2014

How did you get the nodejs010 collection? yum -C list nodejs010-runtime will tell you which channel or repository it came from. I would expect the same channel or repository to have the v8314 collection as well.

@kevinconaway

This comment has been minimized.

Copy link
Contributor Author

kevinconaway commented Jul 18, 2014

Looks like openshift-deps

nodejs010-runtime.x86_64 1-17.el6 @openshift-deps

This is the stock image from https://mirror.openshift.com/pub/origin-server/release/4/images/openshift-origin.tgz

@Miciah

This comment has been minimized.

Copy link
Contributor

Miciah commented Jul 18, 2014

The archive probably needs to be updated to include the v8314 collection. For now, you could try installing the collection from https://www.softwarecollections.org/en/scls/rhscl/v8314/, but I can't be sure there won't be version conflicts.

@kevinconaway

This comment has been minimized.

Copy link
Contributor Author

kevinconaway commented Jul 18, 2014

Sounds good. How can I help get that archive updated?

@Miciah

This comment has been minimized.

Copy link
Contributor

Miciah commented Jul 18, 2014

I'm not sure who is responsible for making that archive. Try sending a message to the openshift-dev mailing list. I doubt the archive will get updated before Monday though.

@kevinconaway

This comment has been minimized.

Copy link
Contributor Author

kevinconaway commented Aug 1, 2014

This has been fixed in the latest rev

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.