RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 848616 - 3.1 - vdsm-reg needs to change default port to 443
Summary: 3.1 - vdsm-reg needs to change default port to 443
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Douglas Schilling Landgraf
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
: 804298 854246 854908 (view as bug list)
Depends On: 832227
Blocks: 822145
TreeView+ depends on / blocked
 
Reported: 2012-08-16 03:05 UTC by Douglas Schilling Landgraf
Modified: 2022-07-09 05:38 UTC (History)
22 users (show)

Fixed In Version: vdsm-4.9.6-31.0
Doc Type: Bug Fix
Doc Text:
Clone Of: 832227
Environment:
Last Closed: 2012-12-04 19:07:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1508 0 normal SHIPPED_LIVE Important: rhev-3.1.0 vdsm security, bug fix, and enhancement update 2012-12-04 23:48:05 UTC

Description Douglas Schilling Landgraf 2012-08-16 03:05:21 UTC 
+++ 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: ^^
<Cybertimber2009> ahh
<@mburns> vdsm-reg needs to change default port for engine to 443

Version-Release number of selected component (if applicable):
ovirt-engine 3.1.0_0001
ovirt-node 2.4.0-1.0.fc17


How reproducible:


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
  
Actual results:
Node default is 8443, engine-setup is 80/443

Expected results:
Node and engine match out of the box

Additional info:

--- Additional comment from dougsland on 2012-06-14 19:19:27 EDT ---

Hi Cybertimber2011,


   Thanks for your report, the patch is available here:
   http://gerrit.ovirt.org/#/c/5367/

--- Additional comment from dougsland on 2012-07-12 23:50:37 EDT ---

*** Bug 839821 has been marked as a duplicate of this bug. ***

--- Additional comment from mburns 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.
Comment 6 Douglas Schilling Landgraf 2012-09-06 15:51:00 UTC 
*** Bug 854908 has been marked as a duplicate of this bug. ***
Comment 7 Douglas Schilling Landgraf 2012-09-12 02:33:07 UTC 
*** Bug 854246 has been marked as a duplicate of this bug. ***
Comment 8 Douglas Schilling Landgraf 2012-09-27 16:10:08 UTC 
*** Bug 804298 has been marked as a duplicate of this bug. ***
Comment 9 Pavel Stehlik 2012-10-01 11:33:20 UTC 
ok - vdsm4.9.6-34
Comment 12 errata-xmlrpc 2012-12-04 19:07:28 UTC 
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.

http://rhn.redhat.com/errata/RHSA-2012-1508.html
Note You need to log in before you can comment on or make changes to this bug.