Question: delete the pod?

Asked By
hubt
Asked At
2017-12-05 23:41:23

Found 15 possible answers.

User Answered At Possible Answer
llambda 2017-12-05 23:43:52 why doesn't kubectl get all include the output of kubectl get pvc ? is there any way to truly list all k8s objects?
stump 2017-12-05 23:44:23 yeah, delete the pod doesn’t fix it
robocop 2017-12-05 23:46:08 i am guessing that the ebs volume hasn't cleanly umounted from another node. check that the volume isn't currently stuck on another node.
stump 2017-12-05 23:52:14 @robocop the node that it was attached to doesn’t exist anymore and the aws api is showing the volume as available can i attach the volume manually?
robocop 2017-12-05 23:55:57 have you checked in the EBS dashboard that everything looks good as well? maybe try mounting the drive to another ec2 instance and see if the data is still there. potentially could have been corrupt. did the old node die or something? did you rebuild your cluster?
stump 2017-12-05 23:57:28 yeah, the old node died i’ve had this happen before, after restarting all the masters it went away and the ASG brought a new one up
weaseal 2017-12-05 23:58:09 @stump any tags on the volume in AWS? maybe those need resetting? just a guess based on how other k8s logic works
stump 2017-12-05 23:59:12 tags are good, it’s an etcd state thing
ivanc 2017-12-06 00:01:13 hi guys, i need your help, i need change the ethernet weave
 weave     Link encap:Ethernet  HWaddr 3e:c5:3c:45:bc:9a  
          inet6 addr: fe80::3cc5:3cff:fe45:bc9a/64 Scope:Link 
inet addr:10.32.0.1 Bcast:0.0.0.0 Mask:255.240.0.0
hubt 2017-12-06 00:02:11 if you're desperate you can try some kinds of surgery, like unbind the pvc from the pv, then set the new pv to the old volume.
stump 2017-12-06 00:02:46 going to try restarting the masters
hubt 2017-12-06 00:02:55 yea, i'd do that first.
robocop 2017-12-06 00:03:11 if that works, sounds like a bug with aws asg
hubt 2017-12-06 00:03:39 no, it's a k8s issue. there's some issues with ebs volume management. ebs is sometimes a bit finicky, but k8s makes it worse sometimes.
ivanc 2017-12-06 00:24:15 pls help.! inet6 addr: fe80 :: 3cc5:3cff:fe45:bc9a/64 Scope:Link
my problem is that the subnet is a valid, i need have to access to 10.40.x.x but i can´t have access
          inet addr:10.32.0.1  Bcast:0.0.0.0  Mask:255.240.0.0
[December 5th, 2017 4:01 PM] ivanc: hi guys, i need your help, i need change the ethernet weave 
weave Link encap:Ethernet HWaddr 3e:c5:3c:45 :bc: 9a

Related Questions