'can_set_password' ignored in the new launch instance experience

[massimo.sgaravatto]

In the legacy launch instance experience users can set the admin password of the instance, if 'can_set_password' is true in local_settings.

In the new launch instance experience this is not possible

Environment: OpenStack Mitaka on CentOS7

[Rob Cresswell (robcresswell-deactivatedaccount)]

Why was this set to Fix Released with no linked patch? Please link relevant content so the bug team can do their jobs.

[Robert T (robetus)]

This has not been fixed in Ocata, just confirmed by install.

[Mathieu Gagné (mgagne)]

Suppose someone wants to work on this feature. In which step should the password field be located?

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/492546

[Akihiro Motoki (amotoki)]

This is still valid, but mitaka is EOL and newton now receives critical and security fixes only, so bug tags have been updated.

[Dmitriy Rabotyagov (noonedeadpunk)]

Hi,

I have exactly the same problem in the Pike release. Moreover, requires_keypair doesn't work in the new interface as well. I've found, that /usr/share/openstack-dashboard/openstack_dashboard/dashboards/project/static/dashboard/project/workflow/launch-instance/keypair/keypair.controller.js should be responsible for redering this menu. On lines 99-101 there are lines, which should retrieve from configuration:

settingsService.getSetting(
  'OPENSTACK_HYPERVISOR_FEATURES.requires_keypair'
).then(setKeypairRequired);

So we've tried to debug function setKeypairRequired() by adding alert(setting) in it, and setting was equal to True. Nevertheless option is not marked as required one.

Thanks in advance.

[Akihiro Motoki (amotoki)]

This bug is about can_set_password. 'requires_keypairs' should be handled as a separate bug.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Ivan Kolodyazhny (<email address hidden>) on branch: master
Review: https://review.openstack.org/492546
Reason: This review is > 4 months without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

[Akihiro Motoki (amotoki)]

It was fixed by https://review.opendev.org/c/openstack/horizon/+/770528

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/horizon 19.1.0 release.