@Corey, you're mentioning that it works on instance with id 049f.... but it was in SHUTOFF state (thus it was working), but if you'd start the instance:
$ os server start 049f76c6-3f6d-4299-b332-bf4c264b8741
$ os server image create --wait 049f76c6-3f6d-4299-b332-bf4c264b8741
HTTP 404 Not Found: No image found with ID 9b5dd242-9d46-41de-955e-5ff97ef50d28
@Corey, you're mentioning that it works on instance with id 049f.... but it was in SHUTOFF state (thus it was working), but if you'd start the instance:
$ os server list
| 049f76c6- 3f6d-4299- b332-bf4c264b87 41 | ubuntu-tests2 | SHUTOFF | internal=10.0.0.30 | ubuntu- bionic- cloudimg | m1.medium | 7426-4ad0- 8263-5cc35e8be8 a8 | ubuntu-test | ACTIVE | internal= 10.0.0. 161, 172.27.86.120 | ubuntu- bionic- cloudimg | m1.medium |
| 645f031e-
$ os server start 049f76c6- 3f6d-4299- b332-bf4c264b87 41 3f6d-4299- b332-bf4c264b87 41 9d46-41de- 955e-5ff97ef50d 28
$ os server image create --wait 049f76c6-
HTTP 404 Not Found: No image found with ID 9b5dd242-
Same as in original issue.