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

CSE 3.0.2 with VCD 10.2.2 after finish the installation the cse ovdc list is not working and can't enable k8s to the tenant, attached some screenshot. #1244

Open
amns12 opened this issue Oct 13, 2021 · 10 comments
Labels

Comments

@amns12
Copy link

amns12 commented Oct 13, 2021

Capture
Capture1

@sahithi
Copy link
Collaborator

sahithi commented Oct 19, 2021

That is strange.
@sakthisunda Sakthi, do we hide the "ovdc" command for any CSE-VCD version combination?

@amns12
Is CSE server running?
Can you paste the output of "vcd cse -h", "vcd cse system info", "vcd cse ovdc -h"?

@sakthisunda
Copy link
Contributor

sakthisunda commented Oct 20, 2021

@sahithi : we do hide ovdc subcommandsenable/disable/list for CSE 3.0, API 33.0, 34.0 to enable placement policy based ovdc. Ref: #756. So, it only hides vcd cse ovdc subcommands.

But the above error is : vcd cse ovdc parent command itself is failing. So, if @amns12 provides the output of the above commands requested, it would be helpful.

@amns12
Can you also logout and relogin to get the right CSE client version before running the above commands. Thanks

@amns12
Copy link
Author

amns12 commented Oct 24, 2021

@sahithi please find attached the output show nothing
github-SS
@sakthisunda I logged out and logged in still having same issue, also I'm using VCD 10.2.2 which API version is 35.2, should I change the config file to accept lower API versions !
Thank you all.

@amns12
Copy link
Author

amns12 commented Oct 28, 2021

please advice.

@sakthisunda
Copy link
Contributor

@amnss12
If possible can you share the following:

  • server configuration file after removing username/password credentials
  • ~/.vcd-cli/profiles.yaml
  • execute : which cse command on both server and client side

Restart your server, if you haven't tried before client logout/login.
Also, I will try to check from my setup, if I encounter the same issue and update

@sakthisunda
Copy link
Contributor

Thanks for attaching: ~/.vcd-cli/profiles.yaml
In this file, cse_server_running: false causes the issue of not seeing the actual command options.

Please remove: cse_server_running: false from ~/.vcd-cli/profiles.yaml and save it.
Make sure that CSE server is running and relogin. This will update ~/.vcd-cli/profiles.yaml with correct values.
This will enable all the supported commands for the specific client version(35.0).

Try vcd cse -h or any specific command

Please let us know.

@amns12
Copy link
Author

amns12 commented Nov 6, 2021

The CSE server keep stopping and each time the value updated to false, what could be the issue

@sakthisunda
Copy link
Contributor

sakthisunda commented Nov 8, 2021

  1. Please attach cse-server-debug.log when the server is up and running and when it stops running. Please notice what is recorded in the log file.
  2. check if the server is reachable. If the server is not running, the above behavior is expected. I remember you were using mqtt messaging.
  3. To avoid any python library conflicts, we suggest to use virtual environment for install/run server and CLI which may resolve your issue.(Ref: https://vmware.github.io/container-service-extension/cse3_1/CONTRIBUTING.html).
  4. Also run: pip list in your environment and check with the following output that I have pasted for CSE 3.0.2

image
5. If you resolve server issue, make sure that removing cse_server_running: false from ~/.vcd-cli/profiles.yaml and relogin
6. If you are running CSE as a service, please make sure the paths to config.yaml and cse.sh are right in cse.sh and cse.service.

@amns12
Copy link
Author

amns12 commented Dec 13, 2021

just solved my issue thank you.

@sakthisunda
Copy link
Contributor

@amns12 Thanks for notifying us. If you can share how you resolved the issue,

  • that would be helpful in knowing any improvment or gaps in the solution or documentation, understanding new customer setup and improvment.
  • Recommending the solution to customers who face similar issue in future.
  • Your feedback is highly important and valuable to us. Thanks

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

No branches or pull requests

3 participants