Project

General

Profile

Actions

Bug #21216

closed

All rudder commands using the API don't detect the port of the webapp when we configure a virtualhost with a different port

Added by Nicolas CHARLES over 2 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Category:
Server components
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Medium
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No

Description

If the webapp/API listen on another port (because of ease of distinction of target for virtualhost) then the commands won't work, as they'll probably talk to 443
Detection of port is made with

get_https_port() {
  # get port from configuration
  PORT=$(agent_conf https_port)
  # if not trust the server on this
  if [ "${PORT}" = "" ] && [ -f "${RUDDER_JSON}" ]; then
    PORT=$(rudder_json_value 'HTTPS_POLICY_DISTRIBUTION_PORT')
  fi
  # else default to 443
  if [ "${PORT}" != "" ]; then
    PORT=":${PORT}" 
  fi
  echo "${PORT}" 
}

which is for the policy distribution, and not the webapp

There is nowhere yet where to store this value, so we'll probably need a new config parameter


Related issues 1 (0 open1 closed)

Related to Scale-out relay - Bug #22290: Script node to relay don't detect webapp port when we configure a virtualhost with a different portReleasedAlexis MoussetActions
Actions #1

Updated by Alexis Mousset over 2 years ago

  • Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Effort required set to Medium
  • Priority changed from 0 to 59
Actions #2

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 7.0.4 to 7.0.5
Actions #3

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 7.0.5 to 7.0.6
  • Priority changed from 59 to 58
Actions #4

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 7.0.6 to 7.0.7
  • Priority changed from 58 to 0
Actions #5

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 7.0.7 to 7.0.8
Actions #6

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 7.0.8 to 1002
Actions #7

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 1002 to 7.1.7
Actions #8

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 7.1.7 to 7.1.8
Actions #9

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 7.1.8 to 7.1.9
Actions #10

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 7.1.9 to 7.1.10
Actions #11

Updated by Benoît PECCATTE almost 2 years ago

  • Target version changed from 7.1.10 to 7.2.4
  • Regression set to No
Actions #12

Updated by Benoît PECCATTE almost 2 years ago

  • Status changed from New to In progress
  • Assignee set to Benoît PECCATTE
Actions #13

Updated by Benoît PECCATTE almost 2 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder-agent/pull/371
Actions #14

Updated by Benoît PECCATTE almost 2 years ago

  • Status changed from Pending technical review to Pending release
Actions #18

Updated by Elaad FURREEDAN almost 2 years ago

  • Related to Bug #22290: Script node to relay don't detect webapp port when we configure a virtualhost with a different port added
Actions #19

Updated by Alexis Mousset almost 2 years ago

  • Fix check changed from To do to Checked
Actions #20

Updated by Vincent MEMBRÉ almost 2 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 7.2.4 which was released today.

Actions

Also available in: Atom PDF