Re: [Rdo-list] [CI] any port changes in kilo?
----- Original Message -----
----- Original Message -----
> Greetings,
> I see that the latest kilo bugs were fixed w/ the latest delorean
> builds, but I did hit an error.
>
>
> 14:55:37 TASK: [packstack/runner | Wait for openstack port 35357 to
> open] **************
> 14:55:37 [[ previous task time: 0:00:00.025562 =
> 0.03s / 3622.74s ]]
> 14:55:37 <127.0.0.1> REMOTE_MODULE wait_for host=66.187.224.52
> port=35357 delay=10 timeout=120
> 14:55:37 failed: [rdo-pksk-4mdt2-rhos-ci-21-controller -> 127.0.0.1] =>
> {"elapsed": 124, "failed": true}
> 14:55:37 msg: Timeout when waiting for 66.187.224.52:35357
> 14:55:37
> 14:55:37 msg:
> 14:55:37 Timeout when waiting for 66.187.224.52:35357
>
>
> Are there any changes to the ports that the controller is exposing?
>
Hi Wes,
I'm not aware of any port changes, maybe there is a change in the security
group that made port 35357 unavailable?
Hi Wes,
After some more thinking about it, I'm quite sure it's a firewall issue. The
tester machine is trying to access the controller's floating IP, so it is either the
external firewall denying access to port 35357, or the security group not including port
35357.
Regards,
Javier
Regards,
Javier
> _______________________________________________
> Rdo-list mailing list
> Rdo-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe(a)redhat.com
>
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com