cloud-provider-openstack
cloud-provider-openstack copied to clipboard
kubernetes
WIP: Remove workaround
What this PR does / why we need it:
Which issue this PR fixes(if applicable): fixes #
Special notes for reviewers:
Release note:
NONE
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: To complete the pull request process, please ask for approval from jichenjc after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
the node we are using ip is following
+ :: : fip=172.24.5.79
+ :: : openstack floating ip set 172.24.5.79 --port 967e4cda-7bcd-4eba-87c1-6d3b2fab2822
error is
STEP: Expecting the symlinks from PodDeviceMapPath to be found.
Jun 9 02:38:25.453: INFO: ssh [email protected]:22: command: sudo sh -c "ls /var/lib/kubelet/pods/20271310-9cbb-4511-b7e2-b046f824c116/volumeDevices/*/ | grep '.'"
Jun 9 02:38:25.453: INFO: ssh [email protected]:22: stdout: "Please login as the user \"ubuntu\" rather than the user \"root\".\n\n"
Jun 9 02:38:25.453: INFO: ssh [email protected]:22: stderr: ""
Jun 9 02:38:25.453: INFO: ssh [email protected]:22: exit code: 142
Jun 9 02:38:25.454: FAIL: Expected grep exit code of 0, got 142
Expected
so if we can enable root login it might solve the problem..
@jichenjc: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| openstack-cloud-csi-manila-e2e-test | 5c1650535c9e1a30dd7f0d98c732a6f065d7c180 | link | true | /test openstack-cloud-csi-manila-e2e-test |
| openstack-cloud-csi-cinder-e2e-test | 5c1650535c9e1a30dd7f0d98c732a6f065d7c180 | link | true | /test openstack-cloud-csi-cinder-e2e-test |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
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. I understand the commands that are listed here.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
@jichenjc: PR needs rebase.
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.
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Reopen this PR with
/reopen - Mark this PR as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closed this PR.
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closedYou can:
- Reopen this PR with
/reopen- Mark this PR as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
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.