The definitive thread on Qantas IT gripes.

[Cloud9]

Qantas let the QLD interns play with the clocks or something?

My flight is 15:00 tomorrow so im aware check in should be in ~45 mins and instead at 14:12 I get this SMS.

Wonder if it's a cron job that they kick off in their system ahead of 24 hours to try and make sure everything's dispatched so folk have their message before T-23

 

[RichardMEL]

Wonder if it's a cron job that they kick off in their system ahead of 24 hours to try and make sure everything's dispatched so folk have their message before T-23

Heh. I wonder how many readers know what "cron" referrs to.

For those scratching their heads at the reference, "cron" is a the name of a process under the UNIX operating system, that as the name may suggest, deals with time related things - specifically scheduling of processes to run in the system. Usually used to kick off regular things like maintenance processes on a system that may run every minute, x times per hour, hours per day etc up to specific days in a year. Quite useful for regular thing you may want to run at certain times to a schedule.

The idea @Cloud9 is suggesting here I think is perhaps a process in the backend running say every minute that checks any flights due to depart in 24h, and for any flight scheduled in 24h to then put them kick off associated processes eg open OLCI.

 

[Cloud9]

Heh. I wonder how many readers know what "cron" referrs to.

For those scratching their heads at the reference, "cron" is a the name of a process under the UNIX operating system, that as the name may suggest, deals with time related things - specifically scheduling of processes to run in the system. Usually used to kick off regular things like maintenance processes on a system that may run every minute, x times per hour, hours per day etc up to specific days in a year. Quite useful for regular thing you may want to run at certain times to a schedule.

The idea @Cloud9 is suggesting here I think is perhaps a process in the backend running say every minute that checks any flights due to depart in 24h, and for any flight scheduled in 24h to then put them kick off associated processes eg open OLCI.

Most eloquently put, sir. Most eloquently put.
Apologies for the unexplained nerd speak. I hadn't had my coffee...

 

[RichardMEL]

All good There's quite a few of we IT types in the forum who would know, but a lot likely who wouldn't. You got your point across regardless of course (easy enough to figure out from the rest of your comment). I just thought I'd explain the reference. i'm sure many of us drop in jargon we're used to without thinking much about it because it's second nature into every day things. I'd be willing to bet I've done it

However I'm not going to explain the "finger" command... or the "halt -n" option (to be used if your CPU is on fire.. )

 

[RooFlyer]

All good There's quite a few of we IT types in the forum who would know, but a lot likely who wouldn't. You got your point across regardless of course (easy enough to figure out from the rest of your comment). I just thought I'd explain the reference. i'm sure many of us drop in jargon we're used to without thinking much about it because it's second nature into every day things. I'd be willing to bet I've done it

However I'm not going to explain the "finger" command... or the "halt -n" option (to be used if your CPU is on fire.. )

I think there's only command we non-IT types need to know. Turn off, re-start. Seems to fix just about everything.

 

[RichardMEL]

I think there's only command we non-IT types need to know. Turn off, re-start. Seems to fix just about everything.

Or as we say...

 

[tdimdad]

Perhaps not a QF error per se but a bizarre one, anyway. It suddenly popped up on FR24 when I was checking for the departure of QF51.



That would make for a memorable trip, though perhaps not the way one would love it.

 

[Cloud9]

Perhaps not a QF error per se but a bizarre one, anyway. It suddenly popped up on FR24 when I was checking for the departure of QF51.

View attachment 383643

That would make for a memorable trip, though perhaps not the way one would love it.

Wonder if they just take the broom head off and pass you the handle for when you get on the flight. I mean, if they're going to shaft you, might as well do a thorough job of it.

 

[RichardMEL]

Going to guess a typo somewhere and it was meant to be VH-EBV?

Or not. Being operated by EBS today.

 

[tdimdad]

Going to guess a typo somewhere and it was meant to be VH-EBV?
Or not. Being operated by EBS today.

You'd hope so. The peculiar thing is that earlier in the morning it showed EBS, then suddenly changed to SBV. It's correct now again but the integration of systems / data transfers seem to have holes in somewhere.

 

[kpro]

Perhaps not a QF error per se but a bizarre one, anyway. It suddenly popped up on FR24 when I was checking for the departure of QF51.

View attachment 383643

That would make for a memorable trip, though perhaps not the way one would love it.

I wrote about this weird behaviour a while back when looking at QF9 on FR24. The explanation from Mattg was "SYD-OAG is QF2009. The callsign is shortened to Q-Link 9D (and is tracked as QLK9 - not to be confused with QFA9), which causes a bit of confusion with some of the websites."

So in this case FR24 is confusing QF51 with QF2051, a Dash 8 service from MEL to DPO.

 

[kpro]

Looks like the text which tells you to select seats on a partner airline website has gone missing.

 

[RSD]

Is it just me or has the rate of errors on the QF website gone through the roof the last few days? I'm getting so many that it is just totally ridiculous - this is the latest one this morning

 

[RSD]

And now this one -

 

[Cloud9]

Is it just me or has the rate of errors on the QF website gone through the roof the last few days? I'm getting so many that it is just totally ridiculous - this is the latest one this morning
View attachment 383767

At least that one can be pinned squarely at the feet of front end cowboys "developers".