Summary:	ASTERISK-09105: Unable to add calling rules after installing System Updates
Reporter:	nicki (nicki)	Labels:
Date Opened:	2007-03-26 06:36:51	Date Closed:	2007-03-29 14:03:36
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I'm unable to add any calling rules after installing the updates using the System Configuration shortcut from the Asterisk GUI. ****** ADDITIONAL INFORMATION ****** The provider dropdown (Place this call through) loses it's value after moving to another field. I reinstalled the system from the CD, and it is working again. System config after the reinstall: OS Version: Linux asterisknow.za.astgroup.com 2.6.17.11-1.1.smp.x86.i686.cmov #1 SMP Tue Sep 5 23:07:02 EDT 2006 i686 i686 i386 GNU/Linux Uptime: 13:34:51 up 1:17, 0 users, load average: 0.02, 0.11, 0.12 Asterisk Build: Asterisk 1.4.0 Asterisk GUI-version Revision: 449 $ Server Date & TimeZone: Mon Mar 26 13:34:51 SAST 2007 Hostname: asterisknow.za.astgroup.com
Comments:	By: James Lyons (james) 2007-03-27 16:55:26 You'll experience this bug if you update via rAA, without turning migration off (you'll have to edit /etc/raa/prod.cfg, and set "updatetroves.migrate = False") Reason is, when you click update via the system configuration page, it "migrates" your appliance to the latest group trove on the repo. Currently, the latest group trove specifies an earlier version of the gui than whats on the gui trove. When you 'conary update asterisk-gui' it looks for the latest updates for that trove on the repo. And thats later than what was pulled in, when the group was built. In the meantime, until the next release, you should turn off migration. That way you can update and add new packages without them disappearing after a system update. By: nicki (nicki) 2007-03-29 03:13:21 Thanks, I've made the suggested changes, and will update packages from the command line. By: James Lyons (james) 2007-03-29 13:38:55 Once Beta5 becomes available this issue should be resolved. By: Serge Vecher (serge-v) 2007-03-29 14:03:35 james, you can close issues like this, "pending release branch" is an unused status that will be removed soon.