Adding 'iptables -F' to local environment run to avoid network issues with pods unable to communicate to routes. #43
Comments
|
When I see this behavior the root cause is generally that the Service Catalog failed to retrieve a list of Service Classes from the Ansible Service Broker. My issue is normally resolved by running "sudo iptables -F". When I hit this, it appears to be a firewall issue that is blocking some of the network traffic between services, i.e. the Service Catalog is unable to hit the route for the Ansible Service Broker. |
|
I will check , but the common_vars under local setup doesn't have any aws details. It might be due to that. Where do i set those to include AWS in my local instance catalog |
|
@arunneoz Note that for the local setup we are not creating the secret in aws_demo to launch the RDS, i.e. no secret is created with the AWS credentials needed to provision RDS from the webui. still....the local setup should populate the APBs in the servicecatalog which are the Amazon services along with ManageIQ and postgres-demo The flow is:
To debug this, I would check to see what ServiceClasses are available in the Service Catalog. Below is an example of what I would expect to see if things are working. Assuming you don't see serviceclasses....next thing is to check: Logs from ansible-service-broker below when things look good. 172.17.0.1 - - [09/May/2017:17:56:42 +0000] "POST /v2/bootstrap HTTP/1.1" 200 22 Next Service Catalog: $ oc project service-catalog .... I've run into issues with my environment that the service catalog couldn't talk to the route for the ansible service broker, in my cases I ran "sudo iptables -F" and redid "reset_environment.sh" from the local directory and it resolved my issues. I typically have to run "sudo iptables -F" after I reboot my linux laptop. |
|
@arunneoz as to getting the RDS provision example to run from the local environment through the WebUI, it requires this secret to be created in the project: The issue is that we didn't have a good way to programmaticly determine {{ my_security_group_id }} for the local case. For the ec2 case we look at the running instance and determine the security group id from that. I assume you could set {{ my_security_group_id }} then include the 'demo_prep' role in the local environment. |
|
When i looked into the Controller Manager. It says unable to get the catalog from the following url E0509 19:11:07.701059 1 open_service_broker_client.go:128] Failed to fetch catalog "ansible-service-broker" from http://asb-1338-ansible-service-broker.172.17.0.1.nip.io/v2/catalog: response: error: &url.Error{Op:"Get", URL:"http://asb-1338-ansible-service-broker.172.17.0.1.nip.io/v2/catalog", Err:(*net.OpError)(0xc42032a050)} When i hit the url from browser , iam able to see the response. Any thoughts, i did run sudo iptables -F and rebooted and ran reset_environment |
|
This is the exact error I see when I need to run "sudo iptables -F" My workflow would be:
Whenever I reboot, I need to re-run sudo iptables -F after the reboot. It's possible there could be another networking issues causing this to fail on local, conflicts with the docker network could be another culprint |
|
That did the trick, thanks i also configured aws secret myself and provisioned the instance. Thanks for all your help |
jwmatthews
changed the title
|
The resolution to this issue was running "sudo iptables -F" prior to running oc cluster up. I've hit this issue several times on my own runs, typically after I have restarted my linux machine (running Fedora 25). To avoid others hitting this problem we could add the iptables -F prior to running oc cluster up, or we could also experiment with modifying firewall rules such as recommended in this comment: |
Hello,
I was able to setup the local instance and everything cameup , but iam not seeing AWS in the catalog. How can i enable the service broker for AWS services.
Regards
Arun
The text was updated successfully, but these errors were encountered: