Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Last step of the lab has a dependency cycle issue. #142

Open
gzepeda opened this issue May 14, 2018 · 6 comments
Open

Last step of the lab has a dependency cycle issue. #142

gzepeda opened this issue May 14, 2018 · 6 comments

Comments

@gzepeda
Copy link
Contributor

gzepeda commented May 14, 2018

The last step of the lab gives me the following error.

this is after trying to run the agent after configuring all the init.pp file.

Error: Failed to apply catalog: Found 1 dependency cycle: (Augeas[server-/var/lib/tomcat7-Catalina-connector-9080] => Tomcat::Config::Server::Connector[tomcat7-http] => Tomcat::Service[default] => Service[tomcat7] => Tomcat::Service[default] => Tomcat::Config::Properties[/opt/apache-tomcat catalina.properties] => Concat[/opt/apache-tomcat/conf/catalina.properties] => Concat_file[/opt/apache-tomcat/conf/catalina.properties] => Concat[/opt/apache-tomcat/conf/catalina.properties] => Tomcat::Config::Properties[/opt/apache-tomcat catalina.properties] => Tomcat::Instance[default] => Tomcat::Config::Server::Connector[tomcat7-http] => Augeas[server-/var/lib/tomcat7-Catalina-connector-9080]) Cycle graph written to /opt/puppetlabs/puppet/cache/state/graphs/cycles.dot.

I used the following version of the lab:
https://microsoft.github.io/PartsUnlimitedMRP/iac/200.2x-IaC-DeployappwithPuppetonAzure.html

@gzepeda
Copy link
Contributor Author

gzepeda commented Jun 9, 2018

Hello @eamonnk I reran the steps on the puppet lab and this issue is still there. I did use the steps on https://microsoft.github.io/PartsUnlimitedMRP/iac/200.2x-IaC-DeployappwithPuppetonAzure.html . I was planning to demo this on the Global DevOps Bootcamp next week.

Are there any plans to fix this? I would like to help but I am not sure where to start with this one. Let me know.

@eamkel
Copy link
Contributor

eamkel commented Jun 10, 2018

Hi,

yeah, have a partial fix for this, i.e. changed the Tomcat installation from downloaded package to install from source in the init.pp file under the configuretomcat class, and that works fine. The is an update to this file https://github.com/Microsoft/PartsUnlimitedMRP/blob/master/Labfiles/DevOps200.2x-InfrastructureasCode/Puppet/final/init.pp

Ran into a follow on issue then starting the tomcat service. Have just been a bit delayed closing it out. I'll be looking at it again later today and should be able to get this back up an running by tomorrow, sorry again for the delay getting back on it, have had a few other distractions. Will touch base later today on it.

Thanks for the follow up!
Eamonn

@eamkel
Copy link
Contributor

eamkel commented Jun 11, 2018

Hi Again,

Have updated the init.pp to install Tomcat from a url source and modified the initial config. The updated file is here https://github.com/Microsoft/PartsUnlimitedMRP/blob/master/Labfiles/DevOps200.2x-InfrastructureasCode/Puppet/final/init.pp and the lab steps points to this for studetns to use, the lab steps on the github.io page have also been updated to go through the modified pp config.

There is still one issue wiht the lab however, the tomcat service is not starting correctly. I'm still working through that, so the pp file will run fine and install and configure Tomcat without error, but when you go to view the MRP app page, it won't be available, due to the service not starting correctly. I'm continuing to look at that today and should have a resolution over today/tomorrow. Will post back here to keep you updated.

Talk Shortly, Thanks Again,
Eamonn

@gzepeda
Copy link
Contributor Author

gzepeda commented Jun 11, 2018

Let me try it out and will let you know my results.

@gzepeda
Copy link
Contributor Author

gzepeda commented Jun 11, 2018

I ran again the puppet test command after modifying the init.pp file and it finished running, but in the process I noticed this came up on the log displayed with a red color (I am using Putty). After it, the symptoms are the same as yours, tomcat service does not run at the end.

Another thing I noticed is that after running the steps, I see a mongodb service on the mrp node but I don't see the tomcat service on the list of services of the node.

Error: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install openjdk-7-jre' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
Package openjdk-7-jre is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'openjdk-7-jre' has no installation candidate
Error: /Stage[main]/Orderingservice/Package[openjdk-7-jre]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install openjdk-7-jre' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
Package openjdk-7-jre is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'openjdk-7-jre' has no installation candidate

@eamkel
Copy link
Contributor

eamkel commented Jun 18, 2018

Hi Again,

This lab issue has been fixed and the lab is functional now, the init.pp file has been updated along with the lab steps on the github.io page. The deployment issue was caused by some user and permissions issue on the webapps, folder and .war file, and then ensuring services were starting. The permissions were broadened out to 777 to allow it run, and users added.

There is still an error that’s received about the openjdk-7-jre' install during the mongodb installation, this is a reference in the mongodb package but doesn’t affect the lab outcome, worst case if you re-run the config it runs through fine, its just potentially encountered on the first run. We will clean this up, but it’s not affecting the lab outcome once re-run and have added a note at the end of the lab steps to call it out if encountered for now.

Anyway,the lab should be working now and the mrp app deploying fine, but if you have any problems with it just let us know.

Thanks Again!
Eamonn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants