FreePBX 14 Framework: Rolled back? Or repo issue?

My system has FreePBX Framework 14.0.13.26.
I’m pretty sure that a few days ago, Module Admin was showing an update to 14.0.13.28 and a total of 26 modules available for update.
Today Module Admin says my 14.0.13.26 is newer than the repo version (14.0.13.23) and a total of 25 modules available for update.

Has Framework been rolled back to 14.0.13.23? Or has the repo been restored from a backup that wasn’t up to date? Or ???

Hi @bitbanger

A few days back we pushed the framework 14.0.13.28 to the stable track and we didn’t roll back to the older version.

Could you please provide the below commands output to us to dig further?

  1. cat /etc/schmooze/pbx-version
    2.cat /etc/schmooze/pbx-brand
    3.fwconsole ma listonline --stable | grep fram
    4.fwconsole ma listonline --edge | grep fram
    5.fwconsole setting MODULE_REPO

Attached is the command output that you requested. It shows framework 14.0.13.23 in both Stable and Edge.
Note: I use only Stable.
FPBX_repo_framework.tgz (1.0 KB)

One more data point: The older version (14.0.13.23) of framework started appearing in the repos some time between the two following dates:

[2020-Apr-10 22:04:52] [UPDATE] (BMO/Notifications.class.php:507) - [NOTIFICATION]-[freepbx]-[NEWUPDATES] - There are 26 modules available for online upgrades

[2020-Apr-11 11:26:26] [UPDATE] (BMO/Notifications.class.php:507) - [NOTIFICATION]-[freepbx]-[NEWUPDATES] - There are 25 modules available for online upgrades

Any news on this?

Hi @bitbanger If you update your modules from “module admin” then also do you see updates available? thanks.

This concerns one module: framework.
I originally noticed the problem from GUI Module Admin.
I see the same thing w/ fwconsole ma listonline.
I just retested: I have framework 14.0.13.26; repo has 14.0.13.23.
Framework 14.0.13.28, which was in the repo for a while, has disappeared from the repo.
If you haven’t already, please check the fwconsole output in the attachment to my previous post.

Hi.
If you try to launch:
# fwconsole setting MODULE_REPO

You should get this
Setting of "MODULE_REPO" is (text)[http://mirror1.freepbx.org,http://mirror2.freepbx.org]

Just to see if you point the the good repos.

@pramarajan asked me to check that and other things above.
That’s what I have for MODULE_REPO.
It’s attached to post above:
FreePBX 14 Framework: Rolled back? Or repo issue?

For my part, I’m under Framework 14.0.13.28.
you can try to force a downloading with
# fwconsole ma downloadinstall framework --tag=14.0.13.28

just an idea like that.

As I said, framework 14.0.13.28 was in the repo for a while. I saw it.
People who updated before it disappeared have it.
Now people can’t get it through a normal update.
I don’t see how I could be the only one seeing this.
I have established that I am using the correct repo URLs.

I think Sangoma needs to find out what happened to the repo between the two dates shown and fix it. Can you pass this along to the responsible party?

I’m attaching an excerpt from freepbx.log.
It shows that before the repos went down they had framework 14.0.13.28.
After the repos came back up framework was no longer being offered to me (because the repos had 14.0.13.23 and my system had 14.0.13.26).

Again, please pass this information along to the responsible party @ Sangoma.

.module_updates.tgz (1.3 KB)

Notes:

  1. The errors starting at [2020-Apr-10 22:22:12] were from a PBX config (database) restore.

  2. The repos were down for a few other people at the same time the repos were down for me. There’s a topic here on the subject.

My apologies. I ran

# fwconsole ma downloadinstall framework --tag=14.0.13.28

as you suggested and that installed framework 14.0.13.28 successfully.

# fwconsole ma listonline

now lists framework correctly.

I don’t know what I did to get my system in the confused state it had been in.
There was nothing wrong with the module repos.

1 Like

Great.

Sometimes inexplicable things happen. C’est la vie :smiley:

2 Likes

C’est Open Source

1 Like

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.