Open Source package manager fails to update, install, or remove available packages

[John Callahan]

Having post-install issues with the open source package manager provided with iACS 1.1.8.0 on an IBM POWER8 server running i 7.3 TR4

Install process seems to complete successfully; however, the app with a "TypeError: tuple indices must be integers, not str" error message while attempting to Resolve Dependencies

The iACS Open Source package manager seems to be working on our other IBMi server running i7.2 TR8.

package manager reports python2 version as 2.7.14-0 on both servers

There are some differences between the two servers post install. The i7.3 server reports yum 3.4.3-6 as installed with yum 3.4.3-13 @ibm The i7.2 server reports yum 3.4.3-9 as installed

I have deleted the /QOpensys/pkgs directory and its subdirectories, and reinstalled the package manager on the i7.3 server and get the same situation: install reports as successfully completed, package manager unusable, yum version different that install on i7.2 server.

[Aaron Bartell]

@kadler or @ThePrez, any idea on this one?

[Jesse G]

Yikes, not sure. I have tried several permutations on my IBM i 7.3 machine, have not been able to recreate. Can you share your /QOpenSys/var/log/yum.log file?

If you did the "fresh" install with ACS and it thinks you have yum 3.4.3-13 installed, that might imply you have an out-of-sync yum database somehow. Possibly, the bootstrap was loaded after yum was already installed. A clean install after deleting these directories via rm -rf might help, but I can't guarantee since the root cause is still unknown:

• /QOpenSys/var/cache/yum
• /QOpenSys/var/lib/yum
• /QOpenSys/etc/yum
• /QOpenSys/pkgs

[Kevin Adler]

I'd recommend also removing /QOpenSys/var/lib/rpm

[John Callahan]

Cleared all the suggested directories * /QOpenSys/var/cache/yum * /QOpenSys/var/lib/yum * /QOpenSys/etc/yum * /QOpenSys/pkgs * /QOpenSys/var/lib/rpm

Reinstalled using iACS, now working as expected- able to install, update, and remove packages via the Open Source package manager.

Thanks for the suggestions.

Root cause may have been a failed earlier attempt to install using the manual "beta" instructions using Run SQL Scripts under a user profile with insufficient special authorities.

[Jesse G]

Marking this as resolved. IBM will open an internal issue to work on further investigation of use cases such as this. Thanks!