Bill,
That does indeed make sense.
I tried repeating this on a Linux OpenShift Origin setup and it works fine.
Thanks
Tim
On 25/07/2017 16:23, William DeCoste wrote:
Hi Tim,
In the past this has been caused by issues with the layered filesystem
being used by docker, we saw this when directories created in one
layer with permissions modified in another became read-only.
What version of Docker are you running? We are researching for
addition info on our side.
Thanks -Bill
On 7/25/17 7:51 AM, Tim Dudgeon wrote:
Hi Bill,
Thanks, that's a bit simpler than what I was doing, but I hit the
same problem.
This is what I am trying:
minishift delete
minishift start
oc login -u system:admin
oc policy add-role-to-user edit developer
oc create -f
dev/git/jboss-openshift/application-templates/jboss-image-streams.json
-n openshift
oc create -f
dev/git/jboss-openshift/application-templates/secrets/sso-app-secret.json
oc process -f
dev/git/jboss-openshift/application-templates/sso/sso71-https.json -p
HTTPS_NAME=jboss -p HTTPS_PASSWORD=mykeystorepass | oc create -f -
All goes OK, but Wildfly fails to start because of this:
14:39:24,591 ERROR [org.jboss.as.server] (Controller Boot Thread)
WFLYSRV0055: Caught exception during boot:
java.lang.IllegalStateException: WFLYCTL0056: Could not rename
/opt/eap/standalone/configuration/standalone_xml_history/current to
/opt/eap/standalone/configuration/standalone_xml_history/20170725-143924587
at
org.jboss.as.controller.persistence.ConfigurationFile.createHistoryDirectory(ConfigurationFile.java:638)
at
org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:470)
at
org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.successfulBoot(BackupXmlConfigurationPersister.java:94)
at
org.jboss.as.controller.AbstractControllerService.finishBoot(AbstractControllerService.java:451)
at org.jboss.as.server.ServerService.boot(ServerService.java:373)
at
org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:301)
at java.lang.Thread.run(Thread.java:748)
14:39:24,592 FATAL [org.jboss.as.server] (Controller Boot Thread)
WFLYSRV0056: Server boot has failed in an unrecoverable manner;
exiting. See previous messages for details.
Tim
On 25/07/2017 15:03, William DeCoste wrote:
Hi Tim,
These are the official templates:
https://github.com/jboss-openshift/application-templates
The secrets folder has sso-app-secret.json that will create the
service account and default keystore you'll need for SSO. The image
streams are in jboss-image-streams.json and should be added to the
"openshift" namespace/project.
If you can provide some additiona details on the issues you are
hitting, we'll be happy to help.
Thanks -Bill
On 7/25/17 1:43 AM, Tim Dudgeon wrote:
I've trying to get sso (keycloak) running, using minishift as an
initial example.
For instance, using this template:
https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_examples/files/examples/v1.5/xpaas-templates/sso70-https.json
There's some information [1,2] that relates to OpenShift
enterprise, but its not clear exactly what's needed in terms of
service accounts and secrets etc. and I keep hitting problems.
Is there any description of how to get this running on OpenShift
Origin or Minishift that can be used as a starting point?
Thanks
Tim
1.
https://access.redhat.com/documentation/en-us/red_hat_jboss_middleware_for_openshift/3/html-single/red_hat_jboss_sso_for_openshift/
2.
https://docs.openshift.com/enterprise/3.1/using_images/xpaas_images/sso.html#quickstart-example-using-the-sso-xpaas-image-with-the-sso-enabled-jboss-eap-xpaas-image
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
