Wikis - Page

Failed to upgrade Octane 16.0.200 from 16.0.100

NEW_ALM12

0 Likes

over 2 years ago

Non-exclusive post upgrade job (ExistingFieldsBecomeTrendableWorker, jobId=4026) started on shared space 4002
2021-12-16 09:11:57 INFO | Exclusive post upgrade job (ElasticMaintenancePostUpgradeWorker, jobId=4021) cannot start on shared space 4002 because there are 8 non-exclusive jobs that have never run (["Add a business rule for tests with ALM origin.", "Fix user activation and relation to SP in site schema", "Remove stale fields from email template", "Run steps migration", "Sync modified site user details to no modified sharedspace users", "Sync new searchable fields to elastic", "Sync new trendable entities to elastic", "Sync new trendable fields to elastic"])
2021-12-16 09:11:57 WARN | Found new trendable fields: {test_automated=[item_origin], test_suite=[item_origin], scenario_test=[item_origin], gherkin_test=[item_origin], test_manual=[item_origin]}
2021-12-16 09:11:57 WARN | Processing workspace 10002

Non-exclusive post upgrade job (AddModelBasedTestRulesPostUpgradeWorker, jobId=6019) started on shared space 1001

2021-12-16 15:48:52 ERROR | Non-exclusive post upgrade job (AddModelBasedTestRulesPostUpgradeWorker, jobId=6019) failed on shared space 1001
com.hp.mqm.ps.businessrules.utils.JsonParsingException: Expected a json object with one expression field exactly.
at com.hp.mqm.ps.businessrules.utils.BRSerializationUtil.getExpressionSingleFieldName(BRSerializationUtil.java:239) ~[mqm-ps-business-rules-impl-16.0.200.101.jar:?]
at com.hp.mqm.ps.businessrules.utils.BRSerializationUtil.jsonToExpression(BRSerializationUtil.java:80) ~[mqm-ps-business-rules-impl-16.0.200.101.jar:?]
at com.hp.mqm.ps.businessrules.serialization.RestBRExpressionSerializerImpl.deserialize(RestBRExpressionSerializerImpl.java:18) ~[mqm-ps-business-rules-impl-16.0.200.101.jar:?]
at com.hp.mqm.ps.businessrules.serialization.RestBRExpressionSerializerImpl.deserialize(RestBRExpressionSerializerImpl.java:10) ~[mqm-ps-business-rules-impl-16.0.200.101.jar:?]
at com.hp.mqm.ps.businessrules.serialization.BROperationSerializerImpl.jsonToOperation(BROperationSerializerImpl.java:95) ~[mqm-ps-business-rules-impl-16.0.200.101.jar:?]
at com.hp.mqm.ps.businessrules.serialization.BROperationSerializerImpl.deserialize(BROperationSerializerImpl.java:32) ~[mqm-ps-business-rules-impl-16.0.200.101.jar:?]
at com.hp.mqm.ps.businessrules.serialization.BROperationSerializerImpl.deserialize(BROperationSerializerImpl.java:25) ~[mqm-ps-business-rules-impl-16.0.200.101.jar:?]
at com.hp.mqm.ps.businessrules.upgraders.UpdateVanillaBusinessRulesBaseUpgradeWorker.operationDeserialize(UpdateVanillaBusinessRulesBaseUpgradeWorker.java:198) ~[mqm-ps-business-rules-impl-16.0.200.101.jar:?]
at com.hp.mqm.ps.businessrules.upgraders.AddModelBasedTestRulesPostUpgradeWorker.getNewRules(AddModelBasedTestRulesPostUpgradeWorker.java:25) ~[mqm-ps-business-rules-impl-16.0.200.101.jar:?]
at com.hp.mqm.ps.businessrules.upgraders.UpdateVanillaBusinessRulesBaseUpgradeWorker.lambda$AddRules$4(UpdateVanillaBusinessRulesBaseUpgradeWorker.java:93) ~[mqm-ps-business-rules-impl-16.0.200.101.jar:?]
at com.hp.mqm.ps.platformservices.context.GenericContextUtils.workWithContext(GenericContextUtils.java:358) ~[mqm-ps-platform-services-api-16.0.200.101.jar:?]
at com.hp.mqm.ps.platformservices.context.GenericContextUtils.workWithContext(GenericContextUtils.java:339) ~[mqm-ps-platform-services-api-16.0.200.101.jar:?]
at com.hp.mqm.ps.platformservices.context.GenericContextUtils.workWithWorkspace(GenericContextUtils.java:112) ~[mqm-ps-platform-services-api-16.0.200.101.jar:?]
at com.hp.mqm.ps.businessrules.upgraders.UpdateVanillaBusinessRulesBaseUpgradeWorker.AddRules(UpdateVanillaBusinessRulesBaseUpgradeWorker.java:86) ~[mqm-ps-business-rules-impl-16.0.200.101.jar:?]
at com.hp.mqm.ps.businessrules.upgraders.UpdateVanillaBusinessRulesBaseUpgradeWorker.lambda$doPostUpgrade$1(UpdateVanillaBusinessRulesBaseUpgradeWorker.java:77) ~[mqm-ps-business-rules-impl-16.0.200.101.jar:?]

