Not possible to use port 88 for ubuntu repository

Bug #1479182 reported by Oleksii Aleksieiev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Undecided
Fuel Python (Deprecated)
6.1.x
Invalid
Undecided
Fuel Python (Deprecated)
7.0.x
Invalid
Undecided
Fuel Python (Deprecated)

Bug Description

when using Fuel 6.1 iso and truing to deploy ubuntu with custom repo that points to IP with port 88 you get error that indicate that network check is trying to connect to port 80(instead of 88).
Other ports are working fine - tired 80 and 8080.

Error message in fuel web
Connection to following repositories could not be established: http://10.21.238.198/mirrors/mirror.fuel-infra.org/mos/ubuntu/, http://10.21.238.198/mirrors/mos/mos-6.1-dev/, http://10.21.238.198/mirrors/percona/

Part of astude log
2015-07-28 16:54:50 WARNING
[7fa6acad2740] (manager) Checking connectivity to repositories failed: Connection to following repositories could not be established: http://10.21.238.198/mirrors/mirror.fuel-infra.org/mos/ubuntu/, http://10.21.238.198/mos/mos-6.1-dev/, http://10.21.238.198/mirrors/percona/
--

In fuel-web the problem repo were added with port 88.

e.g http://10.21.238.198:88/mos/mos-6.1-dev/

description: updated
Revision history for this message
Aleksandr Didenko (adidenko) wrote :

I was not able to reproduce it on 7.0:

/var/log/docker-logs/nailgun/app.log
2015-07-29 14:25:02.662 WARNING [7f3a46608740] (manager) Checking connectivity to repositories failed: HTTPConnectionPool(host='10.119.1.22', port=88): Max retries exceeded with url: /2015.1.0-7.0/ubuntu/x86_64 (Caused by <class 'socket.error'>: [Errno 110] Connection timed out)

So I'm marking it as invalid for 7.0 and forwarding 6.1-updates to python team.

Revision history for this message
Ihor Kalnytskyi (ikalnytskyi) wrote :

@Oleksii, could you please provide a diagnostic snapshot? Mark it as Incomplete until then.

Revision history for this message
Oleksii Aleksieiev (alexzzman) wrote :

unfortunately the environment and repo no longer exist.

Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

Please attach diagnostic snapshot and reopen issue if you reproduce the issue

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.