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

Wrong response for map files #356

Closed
Maharacha opened this issue Jan 21, 2025 · 2 comments
Closed

Wrong response for map files #356

Maharacha opened this issue Jan 21, 2025 · 2 comments

Comments

@Maharacha
Copy link

I upgraded from v2.8.3 to v2.9.8 and started to get these kind of entries in the responses. This particular response is from endpoint /v2/services/haproxy/runtime/maps?include_unmanaged=true. I see similar problem with other endpoints for the map files. Modifying map files would also add these kind of entries to the actual map file on disk.

[
  {
  
  "description": "but maybe one of the following ones is a better match:",
  
  "file": "command,",
  
  "id": "Unknown"
  
  },
  
  {
  
  "description": "send a command to the <pid> process",
  
  "file": ":",
  
  "id": "@!<pid>"
  
  },
  
  {
  
  "description": "send a command to the master process",
  
  "file": ":",
  
  "id": "@master"
  
  },
  
  {
  
  "description": "lower the level of the current CLI session to operator",
  
  "file": ":",
  
  "id": "operator"
  
  },
  
  {
  
  "description": ": show version of the current process",
  
  "file": "version",
  
  "id": "show"
  
  },
  
  {
  
  "description": "lower the level of the current CLI session to user",
  
  "file": ":",
  
  "id": "user"
  
  },
  
  {
  
  "description": ": list matching or all commands",
  
  "file": "[<command>]",
  
  "id": "help"
  
  },
  
  {
  
  "description": "toggle interactive mode with prompt",
  
  "file": ":",
  
  "id": "prompt"
  
  },
  
  {
  
  "description": "disconnect",
  
  "file": ":",
  
  "id": "quit"
  
  }
]
@Maharacha
Copy link
Author

I just went through the different versions. The problem starts at v2.8.7. I have also tried the latest v3.0.4 and same problem.

@Maharacha
Copy link
Author

I updated Haproxy to a newer version and this bug was gone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant