Issue with Cypress V4 Chef Install (Cypress + CVU)

[oqureshi2012]

Good Morning,

I am running into an issue trying to setup the CVU for my install. I followed all of the chef installation instructions on this page: https://github.com/projectcypress/cypress-recipe#installation-options.

After installing both Cypress and CVU I am able to get into the GUI but the validation utility is not working. Using this page: https://github.com/projectcypress/cypress/wiki/Cypress-Validation-Utility-Initial-Setup I was able to run the first command (cd /opt/cypress-validation-utility) but when I tried the second command (/opt/ruby_build/builds/opt/cypress-validation-utility/bin/bundle exec rake bundle:download_and_install version=BUNDLE_VERSION RAILS_ENV=production) it told me that the file/directory does not exist. Please advise on how I can resolve this. Did I miss part of the configuration? I do not see Ruby_Build as a file in that directory.

Thanks

[jxfish2]

Note that /opt/ruby_build does not exist. We are running in the Azure cloud, and Azure is not compatible with your image type. As such, you told us to build our Ubuntu server with docker already installed. Then, you told us to use the "chef" instructions to finish the Cypress and CVI installs. Up to this one last piece, there have been no issues or errors. However, the /opt/ruby_build directory structure does not exist, using this method. At what point is the /opt/ruby_build installed? Is there something we need to do, to install this /opt/ruby_build application?

[geddawi]

Same dilemma in trying to get CVU up and running alongside Cypress, already opened an issue ticket about this. After the Chef installation, redirecting to CVU gives a 502 NGINX error and there is no way offered to either get CVU to share the imported bundle from Cypress or get CVU running by importing our own bundle. Please clarify this guys, it's a huge hassle.

[geddawi]

I tried manually downloading the bundle-2018.zip on the machine and performing abundle exec rake bundle:import[.....]with the respective parameters for that rake call and path to the bundle, but it seems like we can't bundle anything at all in the folder.

[rbclark]

It seems the instructions in the Chef README never got updated for Cypress v4. I apologize for that, I've gone ahead and updated them to point to the proper links for Cypress v4. If you have Cypress + CVU installed then any bundles that you install to Cypress via the UI will automatically be seen by the CVU. If you have only installed CVU and need to import a bundle via the command line then you can run cypress-validation-utility run rake bundle:import[...].

Any instructions mentioning /opt/ruby_build are for Cypress v3, the ruby version is now packaged within /opt/cypress/bin.

[oqureshi2012]

Good Morning Robert,

I have uploaded the 2018 bundle via the UI, but I am still getting the 502 error when I click on the Validation Utility. We have already confirmed everything from a infrastructure standpoint so I believe this is still an application issue. Please see the below images for reference and advise on next steps.

Thanks

[oqureshi2012]

Another thing I noticed is that we are using Cypress v4.0.1 and the bundle version is 2018.1.0, could there be any compatibility issues?

Thanks

[rbclark]

It turns out there was an issue with our build process for CVU v4. We have rebuilt the CVU v4 package, could you try installing it by running

curl https://raw.githubusercontent.com/projectcypress/cypress/v4.0.1.1/contrib/upgrade_cypress_40.sh | sudo bash

and report back whether this works?

[oqureshi2012]

Robert,

I went ahead and ran the update and it did not fix the validation utility. I am still receiving the 502 error message. Please see the image below: it says that the packages cannot be authenticated?

[oqureshi2012]

Update: we added the --anyauth option to the curl command and were able to get past that error message. Now we get more errors while running the update. See below:

[rbclark]

Are you behind a corporate proxy or anything else that could be messing with your traffic by any chance? You definitely shouldn't be getting a segmentation fault from the OS just for trying to update a package. Can you also see if installation of other packages is working correctly by trying to install something like python2-pip or something else you don't already have installed?

[jxfish2]

We are including the crash files from each of the different segmentation faults that occurred.

_optjs-ecqm-engine.heroku_node_bin_node.116.crash.txt

_usr_bin_wget.0.crash.txt

_usr_lib_apt_methods_https.0.crash.txt

[geddawi]

@oqureshi2012 I had your same issue and @rbclark 's fix did it for me. Try destroying your current VM/machine OS instance and run the chef install on a clean Ubuntu VM/machine. Then run @rbclark 's shell script command and if/when it hangs hit enter once; it will be waiting for your password for the second part of the command (the execution part after the pipe '|' symbol), enter your password and it should work.

It turns out there was an issue with our build process for CVU v4. We have rebuilt the CVU v4 package, could you try installing it by running

curl https://raw.githubusercontent.com/projectcypress/cypress/v4.0.1.1/contrib/upgrade_cypress_40.sh | sudo bash

and report back whether this works?

[rbclark]

@jxfish2 Your problem sounds related to something specific to your environment, we have been able to verify it is working on our end and it seems a few people in this thread have been able to successfully run it as well. The script itself is just pulling from apt. Can you verify that all your OS packages are fully up to date and that there is no MITM proxy or something else messing with your traffic?

@oqureshi2012 The updates that we pushed out should actually not require you to run the upgrade script if you do a clean build with Chef. A clean build with Chef should include all of the new changes we have made.

[okeefm]

@oqureshi2012 I'm going to close this issue as resolved. If you're continuing to experience issues with your install, please feel free to comment/re-open the issue.

Thank you, Michael O'Keefe