Tags:

AddModelBasedTestRulesPostUpgradeWorker

MbtFrameworkNodeListUpgrader

Labels:

Education-Training

Support Tips/Support Tips/Support Tips/Knowledge Docss

Support Tips/Support Tips/Knowledge Docs

Support Tips/Knowledge Docs

Comment List

felixturle over 2 years ago in reply to davidvince

Hi David,

Can you share more details with us?

Can you drop an email with octane.log to felix.turle@microfocus.com & alexandru-catalin.costea@microfocus.com.

Also, please open a support ticket for this issue.

Thanks,

Felix
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel
davidvince over 2 years ago

We have the same problem. Is there a solution?
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel
NEW_ALM12 over 2 years ago in reply to NEW_ALM12

Here is a syntax for indices mapping but remember you will need a .jason file in order to run this cmd.

curl -XPUT 'http://localhost:9200/mqm_95o4e04zg45nzul5zlo5rvnq0_event_store/_mapping' -H 'Content-Type: application/json' -d @event_store_mappings.json
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel
NEW_ALM12 over 2 years ago in reply to Jesper Halden

I suspect 2 reasons for the fail due to ES.

Make ES disk space has free space.

Check your wrapper.log if you have below line. if you donot have it, add it.

wrapper.java.additional.44=-Ddisable.validator.elasticsearch_nodes_free_space=true

Make sure you don’t already have a JVM number “44” if you do just use some unique number

Then bounce Octane.

Then, it complaining about ES indices mapping. I had that issue and got a fix from R&D team. They will basically give your the mapping Jason file and run a curl cmd with PUT action.
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel
Jesper Halden over 2 years ago in reply to Jesper Halden

Elasticsearch exception [type=cluster_block_exception, reason=index [mqm_95o4e04zg45nzul5zlo5rvnq0_event_store_reindex_6_index] blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];]
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel
Jesper Halden over 2 years ago in reply to Jesper Halden

Elastic update mappings request failed for alias=mqm_95o4e04zg45nzul5zlo5rvnq0_event_store; mapping={"dynamic":"strict","properties":{"version":{"type":"keyword","index":true,"doc_values":"false"},"migrated_audit_log_id":{"type":"long","index":true},"action":{"type":"keyword","index":true},"entity_id":{"type":"keyword","index":true},"entity_physical_id":{"type":"long","index":false},"entity_type":{"type":"keyword","index":true},"supports_history":{"type":"boolean","index":true},"timestamp":{"type":"date","format":"yyyy-MM-dd'T'HH:mm:ss.SSS"},"user_id":{"type":"long","index":true},"unknown_user_name":{"type":"keyword","index":false,"doc_values":"false"},"session_id":{"type":"keyword","index":true},"workspace_id":{"type":"long"},"request_id":{"type":"keyword","index":true},"change_set":{"type":"nested","properties":{"field_name":{"type":"keyword","index":true,"doc_values":"false"},"field_type":{"type":"keyword","index":false,"doc_values":"false"},"udf_logical_name":{"type":"keyword","index":false,"doc_values":"false"},"custom_data":{"enabled":false},"value":{"type":"keyword","index":false,"doc_values":"false","ignore_above":"150"},"value_id":{"type":"long","index":false},"old_value":{"type":"keyword","index":false,"doc_values":"false","ignore_above":"150"},"old_value_id":{"type":"long","index":false},"mode":{"type":"keyword","index":false,"doc_values":"false"},"ref_entity_type":{"type":"keyword","index":false,"doc_values":"false"},"rule_changer_id":{"type":"keyword","index":false,"doc_values":"false"},"bizRuleChangerId":{"type":"keyword","index":false,"doc_values":"false"}}}}}
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel
Jesper Halden over 2 years ago in reply to Jesper Halden

Didn't help - still geeting Suspended mode - Failed to update elastic schema

This is just occuring for our main Space....other spaces has upgraded successfully
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel
Jesper Halden over 2 years ago in reply to NEW_ALM12

thanks for quick reply - we will try that:)

We did set false for UPG_MbtFrameworkNodeListUpgrader_ENABLE
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel
NEW_ALM12 over 2 years ago in reply to Jesper Halden

Did you change the flag to false for UPG_MbtFrameworkNodeListUpgrader_ENABLE?

Also what does the octane.log and app.log says?

I would only change flag to false from true (default value) for UPG_AddPhaseAndTransitionForModelBasedTest_ENABLE and keep as default vlaue for other 3 parameters.

After that make sure to restart octane service.
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel
Jesper Halden over 2 years ago

when searching for model test - 4 parameters appear.......we changed all 4 to false but didn't help:(

Any other ideas?
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel

Recommended

Menu

ALM Octane Tips

Failed to upgrade Octane 16.0.200 from 16.0.100

Tags:

Labels:

Resources