Tales from the Machine Room

Home Page | Comments | Articles | Faq | Documents | Search | Archive | Tales from the Machine Room | Contribute | Set language to:en it | Login/Register

Everybody or Nobody

It's Monday (incidentally) and like any monday we have the pile of problems that happened during the week-end and instead of  being checked or fixed during the week-end by the person that was supposed to do so, they have simply been ignored, so now we have them together with all the rest of the "normal" requests and complaints.

Just because I am stupid, I pick the first from the pile and look at it.

So, CL from CL's company is complaining that the procedure to change this-and-that that we implemented didn't worked for the whole week-end and even if he called the "hot-standby" number nobody did anything to fix the problem.

After notifying DumBoss that he should check that whoever should answer the 'hot-standby' actually do so, I look at that "procedure".

The first step is to check into the company's Wiki. Obviously I can't find anything useful. A tiny page that says the procedure was requested with a ticket. I check the ticket where there is a vague request to take some data from some database and make them available for some other procedure that isn't clear what should then do.

The ticket is "closed" and the "owner" is the very same guy that was supposed to answer hot-call (from now on PG).

At this point, I route the ticket to PG with a note to document the bloody thing.

Fast-Forward a couple of days, when CL above calls to ask what the fuck happened with his ticket from monday and his procedure. At this point, since I don't have any clue about the status of that thing, I answer that we'll let him know and escalate directly to DumBoss.

DB - And what did PG said?
Me - To me, nothing, and since the ticket that are assigned cannot be seen unless you have super-mega-admin rights, I've no clue.
DB - But did you asked him?
Me - How can I ask if he is not in the office and is not "on line" in the chat?
DB - Hmmm... He shouldn't be in holiday...
Me - You know that.
DB - Ok, let's see when he arrives and what he say...
Me - It's 10.30, isn't the "standard time" between 8 and 8.30 ?
DB - Eh...

In any event, PG decide to arrive "with leisure" after 11 and get immediately tackled.

DB - What happened with CL's ticket?
PG - Which ticket?
Me - The one I routed to you on Monday.
PG - Ah, didn't had the time to look at it.
Me - Good. Did you told CL?
PG - No, I had no time.
DB - Ok, inform CL then.
Me - Just out of curiosity, what the heck have you been doing since monday?
PG - Ah, that thing for $verylargecompany..
Me - The one I fixed last week and also announced during Monday's Big Meeting?
PG - ...You fixed it?
Me - Were you sleeping during the meeting or were you pretending to sleep?

Great! So PG spent 3 days doing fucking nothing, anyhow the problem is in his (in)capable hands and I'll let him deal with it. After a few more days, I get again CL at the phone, and he still hasn't heard anything at all from PG and his "procedure". Ok, let's go back to PG. What a joy!

Me - I have again CL at the phone that asks about his procedure.
PG - Ah, nothing.
Me - What nothing?
PG - Nothing is happening.
Me - Yes, I know, why don't you let CL also know?
PG - I mean, the procedure works fine.
Me - Not if you ask CL.
PG - Well, I can't do nothing about that.
Me - Since you made the procedure you could do something about it, at least explain it to CL.
PG - The procedure works, I don't know why it doesn't work for CL.
Me - Then ask him.

And at this point I decide to get back to do something useful before I start yelling insults at him.

The following week, CL is back with more, this time however, he decide to directly call DumBoss, and he decide, for some unfathomable reason, to came directly to me!

DB - ...so CL thinks that the procedure isn't working.
Me - And why are you telling that to me? The procedure was made by PG.
DB - Yes but PG doesn't know how to make that work.
Me - Listen, if I make a script and that script doesn work for  you, you don't tell to PG to have a look at it, you tell me. So, why don't you tell PG to fix his own crap? It shouldn't be too difficult. If he actually made that fucking "procedure".

Obviously, after a while I start looking at that fucking "procedure" that turns out to be an Ansible "script".
If you don't know what the heck is Ansible, it means you're behind in the whole DevOps business, that is, you haven't missed anything really.

Ansible is a ... thing... in practice, it implements a slightly better version of "Expect". It can send "commands" through SSH to a server and process answers. It does other things too, but the basic idea is to copy files to a remote server and execute commands on it. The problem is... it ain't a programming language. Even if some peoples thinks it is.

For example, you can't make something like "If this Then that...". It is possible to say "check if XXX is installed and if not do install it", but not "If XXX is installed then..."

Now, apparently what PG made is a very convoluted and complicated way of copying files from one place to another and then run some sort of "grep" on them. Something that should have been a lot faster and simpler with a stupid SCP/Grep/bash script.

I run that contraption and I get an error. It looks like something is wrong with it.

Me - Here is the problem: it doesn't work.
PG - That just the initial part.
Me - Yeah, and it doesn't work. If the initial part doesn't work, then the final part is not worth looking at. Did you tested this crap?
PG - No, is not a problem if the starting part doesn't work.
Me - Let's see this "script"... The initial part is the one that copy the file from one place to another. If that fails already how can the rest works?
PG - Probably because the file ain't there.
Me - And if it ain't there how can you process it?
PG - If is not there, I don't process it. Simple.
Me - (login on the server, ls, the file is there) The file is there.
PG - ...
Me - (run script: error) So is not that the file ain't there.
PG - ... I didn't noticed that.
Me - Nice. Now you noticed. You can go on with the debugging.
PG - But... How?
Me - I don't know. You said you were going to make this thing, now you've seen where the problem is, you can proceed with the rest. And inform CL.

