hewlettpackard / csa-ce Goto Github PK

Try to use csa-ce docker environment in MS Azure with the following VM instance:

• Ubuntu 14.04_5LTS
• 8core/26GBmem
• hostname: csatest01
• external IP address: 13.78.126.50
• internal IP: 10.1.0.4
  I setup the environment with the followting command:

# curl -k -L https://github.com/HewlettPackard/csa-ce/raw/master/buildEnv-dockercompose.sh | bash /dev/stdin csatest01 13.78.126.50

When trying to access to CSA, I've accessed to https://13.78.126.50:18444/csa, but redirecting to 10.1.0.4(internal IP) caused error. (I cannot access to 10.1.0.4 because it is internal IP)

Can I use this environment with such NATed network?
Thanks.

Hello,

After deployment, I have no service design available and I can not install any CSA Capsules.

Here is the message

Container Deployment is fine

Changing the  hostname and ipaddress in the yml file
Starting to download all the required images and the containers will be created in the backgroud. This may take sevaral minutes.
Creating network "root_default" with the default driver
Pulling commondb (hpsoftware/useitwithcsacodar:csadb)...
csadb: Pulling from hpsoftware/useitwithcsacodar
6599cadaf950: Pull complete
23eda618d451: Pull complete
f0be3084efe9: Pull complete
52de432f084b: Pull complete
a3ed95caeb02: Pull complete
00d152cb8f7b: Pull complete
b4dbd912e408: Pull complete
511049ccfe7c: Pull complete
Digest: sha256:c8a2a2f807ee55ad351fc3f14ba400c3654bed7a7fee14eaf05e7ee24be3ec93
Status: Downloaded newer image for hpsoftware/useitwithcsacodar:csadb
Pulling ooce (hpsoftware/useitwithcsacodar:ooce1062)...
ooce1062: Pulling from hpsoftware/useitwithcsacodar
15e658a6de17: Pull complete
9ac1fd7cda69: Pull complete
8715d22f5cc2: Pull complete
d0e42a189c3b: Pull complete
41b7042b5523: Pull complete
04bc3986291f: Pull complete
Digest: sha256:aaddadc10ce89a054f1a936f7880368ddc90c05c825756480d18e1b7c764d957
Status: Downloaded newer image for hpsoftware/useitwithcsacodar:ooce1062
Pulling csa (hpsoftware/csa:latest)...
latest: Pulling from hpsoftware/csa
6599cadaf950: Already exists
23eda618d451: Already exists
f0be3084efe9: Already exists
52de432f084b: Already exists
a3ed95caeb02: Already exists
2fc67fff80bc: Pull complete
5cac9b540600: Pull complete
Digest: sha256:cb9f37768f040f9fefb1b07df2dc5bebd81ea88ef6c2e3fb5c17adc0a437fab5
Status: Downloaded newer image for hpsoftware/csa:latest
Creating commondb
Creating ooce
Creating csa
Please note the below URLs for your reference
CSA Management Console - https://16.77.9.164:18444/csa
MPP - https://16.77.9.164:18089/mpp
Operations Orchestration Central - https://16.77.9.164:18445/oo

Any idea ?
Thank you

When stopping CSA then "restarting" it, CSA MPP is never up again.

Current workaround:
Log into csa container and enter service mpp restart.
Would be nice if this workaround won't be necessary

Although user look up test works fine, I keep getting this error:
https://130.175.94.61:18089/error/unauthorized

Access Denied. There was a problem authorizing you.

The exact same setting works on my full CSA setup in another environment but not in this CSA container environment.

tail -f csa-msvc.log hpcloud-idm-service.log csa.log &
==> csa-msvc.log <==
29 Jun 2017 02:38:03,993 [default task-59] ERROR [] IdmRequestTokenProviderImpl : Error requesting Idm: 503 (Service Unavailable) https://130.175.94.61:18444/idm-service/v2.0/tokens/<token>
29 Jun 2017 02:38:48,439 [default task-70] ERROR [] IdmRequestTokenProviderImpl : Error requesting Idm: 503 (Service Unavailable) https://130.175.94.61:18444/idm-service/v2.0/tokens/<token>

