Page 1 of 1

WAPT Console Migration

Published: January 15, 2020 - 10:22 AM
by djedje68
Good morning,

I had to migrate my WAPT console to another computer.
Since then, I haven't been able to complete the installations. I get the following error:

Code: Select all

Installing 724B117C-76F4-4BD3-94CA-CCB43094EC59(=4)

Installing 724B117C-76F4-4BD3-94CA-CCB43094EC59(=4)

Traceback (most recent call last):
  File "C:\Program Files (x86)\wapt\waptservice\service.py", line 1711, in run
    self.running_task.run()
  File "C:\Program Files (x86)\wapt\waptservice\waptservice_common.py", line 559, in run
    self._run()
  File "C:\Program Files (x86)\wapt\waptservice\waptservice_common.py", line 1017, in _run
    self.result.get('errors',[])))
Exception: Erreur lors de l'installation de [u'724B117C-76F4-4BD3-94CA-CCB43094EC59(=4)']: erreurs dans les paquets [[PackageRequest(package=u'724B117C-76F4-4BD3-94CA-CCB43094EC59',version=(Version('4.0.0.0'), None),architectures=[u'x64'],locales=['fr'],maturities=[u'PROD'],min_os_version=Version('10.0.18362'),max_os_version=Version('10.0.18362')), PackageEntry(u'724B117C-76F4-4BD3-94CA-CCB43094EC59',u'4' ), u'Traceback (most recent call last):\n  File "C:\\Program Files (x86)\\wapt\\common.py", line 4855, in install\n    force=force\n  File "C:\\Program Files (x86)\\wapt\\common.py", line 3934, in install_wapt\n    raise e\nEWaptUnavailablePackage: Missing dependencies: xxxx-7zip\n']]

Exception: Erreur lors de l'installation de [u'724B117C-76F4-4BD3-94CA-CCB43094EC59(=4)']: erreurs dans les paquets [[PackageRequest(package=u'724B117C-76F4-4BD3-94CA-CCB43094EC59',version=(Version('4.0.0.0'), None),architectures=[u'x64'],locales=['fr'],maturities=[u'PROD'],min_os_version=Version('10.0.18362'),max_os_version=Version('10.0.18362')), PackageEntry(u'724B117C-76F4-4BD3-94CA-CCB43094EC59',u'4' ), u'Traceback (most recent call last):\n  File "C:\\Program Files (x86)\\wapt\\common.py", line 4855, in install\n    force=force\n  File "C:\\Program Files (x86)\\wapt\\common.py", line 3934, in install_wapt\n    raise e\nEWaptUnavailablePackage: Missing dependencies: xxxx-7zip\n']]
Traceback (most recent call last):
  File "C:\Program Files (x86)\wapt\waptservice\service.py", line 1711, in run
    self.running_task.run()
  File "C:\Program Files (x86)\wapt\waptservice\waptservice_common.py", line 559, in run
    self._run()
  File "C:\Program Files (x86)\wapt\waptservice\waptservice_common.py", line 1017, in _run
    self.result.get('errors',[])))
Exception: Erreur lors de l'installation de [u'724B117C-76F4-4BD3-94CA-CCB43094EC59(=4)']: erreurs dans les paquets [[PackageRequest(package=u'724B117C-76F4-4BD3-94CA-CCB43094EC59',version=(Version('4.0.0.0'), None),architectures=[u'x64'],locales=['fr'],maturities=[u'PROD'],min_os_version=Version('10.0.18362'),max_os_version=Version('10.0.18362')), PackageEntry(u'724B117C-76F4-4BD3-94CA-CCB43094EC59',u'4' ), u'Traceback (most recent call last):\n  File "C:\\Program Files (x86)\\wapt\\common.py", line 4855, in install\n    force=force\n  File "C:\\Program Files (x86)\\wapt\\common.py", line 3934, in install_wapt\n    raise e\nEWaptUnavailablePackage: Missing dependencies: xxxx-7zip\n']]
I don't really know how to do it, how to migrate, etc...

I regenerated a new agent, etc... but it doesn't work.

I missed something but I don't know what.

Thank you in advance

Re: WAPT Console Migration

Published: January 15, 2020 - 10:55 AM
by sfonteneau
Can you verify that 7zip is in the correct architecture for your machine in the private repository?

Re: WAPT Console Migration

Published: January 15, 2020 - 10:57 AM
by djedje68
Hello,

Thank you for the feedback,

I checked, it's OK.

Re: WAPT Console Migration

Published: January 15, 2020 - 11:22 AM
by sfonteneau
The WAPT agent reports

`raise e\nEWaptUnavailablePackage: Missing dependencies: xxxx-7zip`.

This means it's being asked to install 7-Zip, but the 7-Zip package is not found for the machine.

Several scenarios are possible:

- The package is not available for the machine's architecture

- The package's minimum and maximum OS versions are not compatible with the machine

. - The package's language is not compatible with the machine's language.

- The package's maturity level is not available for this machine.

- The WAPT package is not signed with a key accepted by the machine.

When you "Migrate console," did you keep the existing key and not generate a new one?

Re: WAPT Console Migration

Published: January 15, 2020 - 11:37 AM
by djedje68
Several scenarios are possible:

- The package is not available for the machine's architecture.

- The package's minimum and maximum OS versions are not compatible with the machine.

- The package's language is not compatible with the machine's language.

- The package's maturity level is not available for this machine.

- The WAPT package is not signed with a key accepted by the machine.

When you selected "Migrate console," did you keep the existing key and not generate a new one?
I generated a new key, but I still have the old key... Do I just need to move it to my "private" folder?
I think it's really a question of the key because the rest is fine.

Re: WAPT Console Migration

Published: January 15, 2020 - 1:01 PM
by djedje68
I can only install packages I've recently imported.
I have to remove, for example, 7-Zip, Firefox, etc., from my private repository, re-import them, and then the installation works.

Where did I go wrong?

Re: WAPT Console Migration

Published: January 15, 2020 - 2:32 PM
by vcardon
djedje68 wrote: Jan 15, 2020 - 1:01 PM I can only install packages I've recently imported.
I have to delete, for example, 7zip, Firefox, etc. from my private repository, re-import them, and then the installation works.

Where did I go wrong?
As you wrote, you regenerated a key. I imagine that you then somehow deployed the new certificate to your network and removed the old certificate (perhaps deployed an update to your WAPT agents?).

Therefore, the new packages signed with the new key are deployed and installed because the agent recognizes the new key.

Consequently, older packages in your repository, signed with the old key, continue to be served by the server because updates are based on version numbers, but these upgrades are no longer triggered because the execution of a package takes place after the certificate has been properly verified.

This operation is compliant.

WAPT still works really well :D

Sincerely.

Vincent