But I already know that it won't happen. He won't fix this piece of shit and he won't inform CL.

02/05/2018 15:35

Previous Next

Comments are added when and more important if I have the time to review them and after removing Spam, Crap, Phishing and the like. So don't hold your breath. And if your comment doesn't appear, is probably becuase it wasn't worth it.

9 messages this document does not accept new posts


By Naxos posted 23/05/2018 09:01

Questa moda del DevOps passerà, prima o poi: spero più prima che poi. Riguardo ad Ansible: hai perfettamente ragione; chi non ne ha mai saputo niente non si perde niente - a quanto pare serve solo ai pinguini per farli sentire struzzi...

-- Naxos


By emi_ska posted 23/05/2018 09:07

Ciao, sono daccordo che il linguaggio usato da Ansible (yaml) non sia un linguaggio di programmazione, ma come programma è ottimo se devi realizzare installazioni in serie su molti servers...

Certo che usarlo per spostare un file e poi fare una grep... faceva prima con uno script sh!!!

P.S. Sono sempre felice quando arrivo in ufficio, accendo e c'e' una tua storia!!

-- emi_ska


By Nik posted 23/05/2018 11:03

Ma PG ci è o ci fa? (o entrambe?)

-- Chronicles of a Broken Heart


By Guido posted 24/05/2018 07:36

PG - Ah, quella roba per $megaditta...

IO - Quella che ho risolto io la settimana scorsa e l'ho anche detto Lunedi' durante la Riunione Settimanale?

PG - ...Ah l'hai risolta ?


Signori ecco un genio! Uno che sta due giorni a fare qualcosa gia' fatto da altri...

-- who uses Debian learns Debian but who uses Slackware learns Linux

Anonymous coward

@ Guido By Anonymous coward posted 24/05/2018 13:45

> "Signori ecco un genio! Uno che sta due giorni a fare qualcosa gia' fatto da altri"


...lo scemo sono io, che dopo 40 giorni che qualcuno non riesce a fare un restore, in seguito all'ennesima escalation ci provo, e nel giro di 4 ore ho finito.


-- Anonymous coward


@ Anonymous coward By Guido posted 25/05/2018 07:43

...lo scemo sono io, che dopo 40 giorni che qualcuno non riesce a fare un restore, in seguito all'ennesima escalation ci provo, e nel giro di 4 ore ho finito.

Consolati non sei da solo - figurati da questo lato dello schermo io oltre a fare il mio lavoro (sviluppare sw) mi tocca anche fare assistenza sistemistica a $HOSTING_PAMPERS (si hai letto bene! Sono io che devo dire a loro qual'e' il problema e come si risolve)




-- who uses Debian learns Debian but who uses Slackware learns Linux

Anonymous coward

By Anonymous coward posted 25/05/2018 18:51

Ma licenziare PG? Dopotutto uno che arriva quando gli pare e non fa le cose che dovrebbe fare, che lo pagate a fare?

-- Anonymous coward

Messer Franz

By Messer Franz posted 26/05/2018 10:37

Riguardo la storia: ma PG è almeno il parente o l'amante del boss? Cioè, un motivo ce l'ha per stare in ditta? O semplicemente la trafila per un licenziamento è troppo lunga in quell'azienda?

A parte: hai presente che (se ho capito bene) non ti stava troppo simpatico l'Ubuntu? Ecco, per lavoro (vari motivi) ho dovuto sviluppare sotto linux, e , dato che non avevo dieci anni e rotti* per imparare le basi di come installare un programma sotto un linux "vero"  (bestemmiare liberamente su quelle <censura> di librerie mancanti inesistenti non documentate vecchia versione ma il codice non c'è più o non va con l'ultima versione dello gnu ecc.) e quindi sono andato di ubuntu (xubuntu, per la precisione); bene, prima hanno tolto il supporto per i pc "vecchi" (perchè si sa che un linux "leggero" non viene mai usato per pc di quel tipo) , ma ora con l'ultima versione che ho provato ad installare un mesetto fa ti posso dire che è andato a schifìo; non installa, non "legge" i repository, capriole per fargli solo compilare del codice... ho reistallato la precedente (la 16, mi pare) e tutto ok.

Quindi non sono io (non del tutto , per lo meno).

Quindi gioisci, l'Ubuntu sta non per morire come un qualsiasi prodotto schifoso, ma si sta suicidando teatralmente emettendo rantoli in faccia a chi lo usa...


*UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity - Dennis Ritchie

-- Messer Franz

Daniele Lupo

By Daniele Lupo posted 01/06/2018 14:05

Tutto molto bello ma io ancora aspetto la storia di $succhiasangue dopo quella di $formaggini...

-- Daniele Lupo

9 messages this document does not accept new posts

Previous Next

This site is made by me with blood, sweat and gunpowder, if you want to republish or redistribute any part of it, please drop me (or the author of the article if is not me) a mail.

This site was composed with VIM, now is composed with VIM and the (in)famous CMS FdT.

This site isn't optimized for vision with any specific browser, nor it requires special fonts or resolution.
You're free to see it as you wish.

Web Interoperability Pleadge Support This Project
Powered By Gojira