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

Unable to switch containers in the terminal #3602

Closed
onprema opened this issue Feb 22, 2019 · 5 comments · Fixed by #3783
Closed

Unable to switch containers in the terminal #3602

onprema opened this issue Feb 22, 2019 · 5 comments · Fixed by #3783
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.

Comments

@onprema
Copy link

onprema commented Feb 22, 2019

Environment
Installation method:
Kubernetes version: v1.13.1
Dashboard version: v1.10.1
Operating system: MacOS
Node.js version ('node --version' output): v10.15.0
Go version ('go version' output): go1.11.1 darwin/amd64
Steps to reproduce
  1. Deploy the kubernetes dashboard Deployment, NetworkPolicy, Service, etc.
  2. Port-forward the deployment, mapping the --insecure-port to localhost:whatever
  3. Select a Pod that has more than one container in it
  4. Click "Exec" button to go to terminal
  5. Terminal displays shell prompt for default container
  6. Use drop-down arrow to switch to a different container in the Pod
Observed result
  • A popup message appears that displays the message: Normal closure
  • User is directed back to the shell of the default container
Expected result
  • Terminal should display the shell prompt of the container that was selected from the dropdown menu.
Comments
@onprema onprema added the kind/bug Categorizes issue or PR as related to a bug. label Feb 22, 2019
@eloyekunle
Copy link
Contributor

/good-first-issue

@k8s-ci-robot
Copy link
Contributor

@eloyekunle:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Mar 4, 2019
@anuragprafulla
Copy link

I would like to work on this one. It's my first dashboard issue so it'll be great if I could get some help along the way.

@maciaszczykm
Copy link
Member

@anuragprafulla Sure, it would be the best to open the PR and ask questions from there. If you don't know anything that should be asked before then you can do it from here or on #sig-ui Slack.

@huangcuiyang
Copy link

The problem is also happend after i upgrade dashboard from version v2.0.0-beta5 to version v2.0.0.0-beta8, why???

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants