1471862 - t-win1064-ms-281 is unresponsive

Status: RESOLVED FIXED

(Infrastructure & Operations :: DCOps, task)

Description

[Zsolt Fay [:zfay]]

Attachment: boot error

The worker is missing from taskcluster and papertrail. 
Upon using the java interface from the iLo I noticed we are getting an error (see attachment)message and it freezes at PXE boot.

Comment 1

[Zsolt Fay [:zfay]]

We have force stopped the instance multiple times and have started it up again. It is now running and the green OK alert came

Comment 2

[Zsolt Fay [:zfay]]

Made a mistake with the above comment, this machine is still broken and probably needs to be physically checked.

Comment 3

[Van Le [:van]]

can you let me know which chassis/blade?

Comment 4

[Adrian Pop]

The machine can be found on chassis 7, cartridge c11, node 11 and the Cartridge Serial is CN67220BHL.
I hope these info are helpful

Comment 5

[Van Le [:van]]

opened REQ0235355 with QTS to reseat blade.

Comment 6

[Van Le [:van]]

task completed by QTS. please reopen if issues persist.

Comment 7

[Attila Craciun [:arny]]

Attachment: ms-win10-281.PNG

This is still not working, I have powered off/on, could booted and is stuck at the PXE boot.

Comment 8

[Van Le [:van]]

there's not much i can without further information and HPE won't RMA without logs of hardware issues.

1) is this cartridge on the correct VLAN? (im not sure what vlan it needs to be on, i can check)
2) do any of the other blades in the same chassis and same vlan work while this one doesn't? 
3) are there any special boot options we need to include or might have missed in infoblox?
4) if you feel this is a hardware issue, do you have any logs?

Comment 9

[Van Le [:van]]

do you want me to request QTS to reseat the cartridge again?

Comment 10

[Attila Craciun [:arny]]

(In reply to Van Le [:van] from comment #8)
> there's not much i can without further information and HPE won't RMA without
> logs of hardware issues.
> 
> 1) is this cartridge on the correct VLAN? (im not sure what vlan it needs to
> be on, i can check)

I'm not sure about this.

> 2) do any of the other blades in the same chassis and same vlan work while
> this one doesn't? 

Yes, others are fine. I just tested MS282 and PXE works.

> 3) are there any special boot options we need to include or might have
> missed in infoblox?

No sure.

> 4) if you feel this is a hardware issue, do you have any logs?

There are no logs, errors.

Comment 11

[Attila Craciun [:arny]]

(In reply to Van Le [:van] from comment #9)
> do you want me to request QTS to reseat the cartridge again?

Yes, please.

Comment 12

[Van Le [:van]]

opened REQ0236408 to have blade reseated.

Comment 13

[Zsolt Fay [:zfay]]

Thx :van ! For more info: The machine is missing from TC and iLo displays only a pitch black java interface. Cold booting does nothing.

Comment 14

[Zsolt Fay [:zfay]]

Hey :dhouse, in case reseating the blade doesn't help can you add this machine to the list of issues to go to HPE with?

Comment 15

[Van Le [:van]]

:zsoltfay, actually QTS just completed the task. can you check now please?

Comment 16

[Zsolt Fay [:zfay]]

(In reply to Van Le [:van] from comment #15)
> :zsoltfay, actually QTS just completed the task. can you check now please?

It's still not showing up in TC and still frozen at pxe boot. Dhouse said he will have a look at it a bit later.

Comment 17

[Van Le [:van]]

let me know if you need hands on.

Comment 18

[Zsolt Fay [:zfay]]

I've just checked at the worker is still freezing at boot. Dhouse do you think a physical check is required ?

Comment 19

[:dhouse]

redirect to Mark. I tried pinging this machine and get no response. I shut it down from the moonshot interface and then powered it back on. It doesn't respond to ping after that. Maybe it is still getting stuck at boot or needs reimaged?

Comment 20

[Mark Cornmesser [:markco]]

It looks like this blade is  continuously trying to pxe boot and is never getting anywhere. 

Van: Could you check the network configuration for this node?

Comment 21

[Van Le [:van]]

it is currently on vlan 208. which vlan should it be on?

Comment 22

[Mark Cornmesser [:markco]]

It should be in vlan 240.

Comment 23

[Van Le [:van]]

tagged with 240.

Comment 24

[Attila Craciun [:arny]]

I have managed to reimage.