How to avoid update breakage?

Discussion in 'General' started by bill_mcgonigle, Apr 9, 2009.

  1. bill_mcgonigle

    Joined:
    Jun 9, 2008
    Messages:
    3
    Likes Received:
    0
    I'm assuming I'm doing something wrong here. A few times now, including just this week with 1.5.2, an Elastix update has rendered my PBX unusable.

    What I've found each time is that a bunch of FreePBX modules are "disabled, pending upgrade" and I have to log into the PBX and take the updates manually. They all work no problem, but the PBX is broken until I do so. For example, if the IVR is down and that's a destination on an inbound route.

    I want to get the security updates via yum, but I don't want PBX breakage. This seems like it would be the default condition, so that's why I figured I messed something up along the way. I'm sure I could figure out the relevant packages and enter yum excludes for each, but since we have so many Elastix users who aren't sysadmins that's likely the wrong approach.

    I'd want to be sure this is being handled correctly before I try deploying systems for others, or they're gonna hate on me for it.

    Does anybody else have this problem or know why mine might be unusual?
     

Share This Page