Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button.  The answer will now appear with a checkmark.  Please be sure to always mark answers that resolve your issue as verified.  Your fellow Community members will appreciate it!  Learn more.

  • State Not Answered
  • Replies replies
    16
  • Subscribers subscribers
    7
  • Views views
    1392
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Updates unavailable after update to 7.0.1

Kobus Bennemeer

The SMG 7.0.0 appliance was updated to 7.0.1 following the online documentation, patch instructions and messages (including the prepare script) on the appliance.  It is not uncommon to see older servers having to update through versions to get to the latest.  However, updating to 7.0.1 seems to be a killjoy since no updates nor upgrades show afterwards.  I was expecting to see the 23 or 23.2 upgrades which were announced in the past few weeks. The appliance is registered with nu.novell.com, and re-registered, but the updates page is blank.

In an attempt to resolve, the update_v25.sh script was run again with the following restart of the smg service, as per suggestion in other threads. 

Info from zypper and rpm is posted below:

rblxsmg01:~ # zypper info smg
Refreshing service 'nu_novell_com'.
Loading repository data...
Reading installed packages...


Information for package smg:
----------------------------
Repository : SMG-7.0.1-Product
Name : smg
Version : 1.0.1-464.1
Arch : x86_64
Vendor : Micro Focus
Installed Size : 69.5 MiB
Installed : Yes
Status : up-to-date
Source package : smg-1.0.1-464.1.src
Upstream URL : http://www.microfocus.com
Summary : Secure Messaging Gateway package
Description :
Secure Messaging Gateway is used to provide scanning and routing capabilities.


rblxsmg01:~ # rpm -qa | grep smg
smg-1.0.1-464.1.x86_64
smg-va-overlay-2.2.1.3-43.1.noarch
smg-upgrade-7.0.1-45.1.noarch

Output from update_v25.sh

rblxsmg01:~ # bash /vastorage/smg/assets/updater/PostUpdate/update_scripts/update_v25.sh

Refreshing service 'nu_novell_com'.
Loading repository data...
Reading installed packages...
'libcap-progs' is already installed.
No update candidate for 'libcap-progs-2.26-4.6.1.x86_64'. The highest available version is already installed.
Resolving package dependencies...
Nothing to do.
ldconfig: /vastorage/smg/assets/bin/linux/x64/libamclient.so is not a symbolic link

Refreshing service 'nu_novell_com'.
Loading repository data...
Reading installed packages...
The selected package 'smg-0.0.0-0.x86_64' from repository 'Plain RPM files cache' has lower version than the installed one. Use 'zypper install --oldpackage smg-0.0.0-0.x86_64' to force installation of the package.
Resolving package dependencies...
Nothing to do.

Is there anything else to do, or rpms to load manually to facilitate an update to a more contemporary version?

  • 0

    The appliance shows OpenText branding, but the version feels wrong. In System Management portal, the version shows up as 7.0.1 rpm:1.0.1-464.1. 

  • 0   in reply to 

    Well, did you clear your cache or tried another browser or tried to use a private tab?

    Use "Verified Answers" if your problem/issue has been solved!

  • 0 in reply to   

    Yes on the browser care, but the versions are really confusing and I got lost among the RPM version (1.0.1-xx), appliance version (7.x.x) and the advertised (expected) product version (23.x). Does a reference document exist that matches these up?

    Edit - The Release log shows this, completely overlooked on my previous visits.  

  • 0   in reply to 

    This is mine 

    Use "Verified Answers" if your problem/issue has been solved!

  • 0   in reply to   

    What do you see if you run a command line "zypper patch" (without continue)?

    Command line patching is not really recommended.

    Use "Verified Answers" if your problem/issue has been solved!

  • 0 in reply to   

    Only "Nothing to do."

    rblxsmg01:~ # zypper patch
    Refreshing service 'nu_novell_com'.
    Loading repository data...
    Reading installed packages...
    Resolving package dependencies...
    Nothing to do.


    rblxsmg01:~ # zypper info smg
    Refreshing service 'nu_novell_com'.
    Loading repository data...
    Reading installed packages...


    Information for package smg:
    ----------------------------
    Repository : SMG-7.0.1-Product
    Name : smg
    Version : 1.0.1-464.1
    Arch : x86_64
    Vendor : Micro Focus
    Installed Size : 69.5 MiB
    Installed : Yes
    Status : up-to-date
    Source package : smg-1.0.1-464.1.src
    Upstream URL : http://www.microfocus.com
    Summary : Secure Messaging Gateway package
    Description :
    Secure Messaging Gateway is used to provide scanning and routing capabilities.

    The only explanation I can think of could a version file update that got missed somehow.

  • 0   in reply to 

    No, there should no be some 'miss' ... skipping an update is not a problem (sometimes even good luck Innocent)

    Did you open a case?

    (I have opened some cases around similar weird version numbers)

    Use "Verified Answers" if your problem/issue has been solved!

  • 0 in reply to   

    Yes, I have an open SR on this already.

    Do you recall the steps to rectify the versioning, e.g. re-install patches? It seems to be only a cosmetic feature, but is of course not sitting well when the client is told about better numbers.

  • 0   in reply to 

    My cases are still open and it seems to be a cosmetic mismatch as you are assuming. However we want to trust what we see.

    At one customer we did a zypper patch because the browser update looped without success. Nevertheless even the command line update did not help ...

    Use "Verified Answers" if your problem/issue has been solved!

  • 0 in reply to 

    I sent your current .pem and update channel keys to you via the case with support.  Hopefully those will help.  We do have  the new monthly update which should be out tomorrow and a new .ova that is due out next week or the week after.

    Pam

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.