==> hpcloud-idm-service.log <==
2017-06-29 02:38:50,318 [default task-73] ERROR com.hp.ccue.identity.hpsso.HpSsoValidator  - HP SSO authentication failed: [VALIDATION_USER_NOT_AUTHENTICATED: Validation: no SSO cookie on request (not authenticated) - more info: User must login]: initContextFromRequest - no SSO cookie on request (not authenticated).RequestURL is [https://130.175.94.61:18444/idm-service/idm/v0/login]; method [GET]; sessionId [7guW0oBJxvVKc9Zv44lHHqdm]; RequestQuery is [NOT EMPTY];
2017-06-29 02:38:50,320 [default task-73] ERROR com.hp.ccue.identity.filter.hpsso.HpSsoFilter  - HP SSO authentication failed: [VALIDATION_USER_NOT_AUTHENTICATED: Validation: no SSO cookie on request (not authenticated) - more info: User must login]: initContextFromRequest - no SSO cookie on request (not authenticated).RequestURL is [https://130.175.94.61:18444/idm-service/idm/v0/login]; method [GET]; sessionId [7guW0oBJxvVKc9Zv44lHHqdm]; RequestQuery is [NOT EMPTY];

==> csa.log <==
29 Jun 2017 02:39:08,232 [default task-112] ERROR [] IdmRequestTokenProviderImpl : Error requesting Idm: 503 (Service Unavailable) https://130.175.94.61:18444/idm-service/v2.0/tokens/<token>

I also realized, there is no idm service.

root@70b827cb6bf7:/usr/local/hpe/csa/jboss-as/standalone/log# service idm status
idm: unrecognized service

I get the following error and it quits on CentOS 7.3. I have tried some basic debugging and nothing seems to work.

Status: Downloaded newer image for hpsoftware/csa:latest
Creating ooce ...
Creating commondb ...
Creating ooce
Creating ooce ... error

ERROR: for ooce Cannot create container for service ooce: b'mkdir /var/lib/docker/overlay2/447574358d1190233546c5f4c61a7c3dc70a02ba526c887c428Creating commondb ... error

ERROR: for commondb Cannot create container for service commondb: b'mkdir /var/lib/docker/overlay2/2dd2e3b9612ee77dd9c03040d441a16ddf5f7edadeb9766086a9ec87dd0b595e-init/merged/dev/shm: invalid argument'

ERROR: for ooce Cannot create container for service ooce: b'mkdir /var/lib/docker/overlay2/447574358d1190233546c5f4c61a7c3dc70a02ba526c887c428ee36335902215-init/merged/dev/shm: invalid argument'

ERROR: for commondb Cannot create container for service commondb: b'mkdir /var/lib/docker/overlay2/2dd2e3b9612ee77dd9c03040d441a16ddf5f7edadeb9766086a9ec87dd0b595e-init/merged/dev/shm: invalid argument'
Encountered errors while bringing up the project.
Please note the below URLs for your reference
CSA Management Console - https://192.168.1.46:18444/csa
MPP - https://192.168.1.46:18089/mpp

Any help ? The overlay fs is enabled for the docker container.

While, yes, the OS requirements do say "Ubuntu" is the OS requirement ... :) ... this can work on OS X under "Docker for Mac". Simple change to buildEnv-dockercompose.sh needed. Change this:

sed -i -e "s/vmhostname/${hostname}/" -e "s/vmipaddress/${ipaddress}/" -e "s/proxyhost/${proxyhost}/" -e "s/proxyport/${proxyport}/" docker-compose.yml

to this:

sed -i "" -e "s/vmhostname/${hostname}/" -e "s/vmipaddress/${ipaddress}/" -e "s/proxyhost/${proxyhost}/" -e "s/proxyport/${proxyport}/" docker-compose.yml

Notice the double quotes after the -i switch. There is a minor difference between the Linux sed and the BSD sed commands. OS X is BSD based so the -i switch requires an argument even if it's empty.

Try to register the CSA-CE 4.7, but when I run the first login in page:

https://<my_ip_address>:18444/csa/community-activation/index.jsp#/communityactivation/productregistration

I get
"Error while product registration"

No dns issue, no connection issue.

OO and MP work.

Hello,

I have noticed that the password for idmTransportUser has been changed from its default value to a new value.
This should be documented somewhere (as it is mandatory to use this password to access the CSA APIs). Otherwise when we try to get a token; there is a a simple 401 error message without further explanation (bad credentials) and that could lead to a lot of research (acutally I though that the incorrect credentials were the payload send in the request to the idm-service).

Olivier

CSA shouldnt need the IP address of the container for the installation... If we specify a Hostname that should be enough.

Deploying this docker container as is described, makes a configuration in which the mpp login always redirect to provied IP Address... which in many dev setups would not be a static IP.

Hi,
While binding an organization to LDAP (AD2012), when User Search Base is defined, the lookup user function will fail [Error retrieving user information from LDAP]. When User Search Base is empty, lookup user works. Please see screen shots below for further details.
Regards, PO3.

Registration Failed. Tried different email addresses but no luck. Any other way to bypass.?