Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[yugabyted] [UI] yugabyted UI fails to make API calls when the YugabyteDB webserver ports are changed. #17512

Closed
1 task done
nchandrappa opened this issue May 23, 2023 · 0 comments
Assignees
Labels
area/ecosystem Label for all ecosystem related projects kind/bug This issue is a bug priority/medium Medium priority issue

Comments

@nchandrappa
Copy link
Contributor

nchandrappa commented May 23, 2023

Jira Link: DB-6665

Description

Currently, yugabyted-ui makes API calls to the default master/tserver webserver port 7000. When default webserver port is overridden on start, yugabyted-ui fails to load.

Steps to replicating the issue:

  1. Start YugabyteDB node using
./bin/yugabyted start --master_webserver_port=9999
  1. Navigate to yugabyted UI page. Yugabyted UI fails to load the data.

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.
@nchandrappa nchandrappa added area/ecosystem Label for all ecosystem related projects status/awaiting-triage Issue awaiting triage area/ybd yugabyted project related Github tickets. labels May 23, 2023
@nchandrappa nchandrappa self-assigned this May 23, 2023
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue and removed status/awaiting-triage Issue awaiting triage area/ybd yugabyted project related Github tickets. labels May 23, 2023
@nchandrappa nchandrappa added this to To-do in DB Usability May 26, 2023
nchandrappa added a commit that referenced this issue Jun 14, 2023
…t information to the API server.

Summary:
Code changes to pass in the master and tserver webserver port to the API server CLI and subsequent
updates in helper methods to the read the port information from CLI arguments.

Test Plan: manual testing

Reviewers: sgarg-yb, djiang

Reviewed By: sgarg-yb

Subscribers: nikhil

Differential Revision: https://phorge.dev.yugabyte.com/D26160
@nchandrappa nchandrappa moved this from To-do to In-progress in DB Usability Jun 14, 2023
nchandrappa added a commit that referenced this issue Jun 19, 2023
Summary:
Adding support in the API server to retrieve the gflags of each node in the cluster. This is also
required to avoid node.js app directly inovking the Master and Tserver UI instead of the API server.

Test Plan: manual testing

Reviewers: sgarg-yb

Reviewed By: sgarg-yb

Subscribers: nikhil

Differential Revision: https://phorge.dev.yugabyte.com/D26275
dr0pdb pushed a commit to dr0pdb/yugabyte-db that referenced this issue Jul 6, 2023
Summary:
Adding support in the API server to retrieve the gflags of each node in the cluster. This is also
required to avoid node.js app directly inovking the Master and Tserver UI instead of the API server.

Test Plan: manual testing

Reviewers: sgarg-yb

Reviewed By: sgarg-yb

Subscribers: nikhil

Differential Revision: https://phorge.dev.yugabyte.com/D26275
nchandrappa added a commit that referenced this issue Jul 15, 2023
… and tserver webserver port information to the API server.

Summary:
Code changes to pass in the master and tserver webserver port to the API server CLI and subsequent
updates in helper methods to the read the port information from CLI arguments.
Jira: DB-6665

Test Plan: manual testing

Reviewers: sgarg-yb

Reviewed By: sgarg-yb

Subscribers: nikhil

Differential Revision: https://phorge.dev.yugabyte.com/D26198
@nchandrappa nchandrappa moved this from In-progress to Done in DB Usability Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ecosystem Label for all ecosystem related projects kind/bug This issue is a bug priority/medium Medium priority issue
Projects
Development

No branches or pull requests

2 participants