[SOLVED] Problem after updating to 2.3.0

Questions about WAPT Server / Requests and help related to the WAPT server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
User avatar
guigeek
Messages: 147
Registration: Nov 21, 2017 - 9:21 p.m.

January 25, 2023 - 09:20

Hello everyone!
After updating to version 2.3.0, I'm having problems when changing maturity levels, for example, with the following errors:
CRITICAL Error uploading package ... Package filename / name is forbidden
CRITICAL merge_stripped_package failed EWaptForbiddden('Package filename / name is forbidden

Any idea what the problem is?
THANKS!
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

January 25, 2023 - 10:08

Hello Guillaume,
guigeek wrote: Jan 25, 2023 - 09:20 CRITICAL merge_stripped_package failed EWaptForbiddden('Package filename / name is forbidden
What is the name of the package?

Sincerely,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
User avatar
guigeek
Messages: 147
Registration: Nov 21, 2017 - 9:21 p.m.

January 25, 2023 - 12:51

I have the problem with waptupgrade for example:
;Package;Version;Maturity;Status;Message
;stm-waptupgrade;2.3.0.13438-43;PROD;ERROR;Upload error for stm-waptupgrade_2.3.0.13438-43_Change maturity to DEV_33995ddb-86fd-4a67-be97-16bbd7900019: Error on server:
EWaptForbiddden('Package filename / name is forbidden: stm-waptupgrade_2.3.0.13438-43_all_Change maturity to DEV_all_336e4baee8e892aa9725b8c0470b1fb6.wapt')
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

January 25, 2023 - 2:28 PM

Oops, there's a usability issue. In the maturity change window, you must select a maturity level from the combo box at the top; otherwise, the text "change maturity to" is selected.

This will be fixed in the next version. That said, it's important to choose the correct package maturity.

Regards,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
User avatar
guigeek
Messages: 147
Registration: Nov 21, 2017 - 9:21 p.m.

January 25, 2023 - 2:35 PM

Ah yes, my bad... weird, I don't think I did it before. I think production was selected by default when I changed the maturity level of a development package...
Or maybe I'm not fully awake yet... quite possible :lol:
. Thanks a lot!
User avatar
guigeek
Messages: 147
Registration: Nov 21, 2017 - 9:21 p.m.

January 25, 2023 - 2:38 PM

Oh no, I'm not crazy! ;)
I tried again with WaptUpgrade... if I switch from production to development... development is pre-selected, but I get an error. However, if I activate the maturity combobox to choose development, it works!
Thanks!
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

January 25, 2023 - 5:18 PM

This will be fixed in the next release. Thank you for reporting the bug. I'm marking this topic as resolved.

Regards,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Locked