Lab 4.1

ibrahimblule

some steps are not clear :

3. Notice that the Update Image button remains grayed out. Select the link for Metadata in the upper left corner. Remove the top of the Existing Metadata, then select Update Image.

is this means to remove all exisiting list ?

when i tried to launce instance using created image , i couldnt find Networks to select private ..

Instance Name: golden Source: Image Allocated: dev-snap1 Flavor: m1.tiny Networks: Private

please your advice

serewicz

Hello,

Yes, there is currently a feature which required something to change with the metadata in order for the GUI to allow saving. Remove one item, the top item for example. No need to remove everything.  

As far as the networks, that is most likely due to the project permissions, not the metadata of that object. The private network is not a generally accessable network as public is, for example.

Regards,

 

ibrahimblule

thanks so much serewicz,

so you mean i need to delete only the first item in existing records , am i right ?

regarding the network , how to fix this issue and complete the excercise ?

please your advice

serewicz

Hello,

Yes, just delete the first item and the button to continue should become available to use. 

As far as the network, are you logged into Horizon as admin and using the demo project, not the alt_demo?

Regards,

Hamad Yousif

Hello

When I was done with the above steps (lab 4.1 from step 1 to step 5),  the newly created image dev-snap1 did not show for Allocated field. Only the cirros one was there. Please advise.

Thanks

jakubk

Hi Yousif,

Did you try to change the "Select Boot Source" to Instance Snapshoot? In my case just then the newly created "image" appears.

@selewicz: Is there a way to convert an image from the "instance snapshoot" into a simple "image" without downloading and then uploading it back to the OpenStack?

Best regards,

Jakub

prempython2018

Encrypted volume has been created without any issue but when trying to attach it to server instance golden or any otherserver image like DevOs3 then its showing attaching but not atatched and volume become come under  available state and not atatched to server instance, does any one have any inputs on this where/what is the issue please

serewicz

Hello,

I've been seeing a similar issue. I am working on steps to investigate the issue and a fix and hope to report a solution shortly.  From what I can tell it is the interaction with Barbican which may be not quite where it should be. Once I figure out the actual issue and fix, I'll know more. But that is what it looks like at the moment.

Regards,

 

pekon

@serewicz said:
Hello,

I've been seeing a similar issue. I am working on steps to investigate the issue and a fix and hope to report a solution shortly.  From what I can tell it is the interaction with Barbican which may be not quite where it should be. Once I figure out the actual issue and fix, I'll know more. But that is what it looks like at the moment.

I think the issue is dues to the instances created under different projects, have have different authorizations.

The "update image" button appears grey-out when accessed from "Project > Compute > Image" hierarchy. However same image can be updated when seen from "Admin > Compute > Image" hierarchy.

Please check the attached list of observations and corrections.

regards, pekon

akshay87

Hi,
I am not getting an option to select Private Network. Please see attached snapshot.

What was the solution for this?
Please advise.

serewicz

Hello akshay87,

What lab were you on? Which steps did you follow to get to this point? Did anything show an error prior to this issue?

Regards,