Red Hat Bugzilla – Bug 848616
3.1 - vdsm-reg needs to change default port to 443
Last modified: 2013-01-08 23:15:42 EST
+++ This bug was initially created as a clone of Bug #832227 +++
Description of problem:
On engine-setup, the default ports are 80 and 433.
On ovirt-node, the default port is 8443.
<Cybertimber2009> So engine-setup defaults to 80/443 instead of 8080/8433 now?
<@mburns> Cybertimber2009: yes
<Cybertimber2009> So... Node needs to be changed from default to connect yea?
* Cybertimber2009 thinks it's obvious... but wonders if they should match
* Cybertimber2009 OOB
<@mburns> Cybertimber2009: yes, but it's actually vdsm
<@mburns> they set that screen up
<@mburns> dougsland: ^^
<@mburns> vdsm-reg needs to change default port for engine to 443
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install ovirt-engine package
2. Run "engine-setup"
3. Note default port
4. Install oVirt Node 2.4.0-1.0.fc17
5. Access "oVirt Engine" tab on TUI
6. Note default Management Server Port
Node default is 8443, engine-setup is 80/443
Node and engine match out of the box
--- Additional comment from firstname.lastname@example.org on 2012-06-14 19:19:27 EDT ---
Thanks for your report, the patch is available here:
--- Additional comment from email@example.com on 2012-07-12 23:50:37 EDT ---
*** Bug 839821 has been marked as a duplicate of this bug. ***
--- Additional comment from firstname.lastname@example.org on 2012-07-18 10:08:05 EDT ---
IMO, this should be a blocker for 3.1 GA. When running through engine setup, if you choose to let the installer configure the firewall, port 8443 and 8080 are not open. The current version of the patch solves this by having 443 as the default, but will also try fallbacks to 8080/8443.
Given that this is targeted primarily for 3.1, we should default to 443 and fall back to 8443 if it fails.
Current functionality is that it defaults to something which will fail with 3.1 with default firewall.
*** Bug 854908 has been marked as a duplicate of this bug. ***
*** Bug 854246 has been marked as a duplicate of this bug. ***
*** Bug 804298 has been marked as a duplicate of this bug. ***
ok - vdsm4.9.6-34
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.