[kolla-ansible][nova] nova upgrade failed from zed to antelope
Sylvain Bauza
sbauza at redhat.com
Wed Jun 21 08:06:43 UTC 2023
Le mer. 21 juin 2023 à 06:16, Satish Patel <satish.txt at gmail.com> a écrit :
> Folks,
>
> I'am upgrading zed to antelope using kolla-ansible and encount following
> error
>
> TASK [nova : Upgrade status check result]
> ************************************************************************************************************************************************************
> fatal: [kolla-infra-1]: FAILED! => {"changed": false, "msg": ["There was
> an upgrade status check failure!", "See the detail at
> https://docs.openstack.org/nova/latest/cli/nova-status.html#nova-status-checks
> "]}
> fatal: [kolla-infra-2]: FAILED! => {"changed": false, "msg": ["There was
> an upgrade status check failure!", "See the detail at
> https://docs.openstack.org/nova/latest/cli/nova-status.html#nova-status-checks
> "]}
> fatal: [kolla-infra-3]: FAILED! => {"changed": false, "msg": ["There was
> an upgrade status check failure!", "See the detail at
> https://docs.openstack.org/nova/latest/cli/nova-status.html#nova-status-checks
> "]}
>
>
> After running upgrade check command manually on nova-api container got
> following error
>
> (nova-api)[root at kolla-infra-2 /]# nova-status upgrade check
> Modules with known eventlet monkey patching issues were imported prior to
> eventlet monkey patching: urllib3. This warning can usually be ignored if
> the caller is only importing and not executing nova code.
> +---------------------------------------------------------------------+
> | Upgrade Check Results |
> +---------------------------------------------------------------------+
> | Check: Cells v2 |
> | Result: Success |
> | Details: None |
> +---------------------------------------------------------------------+
> | Check: Placement API |
> | Result: Success |
> | Details: None |
> +---------------------------------------------------------------------+
> | Check: Cinder API |
> | Result: Success |
> | Details: None |
> +---------------------------------------------------------------------+
> | Check: Policy File JSON to YAML Migration |
> | Result: Success |
> | Details: None |
> +---------------------------------------------------------------------+
> | Check: Older than N-1 computes |
> | Result: Success |
> | Details: None |
> +---------------------------------------------------------------------+
> | Check: hw_machine_type unset |
> | Result: Success |
> | Details: None |
> +---------------------------------------------------------------------+
> | Check: Service User Token Configuration |
> | Result: Failure |
> | Details: Service user token configuration is required for all Nova |
> | services. For more details see the following: https://docs |
> | .openstack.org/latest/nova/admin/configuration/service- |
> | user-token.html |
> +---------------------------------------------------------------------+
>
> Service user token reference to the following doc [1] . Do I need to
> configure token users in order to upgrade nova?
>
>
As you can read in the documentation below, yes indeed it became mandatory
by the 27.1.0 release.
In general, if you have a question about a new release, you can look at the
release notes by
https://docs.openstack.org/releasenotes/nova/2023.1.html#relnotes-27-1-0-stable-2023-1
and you'll see what is changed.
HTH,
-Sylvain
[1]
> https://docs.openstack.org/nova/latest/admin/configuration/service-user-token.html
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230621/837dd74b/attachment-0001.htm>
More information about the openstack-discuss
mailing list