Magnum: invalid format of client version
Creating a VM from the CLI works fine, as does the heat stack. In both cases using the same image, flavour and keypair/
Alexander Dibbo - Cloud Architect / Cloud Operations Group Leader
For STFC Cloud Documentation visit https://stfc-cloud-docs.readthedocs.io<https://stfc-cloud-docs.readthedocs.io/>
To raise a support ticket with the cloud team please email cloud-support at gridpp.rl.ac.uk<mailto:cloud-support at gridpp.rl.ac.uk>
To receive notifications about the service please subscribe to our mailing list at: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=STFC-CLOUD
To receive fast notifications or to discuss usage of the cloud please join our Slack: https://stfc-cloud.slack.com/
From: Bharat Kunwar <bharat at stackhpc.com>
Sent: 22 July 2020 15:04
To: Dibbo, Alexander (STFC,RAL,SC) <alexander.dibbo at stfc.ac.uk>
Cc: openstack-discuss at lists.openstack.org
Subject: Re: Magnum: invalid format of client version
Looks like the following errors are being emitted from Nova via Heat.
Would you mind ensuring that you are able to spin up servers using nova CLI and then creating a simple heat stack via heat CLI.
On 21 Jul 2020, at 13:53, Alexander Dibbo - UKRI STFC <alexander.dibbo at stfc.ac.uk<mailto:alexander.dibbo at stfc.ac.uk>> wrote:
Jul 17 14:08:24 host-172-16-103-43 magnum-conductor: 2020-07-17 14:08:24.942 6251 ERROR oslo_messaging.rpc.server InvalidParameterValue: ERROR: UnsupportedVersion: : resources.worker_nodes_server_group: : Invalid format of client version ''. Expected format 'X.Y', where X is a major part and Y is a minor part of version.
This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments that are not related directly to UKRI business are solely those of the author and do not represent the views of UKRI.
-------------- next part --------------
An HTML attachment was scrubbed...