** Description changed:

+ ************* SRU TEMPLATE AT THE BOTTOM ************
+ 
  OpenStack/Horizon: Yoga
  
  After creating an instance
  
  # openstack server show test2 | egrep 'flavor| id '
  | flavor                              | gen.medium (gen.medium)
  | id                                  | 95ce0962-64b2-4e38-9af7-af2932c9f192
  # openstack flavor show gen.medium | grep flavor-access
  | os-flavor-access:is_public | True
  
  In Horizon:
  This flavor is shown on (Instances) view for the project as both Admin/User 
correctly (/project/instances/):
  
- Instance Name Image Name           IP Address    Flavor       Key Pair        
Status          Availability Zone       
+ Instance Name Image Name           IP Address    Flavor       Key Pair        
Status          Availability Zone
  test2         Ubuntu 22.04 (Jammy) 192.168.0.237 gen.medium   key1            
Active          nova    None    Running 22 minutes
  
  However when going to the Instance detail view 
(/project/instances/95ce0962-64b2-4e38-9af7-af2932c9f192/)
  The Specs category shows:
  
  Specs
  Flavor Not available
  
  Let me know if any additional info can be provided to assist with 
troubleshooting.
  Patches from https://bugs.launchpad.net/horizon/+bug/1940834 appear to 
already be present.
  This appears to be mainly a visual/cosmetic issue in Instance detail view.
+ 
+ 
+ ===============
+ SRU DESCRIPTION
+ ===============
+ 
+ [Impact]
+ 
+ This issue affects the user experience when trying to see the flavor
+ information of an instance through the dashboard. The flavor name can
+ still be seen in the instance list though.
+ 
+ [Test case]
+ 
+ 1. Deploy openstack with dashboard
+ 
+ 2. login and create an instance
+ 
+ 3. check that the instance is displayed in the list and the correct
+ flavor is displayed
+ 
+ 4. click the instance to open the instance detail page, and check that
+ the flavor field says "not available"
+ 
+ 5. install the fixed package
+ 
+ 6. reload the dashboard and navigate to the instance detail page again,
+ the flavor field should show the correct flavor now
+ 
+ [Where problems could occur]
+ 
+ The code only modifies the instance detail page, so if there is any
+ problem with the modification, the instance page detail page will fail
+ to load. The package will have to be reverted to restore the previous
+ functionality.
+ 
+ [Other Info]
+ 
+ None

** Also affects: horizon (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: horizon (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: horizon (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Changed in: horizon (Ubuntu)
       Status: New => Fix Released

** Changed in: horizon (Ubuntu Jammy)
       Status: New => Fix Released

** Also affects: cloud-archive
   Importance: Undecided
       Status: New

** Also affects: cloud-archive/ussuri
   Importance: Undecided
       Status: New

** Changed in: cloud-archive
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/2011998

Title:
  [SRU] Flavor: Not Available on Instance View

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive ussuri series:
  New
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Focal:
  New
Status in horizon source package in Jammy:
  Fix Released

Bug description:
  ************* SRU TEMPLATE AT THE BOTTOM ************

  OpenStack/Horizon: Yoga

  After creating an instance

  # openstack server show test2 | egrep 'flavor| id '
  | flavor                              | gen.medium (gen.medium)
  | id                                  | 95ce0962-64b2-4e38-9af7-af2932c9f192
  # openstack flavor show gen.medium | grep flavor-access
  | os-flavor-access:is_public | True

  In Horizon:
  This flavor is shown on (Instances) view for the project as both Admin/User 
correctly (/project/instances/):

  Instance Name Image Name           IP Address    Flavor       Key Pair        
Status          Availability Zone
  test2         Ubuntu 22.04 (Jammy) 192.168.0.237 gen.medium   key1            
Active          nova    None    Running 22 minutes

  However when going to the Instance detail view 
(/project/instances/95ce0962-64b2-4e38-9af7-af2932c9f192/)
  The Specs category shows:

  Specs
  Flavor Not available

  Let me know if any additional info can be provided to assist with 
troubleshooting.
  Patches from https://bugs.launchpad.net/horizon/+bug/1940834 appear to 
already be present.
  This appears to be mainly a visual/cosmetic issue in Instance detail view.

  
  ===============
  SRU DESCRIPTION
  ===============

  [Impact]

  This issue affects the user experience when trying to see the flavor
  information of an instance through the dashboard. The flavor name can
  still be seen in the instance list though.

  [Test case]

  1. Deploy openstack with dashboard

  2. login and create an instance

  3. check that the instance is displayed in the list and the correct
  flavor is displayed

  4. click the instance to open the instance detail page, and check that
  the flavor field says "not available"

  5. install the fixed package

  6. reload the dashboard and navigate to the instance detail page
  again, the flavor field should show the correct flavor now

  [Where problems could occur]

  The code only modifies the instance detail page, so if there is any
  problem with the modification, the instance page detail page will fail
  to load. The package will have to be reverted to restore the previous
  functionality.

  [Other Info]

  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2011998/+subscriptions


-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to