C3-prov error in training cluster today

#1

We were trying to re-deploy the lightbulb application in the training environment - the provisioning worked fine yesterday, but fails today with the error shown below. Do we need to get a new version of c3-prov for the training environment ? We’re just playing with training until we get a dev cluster for 3M.

[lightbulb/dev19] Created 152.57Kb ZIP of one package in 2.3s
module.js:471
throw err;
^
Error: Cannot find module 'superagent-proxy’
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object.result.adminServer (net.js:63:5)
at eval (provisioner.js:33:22)
at C:\Users\us336280\AppData\Local\c3\nodeapps\prov\node_modules\async\lib\async.js:607:21
at C:\Users\us336280\AppData\Local\c3\nodeapps\prov\node_modules\async\lib\async.js:246:17
at iterate (C:\Users\us336280\AppData\Local\c3\nodeapps\prov\node_modules\async\lib\async.js:146:13)
at C:\Users\us336280\AppData\Local\c3\nodeapps\prov\node_modules\async\lib\async.js:157:25

0 Likes

#2

Hey Raj,

We are currently upgrading the training environment to the 7.7 generally available release. As a result of this upgrade, the c3-prov tool that you have downloaded is not compatible with the environment. I recommend provisioning via the provisioner tool in the static/console. Remember to point the console provisioner tool to the training directory within the c3training repository.

Thank you,

0 Likes

#3

Bus
Thanks - that got us a bit further, but we’re getting errors that we don’t think are coming from our code (multiple of us are getting this error).

{fileUrl:"-type-CustomerRelation.c3typ",lineNum:-1,colNum:-1,severity:“ERROR”,message:“Unknown extension type Validation in type -type-CustomerRelation.CustomerRelation field fromRole”,code:“NOT_CLASSIFIED”}
{fileUrl:"-type-ValidatedTimeseriesDataPoint.c3typ",lineNum:-1,colNum:-1,severity:“ERROR”,message:“Unknown extension type Validation in type -type-ValidatedTimeseriesDataPoint.ValidatedTimeseriesDataPoint field start”,code:“NOT_CLASSIFIED”}
{fileUrl:"-type-ValidatedTimeseriesDataPoint.c3typ",lineNum:-1,colNum:-1,severity:“ERROR”,message:“Unknown extension type Validation in type -type-ValidatedTimeseriesDataPoint.ValidatedTimeseriesDataPoint field start”,code:“NOT_CLASSIFIED”}
{fileUrl:"-type-ValidatedTimeseriesDataPoint.c3typ",lineNum:-1,colNum:-1,severity:“ERROR”,message:“Unknown extension type Validation in type -type-ValidatedTimeseriesDataPoint.ValidatedTimeseriesDataPoint field start”,code:“NOT_CLASSIFIED”}
{fileUrl:"-type-ValidatedTimeseriesDataPoint.c3typ",lineNum:-1,colNum:-1,severity:“ERROR”,message:“Unknown extension type Validation in type -type-ValidatedTimeseriesDataPoint.ValidatedTimeseriesDataPoint field start”,code:“NOT_CLASSIFIED”}
{fileUrl:"-type-ValidatedTimeseriesDataPoint.c3typ",lineNum:-1,colNum:-1,severity:“ERROR”,message:“Unknown extension type Validation in type -type-ValidatedTimeseriesDataPoint.ValidatedTimeseriesDataPoint field start”,code:“NOT_CLASSIFIED”}
{fileUrl:"-type-OldGeoPoint.c3typ",lineNum:-1,colNum:-1,severity:“ERROR”,message:“Unknown extension type Validation in type -type-OldGeoPoint.OldGeoPoint field latitude”,code:“NOT_CLASSIFIED”}
{fileUrl:“meta://base/repository.json”,lineNum:0,colNum:0,severity:“WARNING”,message:“Wrong server version, current version is: ‘7.7.5’ but expected version matching: ‘7.6.1.13’”}

0 Likes

#4

Hey Raj,
I will stop by shortly to see what’s going on so you can continue using the environment.

0 Likes