Forums

Resolved
-1 votes
Hi Guys ever since these updates installed below having two errors pop up in yum update.

app-base-2.7.8-1.v7 Updated Oct 02, 09:21:19
app-base-core-2.7.8-1.v7 Updated Oct 02, 09:21:18
app-web-server-2.5.2-1.v7 Installed Oct 02, 08:02:58

The errors found during manual yum update are:
1.) ClearCenter Marketplace: global name 'section_id' is not defined
2.) NameError: global name 'wc_repos' is not defined

I have researched around saw a fix to similar question posted in 2017 not so sure that particular fix still applies?
Your guidance is much appreciated.
Friday, October 11 2019, 08:43 AM
Share this post:
Responses (69)
  • Accepted Answer

    Thursday, October 31 2019, 06:17 PM - #Permalink
    Resolved
    0 votes
    iSparky Systems wrote:

    If we can get clear glass firing (the registration email is problematic - separate issue for a later date) and the older php (currently playing with mono as seen in the repos mentioned before as the alternative) removed we may bump clearos to our client base it all depends on how secure we can get it with ease.
    I can't remember all the forum threads, but note that we can supply PHP up to 7.2 with the PHP Engines app.

    Re the ClearGLASS registration e-mail, there are some simple tricks you can pull if you don't want to set up ClearOS as a proper mail server and if you don't have access to another mail server on your LAN, but can I ask that you open a separate thread as we are going off-topic and I'd like to leave this one for people with the yum issue.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 31 2019, 05:50 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    iSparky Systems wrote:

    Should the same error re occur within the next 14 days subscription cancelled alternative already up and running. Public facing needs to be updated effortlessly. Thanx
    As far as we are aware the issue only affected some new installations and (a bit convoluted) old installations that became deregistered (expired) and subsequently updated from the community repos. I only ever got it once by deregistering a new install and then trying to change it to Business. We also think it only affected Community installations and as such was blocking the release of the 7.7 for Home and Business.



    Here changed from Community to Home waiting on pen test results which was obviously stalled with the update issue. If we can get clear glass firing (the registration email is problematic - separate issue for a later date) and the older php (currently playing with mono as seen in the repos mentioned before as the alternative) removed we may bump clearos to our client base it all depends on how secure we can get it with ease.

    The ease (efficiency) most definitely seems to be there - and that We will support and always applause. But always number one priority security - no update left behind :P
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 31 2019, 04:37 PM - #Permalink
    Resolved
    0 votes
    iSparky Systems wrote:

    Should the same error re occur within the next 14 days subscription cancelled alternative already up and running. Public facing needs to be updated effortlessly. Thanx
    As far as we are aware the issue only affected some new installations and (a bit convoluted) old installations that became deregistered (expired) and subsequently updated from the community repos. I only ever got it once by deregistering a new install and then trying to change it to Business. We also think it only affected Community installations and as such was blocking the release of the 7.7 for Home and Business.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 31 2019, 04:10 PM - #Permalink
    Resolved
    0 votes
    Thanks for the update.

    For anyone else with the problem you can either do the manual edit or:
    rpm -Uvh https://mirror1-newyork.clearos.com/clearos/7/updates-testing/x86_64/RPMS/yum-marketplace-plugin-2.3-2.v7.noarch.rpm
    yum clean all


    If the file is not found, it means we have promoted it to clearos-updates and the command to fix becomes:
    rpm -Uvh https://mirror1-newyork.clearos.com/clearos/7/updates/x86_64/RPMS/yum-marketplace-plugin-2.3-2.v7.noarch.rpm
    yum clean all
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 31 2019, 03:21 PM - #Permalink
    Resolved
    0 votes
    iSparky Systems wrote:

    Nick Howitt wrote:

    Gents, please can you try a one line fix. In /usr/lib/yum-plugins/clearcenter-marketplace.py add a line after 285 (at the end of the init_hook(conduit) function), changing:
        except Exception, msg:
    conduit.info(2, 'ClearCenter Marketplace: %s' % msg)
    to:
        except Exception, msg:
    conduit.info(2, 'ClearCenter Marketplace: %s' % msg)
    wc_repos = []
    Then try again.


    I have made the code change the execution of yum update seems to be running fine now at 240/572 - will revert with login info should the need arise after execution has completed or erred. Thank you for your time.


    Update Completed - Mark Resolved. Should the same error re occur within the next 14 days subscription cancelled alternative already up and running. Public facing needs to be updated effortlessly. Thanx
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 31 2019, 03:12 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    Gents, please can you try a one line fix. In /usr/lib/yum-plugins/clearcenter-marketplace.py add a line after 285 (at the end of the init_hook(conduit) function), changing:
        except Exception, msg:
    conduit.info(2, 'ClearCenter Marketplace: %s' % msg)
    to:
        except Exception, msg:
    conduit.info(2, 'ClearCenter Marketplace: %s' % msg)
    wc_repos = []
    Then try again.


    I have made the code change the execution of yum update seems to be running fine now at 240/572 - will revert with login info should the need arise after execution has completed or erred. Thank you for your time.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 31 2019, 02:54 PM - #Permalink
    Resolved
    0 votes
    @iSparky Systems,
    Posts crossed. If what I have just posted does not work, ssh access would be great. Or I can do it for you. Just submit your credentials to https://secure.clearcenter.com/portal/system_password.jsp.
    Thanks
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 31 2019, 02:51 PM - #Permalink
    Resolved
    0 votes
    Hi guys sorry for the late reply - Registered! (Screeny attached) Remote access are not a problem - let me catch up with the thread in the next 5-10 minutes :)
    ssl vpn ok so you can ssh web console and do all the scratchy things you need to do?
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 31 2019, 02:51 PM - #Permalink
    Resolved
    0 votes
    Gents, please can you try a one line fix. In /usr/lib/yum-plugins/clearcenter-marketplace.py add a line after 285 (at the end of the init_hook(conduit) function), changing:
        except Exception, msg:
    conduit.info(2, 'ClearCenter Marketplace: %s' % msg)
    to:
        except Exception, msg:
    conduit.info(2, 'ClearCenter Marketplace: %s' % msg)
    wc_repos = []
    Then try again.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 31 2019, 02:48 PM - #Permalink
    Resolved
    0 votes
    Hi guys sorry for the late reply - Registered! (Screeny attached) Remote access are not a problem - let me catch up with the thread in the next 5-10 minutes :)
    ssl vpn ok so you can ssh webcole and do all the scratching you need to do?
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 31 2019, 10:52 AM - #Permalink
    Resolved
    0 votes
    I have now been able to reproduce if the system is unregistered by deleting my registration. @khvalera and ISparky Systems are your systems registered?
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 31 2019, 10:06 AM - #Permalink
    Resolved
    0 votes
    Thanks. As you are still having problems with the wc_repos can you give us remote logon? You've raised a ticket but not supplied any login credentials. Credentials can be supplied securely to https://secure.clearcenter.com/portal/system_password.jsp.

    We are struggling as we cannot reporduce it. I have just tried a couple of fresh installations and both succeeded. It would really help if we could access your system.
    The reply is currently minimized Show
  • Accepted Answer

    khvalera
    khvalera
    Offline
    Thursday, October 31 2019, 09:24 AM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    I am sorry but I don't understand the reference to udvlenie.

    Are you now saying the issue has disappeared> or do you still have the issue?


    Sorry typo, message fixed
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 31 2019, 09:07 AM - #Permalink
    Resolved
    0 votes
    I am sorry but I don't understand the reference to udvlenie.

    Are you now saying the issue has disappeared> or do you still have the issue?
    The reply is currently minimized Show
  • Accepted Answer

    khvalera
    khvalera
    Offline
    Thursday, October 31 2019, 09:01 AM - #Permalink
    Resolved
    0 votes
    iSparky Systems wrote:

    Good Morning Guys

    The error must know it almost Halloween - it haunting again.

    Process followed:
    Same as before really - automatic updates on - other linux systems have updated last couple of days clearos did not went via web console press the software updates - a huge list appeared.
    pressed update - next day same list. Putty - yum update result.

    Traceback (most recent call last):
    File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
    File "/usr/share/yum-cli/yummain.py", line 375, in user_main
    errcode = main(args)
    File "/usr/share/yum-cli/yummain.py", line 281, in main
    return_code = base.doTransaction()
    File "/usr/share/yum-cli/cli.py", line 683, in doTransaction
    problems = self.downloadPkgs(downloadpkgs, callback_total=self.download_callback_total_cb)
    File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 2635, in downloadPkgs
    self.plugins.run('postdownload', pkglist=pkglist, errors=errors)
    File "/usr/lib/python2.7/site-packages/yum/plugins.py", line 188, in run
    func(conduitcls(self, self.base, conf, **kwargs))
    File "/usr/lib/yum-plugins/clearcenter-marketplace.py", line 291, in postdownload_hook
    if pkg.repo in wc_repos:
    NameError: global name 'wc_repos' is not defined

    Would you guys mind supplying manual file(s) installation method once the fix is good to go please?

    I managed to update from the 10th time, but until the end I still did not understand what was the reason. Last done by Delete System
    and then recreated it, maybe it helped.
    Procedure:
    1. Delete System: https://secure.clearcenter.com/portal/device_delete.jsp
    2. Installation of the system.
    3. After the installation is completed and rebooted, I execute the following commands in the console:
    yum update app-base --enablerepo = clearos-updates-testing
    yum clean all
    yum update

    - I get an error again: NameError: global name 'wc_repos' is not defined
    surprisingly, through the web interface, the installation and update were successful.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 31 2019, 08:21 AM - #Permalink
    Resolved
    0 votes
    @iSparky Systems, we would love access to a system we can troubleshoot on. If you are happy, can you raise ticket at https://secure.clearcenter.com/portal/ticket_manage.jsp? As you won't have a subscription, please raise the ticket as a General Enquiry. Please also submit login credentials to https://secure.clearcenter.com/portal/system_password.jsp once you've raised the ticket. If you'd rather not give us username/password access, once you raise the ticket we can give you SSH keys instead. If the device is on your LAN, you may have to port forward tcp:22 to it.

    @khvalera, we have your ticket but you have not submitted your logon credentials so we can't troubleshoot.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 31 2019, 05:13 AM - #Permalink
    Resolved
    0 votes
    Good Morning Guys

    The error must know it almost Halloween - it haunting again.

    Process followed:
    Same as before really - automatic updates on - other linux systems have updated last couple of days clearos did not went via web console press the software updates - a huge list appeared.
    pressed update - next day same list. Putty - yum update result.

    Traceback (most recent call last):
    File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
    File "/usr/share/yum-cli/yummain.py", line 375, in user_main
    errcode = main(args)
    File "/usr/share/yum-cli/yummain.py", line 281, in main
    return_code = base.doTransaction()
    File "/usr/share/yum-cli/cli.py", line 683, in doTransaction
    problems = self.downloadPkgs(downloadpkgs, callback_total=self.download_callback_total_cb)
    File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 2635, in downloadPkgs
    self.plugins.run('postdownload', pkglist=pkglist, errors=errors)
    File "/usr/lib/python2.7/site-packages/yum/plugins.py", line 188, in run
    func(conduitcls(self, self.base, conf, **kwargs))
    File "/usr/lib/yum-plugins/clearcenter-marketplace.py", line 291, in postdownload_hook
    if pkg.repo in wc_repos:
    NameError: global name 'wc_repos' is not defined

    Would you guys mind supplying manual file(s) installation method once the fix is good to go please?
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 29 2019, 09:24 PM - #Permalink
    Resolved
    0 votes
    If possible, we'd like to have a look at your system. Can you raise ticket at https://secure.clearcenter.com/portal/ticket_manage.jsp? As you won't have a subscription, please raise the ticket as a General Enquiry. Please also submit login credentials to https://secure.clearcenter.com/portal/system_password.jsp once you've raised the ticket. If you'd rather not give us username/password access, once you raise the ticket we can give you SSH keys instead.
    The reply is currently minimized Show
  • Accepted Answer

    khvalera
    khvalera
    Offline
    Tuesday, October 29 2019, 09:09 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    The recent update to app-base to fix the upgrade script did not go as planned. As a result, if you see things like "kernel-*" and "samba-*" in /etc/yum.repos.d/centos-unverified.repo or /etc/yum.repos.d/clearos-centos.repo then your upgrade wont work properly. We have just pushed a fix and it is syncing to the mirrors. If you upgrade has failed, please do a:
    yum update app-base --enablerepo-clearos-updates-testing
    yum clean all
    yum update
    You are looking for app-base-2.8.10-1.v7. If you do not get it, try waiting for a bit, do a "yum clean all" then try the update again. Most of the mirrors should be sync'd within a couple of hours.

    The aim is to reduce the "exclude" lines in /etc/yum.repos.d/centos-unverified.repo or /etc/yum.repos.d/clearos-centos.repo to:
    exclude=shim-aa64-* centos-release centos-logos anaconda-* arpwatch cloud-init-* cyrus-imapd-* debugmode grub2-* initscripts iptables-* mokutil-* openldap-* ppp-* rp-pppoe shim-ia32-* shim-x64-*
    The order of the parameters does not matter, just that they and only they exist after upgrading to 7.7.


    Help!!! I can’t get rid of the error when updating :(
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, October 27 2019, 06:59 PM - #Permalink
    Resolved
    0 votes
    A couple of things. app-base was released later yesterday not now a simple "yum update" should pick it up, but it won't as mirrorlist.clearos.com is down at the moment so yum is failing.
    The reply is currently minimized Show
  • Accepted Answer

    khvalera
    khvalera
    Offline
    Sunday, October 27 2019, 06:45 PM - #Permalink
    Resolved
    0 votes
    Marcel van van Leeuwen wrote:

    Install of ClearOS 7.6 upgraded to ClearOS 7.7 (with the new app-base file from "clearos-updates-testing")


    -- Fresh install of ClearOS Community 7.6.

    -- Completed the wizard.

    -- Then after that go to the terminal:

    yum update app-base --enablerepo-clearos-updates-testing


    -- It successfully updated.


    ================================================================================================================================================================
    Package Arch Version Repository Size
    ================================================================================================================================================================
    Updating:
    app-base noarch 1:2.8.10-1.v7 clearos-updates-testing 31 k
    Updating for dependencies:
    app-base-core noarch 1:2.8.10-1.v7 clearos-updates-testing 455 k

    Transaction Summary
    ================================================================================================================================================================
    Upgrade 1 Package (+1 Dependent package)

    Total download size: 487 k
    Is this ok [y/d/N]: y
    Downloading packages:
    Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
    (1/2): app-base-2.8.10-1.v7.noarch.rpm | 31 kB 00:00:00
    (2/2): app-base-core-2.8.10-1.v7.noarch.rpm | 455 kB 00:00:00
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    Total 1.4 MB/s | 487 kB 00:00:00
    Running transaction check
    Running transaction test
    Transaction test succeeded
    Running transaction
    Updating : 1:app-base-core-2.8.10-1.v7.noarch 1/4
    Updating : 1:app-base-2.8.10-1.v7.noarch 2/4
    Cleanup : 1:app-base-2.8.9-1.v7.noarch 3/4
    Cleanup : 1:app-base-core-2.8.9-1.v7.noarch 4/4
    Verifying : 1:app-base-2.8.10-1.v7.noarch 1/4
    Verifying : 1:app-base-core-2.8.10-1.v7.noarch 2/4
    Verifying : 1:app-base-2.8.9-1.v7.noarch 3/4
    Verifying : 1:app-base-core-2.8.9-1.v7.noarch 4/4

    Updated:
    app-base.noarch 1:2.8.10-1.v7

    Dependency Updated:
    app-base-core.noarch 1:2.8.10-1.v7

    Complete!



    -- yum clean all

    [root@localhost ~]# yum clean all
    Failed to set locale, defaulting to C
    Loaded plugins: clearcenter-marketplace, fastestmirror
    ClearCenter Marketplace: fetching repositories...
    Cleaning repos: clearos clearos-centos clearos-centos-sclo-rh clearos-centos-updates clearos-centos-verified clearos-contribs clearos-epel-verified
    : clearos-fast-updates clearos-infra clearos-paid clearos-verified private-clearcenter-dyndns private-clearcenter-ids
    : private-clearcenter-kopano-basic private-clearcenter-verified-updates
    Cleaning up list of fastest mirrors
    Other repos take up 120 k of disk space (use --verbose for details)



    -- yum update

    -- cat /etc/clearos-release

    [root@localhost ~]# cat /etc/clearos-release 
    ClearOS release 7.7.1 (Final)


    -- Everything went following this order okay!


    it didn't work for me:
     One of the configured repositories failed (Неизвестно),
    and yum doesn't have enough cached data to continue. At this point the only
    safe thing yum can do is fail. There are a few ways to work "fix" this:

    1. Contact the upstream for the repository and get them to fix the problem.

    2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

    3. Run the command with the repository temporarily disabled
    yum --disablerepo=<repoid> ...

    4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

    yum-config-manager --disable <repoid>
    or
    subscription-manager repos --disable=<repoid>

    5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

    yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

    Cannot find a valid baseurl for repo: clearos/7
    The reply is currently minimized Show
  • Accepted Answer

    khvalera
    khvalera
    Offline
    Sunday, October 27 2019, 06:43 PM - #Permalink
    Resolved
    0 votes
    it didn't work for me:
    yum update app-base system-base enablerepo=clearos-updates-testing


    One of the configured repositories failed,
    and yum doesn't have enough cached data to continue. At this point the only
    safe thing yum can do is fail. There are a few ways to work "fix" this:

    1. Contact the upstream for the repository and get them to fix the problem.

    2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

    3. Run the command with the repository temporarily disabled
    yum --disablerepo=<repoid> ...

    4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

    yum-config-manager --disable <repoid>
    or
    subscription-manager repos --disable=<repoid>

    5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

    yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

    Cannot find a valid baseurl for repo: clearos/7
    The reply is currently minimized Show
  • Accepted Answer

    khvalera
    khvalera
    Offline
    Sunday, October 27 2019, 06:31 PM - #Permalink
    Resolved
    0 votes
    it didn’t work out for me, it seems that the command is not correct: yum update app-base --enablerepo-clearos-updates-testing.
    or maybe I’m doing it at the wrong time.
    The reply is currently minimized Show
  • Accepted Answer

    kquadrat
    kquadrat
    Offline
    Sunday, October 27 2019, 03:32 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    @kquadrat, I hope that is a copy and paste error, but you have an extra linefeed after cyrus-imapd in your first "exclude" line. All three "exclude" lines should be the same.


    I verified this now and all three "exlude lines" are the same and correct on the server. I should avoid trying to fix broken things late night/early morning and then not able to do a propper copy/paste ;) sorry for it.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, October 27 2019, 08:17 AM - #Permalink
    Resolved
    0 votes
    @kquadrat, I hope that is a copy and paste error, but you have an extra linefeed after cyrus-imapd in your first "exclude" line. All three "exclude" lines should be the same.
    The reply is currently minimized Show
  • Accepted Answer

    kquadrat
    kquadrat
    Offline
    Saturday, October 26 2019, 10:50 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    Anyone with the upgrade issue, please can you post your /etc/yum.repos.d/clearos-centos.repo file?


    I fixed it as Nick wrote before - Thank You ! Here is my /etc/yum/.repos.d/clearos-centos.repo for debugging.


    name=CentOS-$releasever - Base
    baseurl=http://download1.clearsdn.com/centos/7.7.1908/os/$basearch
    http://download2.clearsdn.com/centos/7.7.1908/os/$basearch
    http://download3.clearsdn.com/centos/7.7.1908/os/$basearch
    http://download4.clearsdn.com/centos/7.7.1908/os/$basearch
    enabled=1
    gpgcheck=1
    exclude=shim-aa64-* shim-x64-* shim-ia32-* cloud-init-* shim-0* mokutil-* grub2-* centos-release centos-logos anaconda-* arpwatch cyrus-imapd
    -* debugmode initscripts iptables-* openldap-* ppp-* rp-pppoe
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever

    [clearos-centos-fasttrack]
    name=CentOS-7 - fasttrack
    baseurl=http://download1.clearsdn.com/centos/7.7.1908/fasttrack/$basearch
    http://download2.clearsdn.com/centos/7.7.1908/fasttrack/$basearch
    http://download3.clearsdn.com/centos/7.7.1908/fasttrack/$basearch
    http://download4.clearsdn.com/centos/7.7.1908/fasttrack/$basearch
    enabled=1
    gpgcheck=1
    exclude=shim-aa64-* shim-x64-* shim-ia32-* cloud-init-* shim-0* mokutil-* grub2-* centos-release centos-logos anaconda-* arpwatch cyrus-imapd-* debugmode initscripts iptables-* openldap-* ppp-* rp-pppoe
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever

    [clearos-centos-updates]
    name=CentOS-$releasever - Updates
    baseurl=http://download1.clearsdn.com/centos/7.7.1908/updates/$basearch
    http://download2.clearsdn.com/centos/7.7.1908/updates/$basearch
    http://download3.clearsdn.com/centos/7.7.1908/updates/$basearch
    http://download4.clearsdn.com/centos/7.7.1908/updates/$basearch
    enabled=1
    gpgcheck=1
    exclude=shim-aa64-* shim-x64-* shim-ia32-* cloud-init-* shim-0* mokutil-* grub2-* centos-release centos-logos anaconda-* arpwatch cyrus-imapd-* debugmode initscripts iptables-* openldap-* ppp-* rp-pppoe
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever

    [clearos-centos-extras]
    name=CentOS-$releasever - Extras
    baseurl=http://download1.clearsdn.com/centos/7.7.1908/extras/$basearch
    http://download2.clearsdn.com/centos/7.7.1908/extras/$basearch
    http://download3.clearsdn.com/centos/7.7.1908/extras/$basearch
    http://download4.clearsdn.com/centos/7.7.1908/extras/$basearch
    enabled=1
    gpgcheck=1
    exclude=shim-aa64-* shim-x64-* shim-ia32-* cloud-init-* shim-0* mokutil-* grub2-* centos-release centos-logos anaconda-* arpwatch cyrus-imapd-* debugmode initscripts iptables-* openldap-* ppp-* rp-pppoe
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever

    [clearos-centos-updates]
    name=CentOS-$releasever - Updates
    baseurl=http://download1.clearsdn.com/centos/7.7.1908/updates/$basearch
    http://download2.clearsdn.com/centos/7.7.1908/updates/$basearch
    http://download3.clearsdn.com/centos/7.7.1908/updates/$basearch
    http://download4.clearsdn.com/centos/7.7.1908/updates/$basearch
    enabled=1
    gpgcheck=1
    exclude=shim-aa64-* shim-x64-* shim-ia32-* cloud-init-* shim-0* mokutil-* grub2-* centos-release centos-logos anaconda-* arpwatch cyrus-imapd-* debugmode initscripts iptables-* openldap-* ppp-* rp-pppoe
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever

    [clearos-centos-extras]
    name=CentOS-$releasever - Extras
    baseurl=http://download1.clearsdn.com/centos/7.7.1908/extras/$basearch
    http://download2.clearsdn.com/centos/7.7.1908/extras/$basearch
    http://download3.clearsdn.com/centos/7.7.1908/extras/$basearch
    http://download4.clearsdn.com/centos/7.7.1908/extras/$basearch
    enabled=1
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever

    [clearos-centosplus]
    name=CentOS-$releasever - Plus
    baseurl=http://download1.clearsdn.com/centos/7.7.1908/centosplus/$basearch
    http://download2.clearsdn.com/centos/7.7.1908/centosplus/$basearch
    http://download3.clearsdn.com/centos/7.7.1908/centosplus/$basearch
    http://download4.clearsdn.com/centos/7.7.1908/centosplus/$basearch
    enabled=1
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, October 26 2019, 05:44 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    @Marcel,
    Are you saying that if you have hit the python error then you cannot recover without reinstalling.
    If you do a fresh install, it now works?

    It is a bit odd, but it may be the case. I'll ask Dave if he wants to promote app-base.


    I did 2 tests!

    One install new ClearOS Community 7.7 iso / Stuck and has the following output when do a yum update:

    See this post


    One upgrade ClearOS Community 7.6 iso --> ClearOS Community 7.7 (with new app-base) / was successful.

    See this post

    Clear?
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, October 26 2019, 05:21 PM - #Permalink
    Resolved
    0 votes
    Dave has also successfully tested so we have released app-base-2.8.10-1.v7. It should sync to the repos within 2 hours.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, October 26 2019, 05:06 PM - #Permalink
    Resolved
    0 votes
    @Marcel,
    Are you saying that if you have hit the python error then you cannot recover without reinstalling.
    If you do a fresh install, it now works?

    It is a bit odd, but it may be the case. I'll ask Dave if he wants to promote app-base.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, October 26 2019, 03:31 PM - #Permalink
    Resolved
    0 votes
    Install of ClearOS 7.6 upgraded to ClearOS 7.7 (with the new app-base file from "clearos-updates-testing")


    -- Fresh install of ClearOS Community 7.6.

    -- Completed the wizard.

    -- Then after that go to the terminal:

    yum update app-base --enablerepo-clearos-updates-testing


    -- It successfully updated.


    ================================================================================================================================================================
    Package Arch Version Repository Size
    ================================================================================================================================================================
    Updating:
    app-base noarch 1:2.8.10-1.v7 clearos-updates-testing 31 k
    Updating for dependencies:
    app-base-core noarch 1:2.8.10-1.v7 clearos-updates-testing 455 k

    Transaction Summary
    ================================================================================================================================================================
    Upgrade 1 Package (+1 Dependent package)

    Total download size: 487 k
    Is this ok [y/d/N]: y
    Downloading packages:
    Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
    (1/2): app-base-2.8.10-1.v7.noarch.rpm | 31 kB 00:00:00
    (2/2): app-base-core-2.8.10-1.v7.noarch.rpm | 455 kB 00:00:00
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    Total 1.4 MB/s | 487 kB 00:00:00
    Running transaction check
    Running transaction test
    Transaction test succeeded
    Running transaction
    Updating : 1:app-base-core-2.8.10-1.v7.noarch 1/4
    Updating : 1:app-base-2.8.10-1.v7.noarch 2/4
    Cleanup : 1:app-base-2.8.9-1.v7.noarch 3/4
    Cleanup : 1:app-base-core-2.8.9-1.v7.noarch 4/4
    Verifying : 1:app-base-2.8.10-1.v7.noarch 1/4
    Verifying : 1:app-base-core-2.8.10-1.v7.noarch 2/4
    Verifying : 1:app-base-2.8.9-1.v7.noarch 3/4
    Verifying : 1:app-base-core-2.8.9-1.v7.noarch 4/4

    Updated:
    app-base.noarch 1:2.8.10-1.v7

    Dependency Updated:
    app-base-core.noarch 1:2.8.10-1.v7

    Complete!



    -- yum clean all

    [root@localhost ~]# yum clean all
    Failed to set locale, defaulting to C
    Loaded plugins: clearcenter-marketplace, fastestmirror
    ClearCenter Marketplace: fetching repositories...
    Cleaning repos: clearos clearos-centos clearos-centos-sclo-rh clearos-centos-updates clearos-centos-verified clearos-contribs clearos-epel-verified
    : clearos-fast-updates clearos-infra clearos-paid clearos-verified private-clearcenter-dyndns private-clearcenter-ids
    : private-clearcenter-kopano-basic private-clearcenter-verified-updates
    Cleaning up list of fastest mirrors
    Other repos take up 120 k of disk space (use --verbose for details)



    -- yum update

    -- cat /etc/clearos-release

    [root@localhost ~]# cat /etc/clearos-release 
    ClearOS release 7.7.1 (Final)


    -- Everything went following this order okay!
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, October 26 2019, 03:02 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    Dave did not think this would fix the python issue. He is expecting that it will go away when the paid versions get updated to 7.7.


    The issue bellow is on a Community 7.7 VM (fresh install) during the meeting.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, October 26 2019, 02:59 PM - #Permalink
    Resolved
    0 votes
    Ah, okay that is related to the Python issue..

    Nick Howitt wrote:

    I do not know what to expect from a fresh new 7.6 install, but I'd expect that to still be broken.


    I can test that ip you have a some time??
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, October 26 2019, 02:55 PM - #Permalink
    Resolved
    0 votes
    Dave did not think this would fix the python issue. He is expecting that it will go away when the paid versions get updated to 7.7. The fix to app-base just allowed existing systems to upgrade correctly. I do not know what to expect from a fresh new 7.6 install, but I'd expect that to still be broken.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, October 26 2019, 02:45 PM - #Permalink
    Resolved
    0 votes
    Nick,

    tried to update my 7.7 VM but it is still failing.

    ================================================================================================================================================================
    Package Arch Version Repository Size
    ================================================================================================================================================================
    Updating:
    app-base noarch 1:2.8.10-1.v7 clearos-updates-testing 31 k
    Updating for dependencies:
    app-base-core noarch 1:2.8.10-1.v7 clearos-updates-testing 455 k

    Transaction Summary
    ================================================================================================================================================================
    Upgrade 1 Package (+1 Dependent package)

    Total size: 487 k
    Is this ok [y/d/N]: y
    Downloading packages:
    Traceback (most recent call last):
    File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
    File "/usr/share/yum-cli/yummain.py", line 375, in user_main
    errcode = main(args)
    File "/usr/share/yum-cli/yummain.py", line 281, in main
    return_code = base.doTransaction()
    File "/usr/share/yum-cli/cli.py", line 683, in doTransaction
    problems = self.downloadPkgs(downloadpkgs, callback_total=self.download_callback_total_cb)
    File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 2633, in downloadPkgs
    self.plugins.run('postdownload', pkglist=pkglist, errors=errors)
    File "/usr/lib/python2.7/site-packages/yum/plugins.py", line 188, in run
    func(conduitcls(self, self.base, conf, **kwargs))
    File "/usr/lib/yum-plugins/clearcenter-marketplace.py", line 291, in postdownload_hook
    if pkg.repo in wc_repos:
    NameError: global name 'wc_repos' is not defined



    Version is correct (1:2.8.10-1.v7)
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, October 26 2019, 02:05 PM - #Permalink
    Resolved
    0 votes
    The recent update to app-base to fix the upgrade script did not go as planned. As a result, if you see things like "kernel-*" and "samba-*" in /etc/yum.repos.d/centos-unverified.repo or /etc/yum.repos.d/clearos-centos.repo then your upgrade wont work properly. We have just pushed a fix and it is syncing to the mirrors. If you upgrade has failed, please do a:
    yum update app-base --enablerepo-clearos-updates-testing
    yum clean all
    yum update
    You are looking for app-base-2.8.10-1.v7. If you do not get it, try waiting for a bit, do a "yum clean all" then try the update again. Most of the mirrors should be sync'd within a couple of hours.

    The aim is to reduce the "exclude" lines in /etc/yum.repos.d/centos-unverified.repo or /etc/yum.repos.d/clearos-centos.repo to:
    exclude=shim-aa64-* centos-release centos-logos anaconda-* arpwatch cloud-init-* cyrus-imapd-* debugmode grub2-* initscripts iptables-* mokutil-* openldap-* ppp-* rp-pppoe shim-ia32-* shim-x64-*
    The order of the parameters does not matter, just that they and only they exist after upgrading to 7.7.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, October 26 2019, 12:58 PM - #Permalink
    Resolved
    1 votes
    Anyone with the upgrade issue, please can you post your /etc/yum.repos.d/clearos-centos.repo file?
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, October 26 2019, 07:46 AM - #Permalink
    Resolved
    0 votes
    Dave has indicated there my be a workaround but it requires a fresh install. Can you do the install, then before you do the first-run wizard in the browser, drop to the command line (alt+f2 from the console or use PuTTy) then do a "yum update", ignoring the warnings about not being registered. Then you should be able to proceed with the first-run wizard.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, October 25 2019, 10:51 PM - #Permalink
    Resolved
    0 votes
    I’ve got the same issue trying to install new system, I’ve tried downloading older version iso it it seems even though it says it is the older ones it is not. Is this going to get fixed?
    The reply is currently minimized Show
  • Accepted Answer

    khvalera
    khvalera
    Offline
    Thursday, October 24 2019, 09:50 AM - #Permalink
    Resolved
    0 votes
    How to identify the problem, I wrote above. I am really looking forward to a decision.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 24 2019, 07:04 AM - #Permalink
    Resolved
    0 votes
    Dave is trying to replicate in his lab.
    The reply is currently minimized Show
Your Reply