Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

customised IBM MQ docker image (base) test failed for ". . ./make test-devserver" #386

Open
HarmanHM opened this issue Feb 13, 2020 · 3 comments

Comments

@HarmanHM
Copy link

When customising IBM MQ docker image (base) the test failed - ". . ./make test-devserver"

### Is there anything specific or any other variables that needs to be set?

I have listed the variables I have used. Also this test was run on a Linux Centos docker container.

Thank you

Linux Docker container Info:
[root@c1-lc docker]# hostnamectl
Static hostname: c1-lc
Icon name: computer-container
Chassis: container
Machine ID: 66f7f7a0a77d4988b3066f8616ee4a8c
Boot ID: 22e866e186d64baeb110a560ad36f028
Virtualization: docker
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 4.9.184-linuxkit
Architecture: x86-64

IBM MQ Image customisation Info:

export MQ_URL="https://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/messaging/mqadv/mqadv_dev914_linux_x86-64.tar.gz"
export REGISTRY_USER=;
export REGISTRY_PASS=;
export MQ_ARCHIVE_DEV=mqadv_dev914_linux_x86-64.tar.gz ;
export MQ_VERSION=9.1.4.0;
export MQ_TAG=$MQ_VERSION;
export MQ_IMAGE_DEVSERVER=labmqcd;
export MQM_UID=100803;
export MQ_PACKAGES="MQSeriesRuntime-.rpm
MQSeriesServer-
.rpm
MQSeriesJava*.rpm
MQSeriesJRE*.rpm
MQSeriesGSKit*.rpm
MQSeriesMsg*.rpm
MQSeriesSamples*.rpm
MQSeriesWeb*.rpm
MQSeriesAMS*.rpm
MQSeriesSDK*.rpm
MQSeriesSFBridge*.rpm
MQSeriesBCBridge*.rpm
MQSeriesAMQP*.rpm
MQSeriesFTBase*.rpm
MQSeriesFTTools*.rpm
MQSeriesFTAgent*.rpm
MQSeriesFTLogger*.rpm
MQSeriesFTService*.rpm
MQSeriesExplorer*.rpm
MQSeriesXRService*.rpm
MQSeriesMan*.rpm
MQSeriesClient*.rpm";
/usr/bin/make devserver

NOTE: "/usr/bin/make devserver" is composed of/includes following make commands;
"/usr/bin/make devserver" = build-devserver + build-devjmstest + test-devserver

Error Info:
Problem / error:
customised IBM MQ docker image (base) test failed for ". . ./make test-devserver";
--- FAIL: TestMultiInstanceStartStop (85.07s)
--- FAIL: TestMultiInstanceContainerStop (81.57s)
Relevant error entries extracted from the output log …

cd test/docker && TEST_IMAGE=labmqcd:9.1.4 EXPECTED_LICENSE=Developer DEV_JMS_IMAGE=mq-dev-jms-test IBMJRE=true go test -parallel 2 -tags mqdev
--- FAIL: TestMultiInstanceStartStop (85.07s) ---> test script = mq-container/test/docker/mq_multi_instance_test.go
. . .
2020-01-26T18:04:00.966Z Creating queue manager QM1
2020-01-26T18:04:00.966Z Starting web server
2020-01-26T18:04:01.085Z Created standby queue manager
2020-01-26T18:04:01.172Z Starting queue manager
2020-01-26T18:04:01.543Z Error 43 starting queue manager: IBM MQ queue manager 'QM1' starting.
The queue manager is associated with installation 'Installation1'.
IBM MQ queue manager 'QM1' is already running elsewhere. It does not permit
standby instances.

    2020-01-26T18:04:01.544Z /usr/bin/strmqm: exit status 43
docker_api_test_util.go:248: Termination message: /usr/bin/strmqm: exit status 43

. . .
No commands have a syntax error.
All valid MQSC commands were processed.
2020-01-26T18:04:54.046Z Metrics are disabled
2020-01-26T18:04:57.359Z Signal received: terminated
2020-01-26T18:04:57.360Z Stopping queue manager
2020-01-26T18:04:58.064Z Error 77 stopping queue manager: AMQ7276E: IBM MQ queue manager cannot switch over.
. . .
--- FAIL: TestMultiInstanceContainerStop (81.57s) ---> test script = mq-container/test/docker/mq_multi_instance_test.go
. . .
2020-01-26T18:05:19.791Z MQ license: Developer
2020-01-26T18:05:22.563Z Creating queue manager QM1
2020-01-26T18:05:22.565Z Starting web server
2020-01-26T18:05:22.710Z Created standby queue manager
2020-01-26T18:05:22.826Z Starting queue manager
2020-01-26T18:05:23.185Z Error 43 starting queue manager: IBM MQ queue manager 'QM1' starting.
The queue manager is associated with installation 'Installation1'.
IBM MQ queue manager 'QM1' is already running elsewhere. It does not permit
standby instances.

    2020-01-26T18:05:23.186Z /usr/bin/strmqm: exit status 43
docker_api_test_util.go:248: Termination message: /usr/bin/strmqm: exit status 43

. . .
All valid MQSC commands were processed.
2020-01-26T18:06:17.979Z Metrics are disabled
2020-01-26T18:06:21.991Z Signal received: terminated
2020-01-26T18:06:21.991Z Stopping queue manager
2020-01-26T18:06:22.601Z Error 77 stopping queue manager: AMQ7276E: IBM MQ queue manager cannot switch over.
. . .
exit status 2
FAIL mq-container-9.1.4/test/docker 600.049s
make: *** [test-devserver] Error 1

@arthurbarr
Copy link
Contributor

strmqm ends with an exit status of 43 to indicate that the queue manager does not permit standby instances (docs). Have you changed any of the options used by strmqm in the Go code? Also, it's worth checking that the tests pass if you don't make any modifications (i.e. a clean extract of the source), just to rule out any environment problems (like an issue with the filesystem you're using).

@HarmanHM
Copy link
Author

I have not changed any of the options used by strmqm in the Go code.
This test uses a clean extract of the source, i.e. asis.

I want to ensure that after customising the MQ image it passes all the IBM supplied test, asis
".../make test-unit" runs fine, no problems

@HarmanHM
Copy link
Author

strmqm ends with an exit status of 43 to indicate that the queue manager does not permit standby instances (docs). Have you changed any of the options used by strmqm in the Go code? Also, it's worth checking that the tests pass if you don't make any modifications (i.e. a clean extract of the source), just to rule out any environment problems (like an issue with the filesystem you're using).

Any more update on this issue?
".../make test-devserver" FAILS - I am trying to run the test asis

mirskifa pushed a commit that referenced this issue Feb 16, 2023
* configuing ws

* configuing ws for path exlude
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants