|
| 1 | +--- |
| 2 | +author: meshcloud |
| 3 | +title: Release 2024.50.0 |
| 4 | +--- |
| 5 | + |
| 6 | +Release period: 2024-11-14 to 2024-11-20 |
| 7 | + |
| 8 | +This release includes the following issues: |
| 9 | +* Fix Tags Editing for Payment Method |
| 10 | +* Improved logging when GCP Cloud Function call fails |
| 11 | +* Remove erroneously updated Chargebacks and Usage Reports |
| 12 | +* Empty Recommended Building Blocks |
| 13 | +* Missing projects when adding tenants via marketplace |
| 14 | +* Improved error message for last Subscription owner removal |
| 15 | +<!--truncate--> |
| 16 | + |
| 17 | +## Ticket Details |
| 18 | +### Fix Tags Editing for Payment Method |
| 19 | +**Audience:** User<br> |
| 20 | + |
| 21 | +#### Description |
| 22 | +We identified and resolved an issue where the payment method tags could not |
| 23 | +be updated in the workspace area under the financial section. This issue has |
| 24 | +now been fixed, and all payment method tags can be updated as expected. |
| 25 | + |
| 26 | +### Improved logging when GCP Cloud Function call fails |
| 27 | +**Audience:** Operator<br> |
| 28 | + |
| 29 | +#### Description |
| 30 | +This adds the used parameter to the admin logs when a GCP cloud function call fails during |
| 31 | +a GCP tenant replication. |
| 32 | + |
| 33 | +### Remove erroneously updated Chargebacks and Usage Reports |
| 34 | +**Audience:** Customer, Partner<br> |
| 35 | + |
| 36 | +#### Description |
| 37 | +For customers that already use our newly revamped chargeback process, the |
| 38 | +previous release accidentally caused existing chargeback statements to be |
| 39 | +cancelled and replaced by new chargeback statements, even though there were |
| 40 | +no differences between the cancelled chargeback statement and the new |
| 41 | +chargeback statement. Only chargeback statements that included Azure cost |
| 42 | +items from the period of October 2024 were impacted. |
| 43 | +This has been fixed, such that the erroneously created chargeback statements |
| 44 | +are removed, and the corresponding chargeback statements that were previously |
| 45 | +shown as cancelled are reset to their original state. |
| 46 | +This essentially means that chargeback statements that were previously shown |
| 47 | +with a yellow "Updated" badge are now shown with the green "Finalized" badge |
| 48 | +again. The actual line items (charges) inside the chargeback statement are |
| 49 | +not in any way modified by this fix. |
| 50 | +The same applies to Tenant Usage Reports. |
| 51 | + |
| 52 | +### Empty Recommended Building Blocks |
| 53 | +**Audience:** User<br> |
| 54 | + |
| 55 | +#### Description |
| 56 | +Before this change it could happen that the recommended building blocks page during the tenant/project |
| 57 | +creation was empty in case no building blocks existed or all possible building blocks were already added. |
| 58 | +This has now been adjusted so that the step has been removed if no recommended building blocks are available. |
| 59 | + |
| 60 | +### Missing projects when adding tenants via marketplace |
| 61 | +**Audience:** User<br> |
| 62 | + |
| 63 | +#### Description |
| 64 | +Resolves an issue where projects were incorrectly displayed as ineligible for adding a tenant when initially selecting the tenant from the marketplace. |
| 65 | +Specifically, projects with previously deleted tenants of the same platform were incorrectly shown as unavailable for receiving a new tenant. |
| 66 | + |
| 67 | +### Improved error message for last Subscription owner removal |
| 68 | +**Audience:** Partner<br> |
| 69 | + |
| 70 | +#### Description |
| 71 | +Azure does not allow the last Owner of a Subscription to be removed. This is often an issue with |
| 72 | +Azure platform configurations. Since the replicator principal can not be used as the owner |
| 73 | +(doing so in the configuration had no effect), the error message was now improved to point this out. |
| 74 | + |
0 commit comments