Forgeops: Amster can’t install OpenAM

This topic contains 5 replies, has 2 voices, and was last updated by  bmccraw 1 month, 1 week ago.

  • Author
    Posts
  • #25033
     bmccraw 
    Participant

    I’m finally sitting down to play with forgeops and I can’t get it to work. I’ve got minikube up and running on my mac, I can deploy all the helm charts, but when the amster service attempts to execute the install-openam script, it fails with:

    am> :load /opt/amster/scripts/00_install.amster
    Failed to execute the 'install-openam' command: http://openam:80/openam/setup/setSetupProgress?mode=text

    To not clutter this thread, I put the debug output for my cluster at the link below:

    LINK

    I ran the minikube ssh sudo ip link set docker0 promisc on command found here: minikube workaround

    I can curl from the amster instance to the openam instance, so I don’t think it’s a network block. I’m out of ideas at this point. This is my first time interacting with Kubernetes as well, so the issue could be my minikube environment or my forgeops setup. Any help would be appreciated.

    • This topic was modified 1 month, 1 week ago by  bmccraw.
    • This topic was modified 1 month, 1 week ago by  bmccraw.
    #25036
     David Goldsmith 
    Participant

    Hi,

    For starters, could you post some information here, especially what we list in https://backstage.forgerock.com/docs/platform/6.5/devops-guide/#sec-feedback?

    The debug logs are the most important but it would also be helpful to know some of the versions you’re using, especially minikube in this case.

    Thanks,

    David

    #25037
     bmccraw 
    Participant

    Sure:

    This is how I started my minikube environment:
    minikube start --memory=8192 --disk-size=30g --vm-driver=vmwarefusion --bootstrapper kubeadm --kubernetes-version=v1.11.2 && minikube ssh sudo ip link set docker0 promisc on

    I’m on the master branch of forgeops.

    #25038
     David Goldsmith 
    Participant

    For starters, I’d suggest you use the release/6.5.0 branch of the forgeops repo. The master branch becomes unstable from time to time and I’m not sure whether it’s working right now or not.

    You didn’t say what version of minikube you’re on, but if it’s 0.34.1, you’ll need to specify cluster version 1.13.2. I’m about to push a doc update with that information in it BTW.

    If that doesn’t help, please provide the debug logs and more information about your environment as I requested above.

    Thanks,

    David

    #25039
     bmccraw 
    Participant

    Thanks David. I did just notice it says to not run on the master branch of forgeops. I’ll switch now and see if that helps.

    my minikube version is 0.31.0 so I think I’m ok with version compatibility.

    #25040
     bmccraw 
    Participant

    David,

    Switching to the release/6.5.0 branch of forgeops seems to have fixed the issue. I’m able to get the XUI to load now. Thank you for the simple suggestion.

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.

©2019 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?