Closing ticket due inactivity.

BR,
Bruno.

Dear KT,

@=> My whole problem starts when the secgroups STOP applying the change
(include newly added ports three days ago). I do not have this problem
previously.

I have not looked into this problem yet.

@=> The VM [ubuntu14_2016]( not VMs, only one) is based on public
basic_ubuntu fiware image [ubuntu_14.04]. I made a snapshort
[ubuntu14_2016](to backup what I have done to the public fiware ubuntu
image [ubuntu_14.04] ).
> I expect that after making a backup or snapshort, one should be able to
> create this into an instance and still able to login as previously.
Correct. Regarding login - do you use ssh keys? If you do, even if there were a change to the root password, it would not affect your ability to log in.

> Unfortunately, this does not happen. I no longer able to do sudo apt-get
> update because of this error [etc/sudoers.d/90-cloud-init-users: syntax
error near line 8]
We did no try this test - we will test this now and see what we observe. We would expect what you expected.

So, we performed this test:

• create instance from stock 14.04 image
• add a small file
• snapshot instance
• launch instance from snapshot
• log in to instance
• run sudo command

Note that in this case, I use ssh login and the ssh keys for the
snapshot and the original instance were the same.

I think this is more or less what you want to do.

We did notice one issue that it is not possible to launch the snapshot
from the 'snapshots' page - we had to launch it from the set of images.

@@@==> Is it possible for your team to access the instance or image of
ubuntu14_2016 to correct for the error in
[etc/sudoers.d/90-cloud-init-users: syntax error near line 8]
> I guess, the most important part of the cloud service is that the user
> can backup the image (snapshort) and able to turn that into instance
> again and able to login as user and still able to do sudo apt-get update..

Regarding accessing your VM, we cannot access this.

Did you put keys on the VM?

On a different note: the volume issue has been resolved - there was a recent change to our firewall rules which caused this problem - we were not aware of this - apologies for this inconvenience.

BR,
Seán.

Yes.
We will revert soon with an update on what we have seen.
We are still trying to progress the issue with the volumes, but we are waiting on feedback from other participants in the project.
BR,
Seán.

Dear KT,

> FIWARE is a relatively young initiative. We need to learn as much as > possible from feedback on how to provide a robust services. A few days back, I hesitated to provide all challenges I face when using Fiware cloud solution but to silently turning to other more reliable options like AWS or Azure.

Thanks for your support.

> However, I feel that the whole purpose of FIWARE is to eventually be able to come close in term of reliability as these commercial options.
> Please keep trying. Thank you your team for your support

Yes - we are pushing forward on this.

Apologies for not getting a quick resolution to these issues.

@=> My whole problem starts when the secgroups STOP applying the change
(include newly added ports three days ago). I do not have this problem
previously.
@=> The VM [ubuntu14_2016]( not VMs, only one) is based on public
basic_ubuntu fiware image [ubuntu_14.04]. I made a snapshort
[ubuntu14_2016](to backup what I have done to the public fiware ubuntu
image [ubuntu_14.04] ).

> I expect that after making a backup or snapshort, one should be able to
> create this into an instance and still able to login as previously.

Correct. Regarding login - do you use ssh keys? If you do, even if there were a change to the root password, it would not affect your ability to log in.

> Unfortunately, this does not happen. I no longer able to do sudo apt-get
> update because of this error [etc/sudoers.d/90-cloud-init-users: syntax
error near line 8]

We did no try this test - we will test this now and see what we observe. We would expect what you expected.

@@@==> Is it possible for your team to access the instance or image of
ubuntu14_2016 to correct for the error in
[etc/sudoers.d/90-cloud-init-users: syntax error near line 8]

> I guess, the most important part of the cloud service is that the user
> can backup the image (snapshort) and able to turn that into instance
> again and able to login as user and still able to do sudo apt-get update..

Yes.

We will revert soon with an update on what we have seen.

We are still trying to progress the issue with the volumes, but we are waiting on feedback from other participants in the project.

BR,
Seán.

Dear Seán.

FIWARE is a relatively young initiative. We need to learn as much as possible from feedback on how to provide a robust services. A few days back, I hesitated to provide all challenges I face when using Fiware cloud solution but to silently turning to other more reliable options like AWS or Azure.

However, I feel that the whole purpose of FIWARE is to eventually be able to come close in term of reliability as these commercial options.

Please keep trying. Thank you your team for your support

Regards,
KT

@=> My whole problem starts when the secgroups STOP applying the change
(include newly added ports three days ago). I do not have this problem
previously.
@=> The VM [ubuntu14_2016]( not VMs, only one) is based on public
basic_ubuntu fiware image [ubuntu_14.04]. I made a snapshort
[ubuntu14_2016](to backup what I have done to the public fiware ubuntu
image [ubuntu_14.04] ).

I expect that after making a backup or snapshort, one should be able to
create this into an instance and still able to login as previously.
Unfortunately, this does not happen. I no longer able to do sudo apt-get
update because of this error [etc/sudoers.d/90-cloud-init-users: syntax
error near line 8]

@@@==> Is it possible for your team to access the instance or image of
ubuntu14_2016 to correct for the error in
[etc/sudoers.d/90-cloud-init-users: syntax error near line 8]

I guess, the most important part of the cloud service is that the user
can backup the image (snapshort) and able to turn that into instance
again and able to login as user and still able to do sudo apt-get update..

Hi KT,

A few issues to deal with there...

We're not responsible for all of these points, but we'll try to help as much as a we can.

First, we're still looking into the volume issue - the problem still manifests for us. We're waiting on feedback on that point while also pursuing further testing.

So, to address your issues:

> => Instance ubuntu14_2016
> <https://cloud.lab.fiware.org/#nova/instances/a4a80f4c-a6a2-4a26- 960b-5843afad2c09/detail>

> =>I test this problem by launching a brand new ubuntu image into
instance ubuntu_14.04
> <https://cloud.lab.fiware.org/#nova/instances/5347e11f-4af3-4716-b0a2-fe1aa50c0543/detail>
> ( test). I am able to ssh login in and run
> sudo apt-get update (without problem)

Ok - that is good - this is the image provided by Fiware and it
seems to work sensibly.

> => Clearly, something strange happens to theubuntu14_2016
> <https://cloud.lab.fiware.org/#nova/instances/a4a80f4c-a6a2-4a26-960b-5843afad2c09/detail> , which I have been working without problem (e.g.
> sudo apt-get update)
> Please grant me root access again so I can continue with my development work.
> Thanks again for excellent timely support!!!!!

So I've checked out the VM and the image.

The VM is based on the image

ubuntu14-jan2016 (34939e0c-2920-4861-a99b-afb3dd0edbf1)

This is not one of the official Fiware images. Details on this image
are as follows:

root@node-1:~# glance image-show 34939e0c-2920-4861-a99b-afb3dd0edbf1
------------------------------------------------------+

------------------------------------------------------+

------------------------------------------------------+

You can see that this is a private image to the account 6770
(your account). You can also see that it is not a public image
('is_private' set to False).

So, I don't know what this image is or where it came from. This
makes it difficult to address issues relating to it as I'm sure you
understand. Do you have any info on where this image came from
which could help us understand what we are dealing with?

Next issue:

> Dear Seán
> What is the best practice to add new port to the "Security Groups"
> I have added new ports, I have tried different ways to make these ports work. Including creating a new instance using the security Groups with new ports, no luck.
> Any suggestion? How to the newly added ports get reflected in the running instance?

To be clear here, I assume you're asking about opening ports.

To add a new port to an existing secgroup, you need to select the
secgroup by clicking on the security panel on the left and then the
security groups tab on the top. Then you select the secgroup you
want to modify. Check the box, then go to actions. Edit rules. Add a rule indicating the source port and the destination port (usually the port you want to open on your VM) and make the CIDR 0.0.0.0/0 to enable access to this port from anywhere on the internet. Then click on Add rule and the rule should appear in your secgroup.

The rules for the secgroups get applied instantly, I think.

> Dear Seán,
> It seems that the password I used to enable sudo (root) no longer valid.
> Very strange.
> Please reset these password or mail the temporary password DIRECTLY to my email. Thank you.

Right now, we cannot reset the root password of your VMs, I'm afraid.

Is this a big problem? Can you just restart a new VM - is there much info on this VM which you need to keep?

BR,
Seán.

Dear Seán,

It seems that the password I used to enable sudo (root) no longer valid.
Very strange.

Please reset these password or mail the temporary password DIRECTLY to my email. Thank you.

KT

Dear Seán

What is the best practice to add new port to the "Security Groups"

I have added new ports, I have tried different ways to make these ports work. Including creating a new instance using the security Groups with new ports, no luck.

Any suggestion? How to the newly added ports get reflected in the running instance?

Thanks again!

=> Instance ubuntu14_2016
<https://cloud.lab.fiware.org/#nova/instances/a4a80f4c-a6a2-4a26-960b-5843afad2c09/detail>

=>I test this problem by launching a brand new ubuntu image into
instance ubuntu_14.04
<https://cloud.lab.fiware.org/#nova/instances/5347e11f-4af3-4716-b0a2-fe1aa50c0543/detail>
(test). I am able to ssh login in and run

sudo apt-get update (without problem)

=> Clearly, something strange happens to theubuntu14_2016
<https://cloud.lab.fiware.org/#nova/instances/a4a80f4c-a6a2-4a26-960b-5843afad2c09/detail> , which I have been working without problem (e.g.
sudo apt-get update)

Please grant me root access again so I can continue with my development work.

Thanks again for excellent timely support!!!!!

> Dear Seán.
> I checked this morning. Now it is possible to launch an image and I am able to login as user
> Thank you for your team's support. It is critical for us to keep up with
our development schedule.

Yes - we were informed a little earlier that the problem with the web portal should be resolved now.

> Additional issues
> (a) I am no longer a sudoer anymore – urgent ( sudo apt-get update no
longer work!)

That's a real problem - can you tell us which image this applies to?

>>> /etc/sudoers.d/90-cloud-init-users: syntax error near line 8 <<<
sudo: parse error in /etc/sudoers.d/90-cloud-init-users near line 8
sudo: no valid sudoers sources found, quitting
sudo: unable to initialize policy plugin

> (b) I still not able to mount a volume under
https://cloud.lab.fiware.org/#nova/volumes/
*Error:*Error creating volume volume1. Cause: 503 Error

Ok - this is a strange error - we are looking into this now.

Apologies for these difficulties.

BR,
Seán.

Thanks again for your team to support us!

Dear Seán.

I checked this morning. Now it is possible to launch an image and I am
able to login as user
Thank you for your team's support. It is critical for us to keep up with
our development schedule.

Additional issues
(a) I am no longer a sudoer anymore – urgent ( sudo apt-get update no
longer work!)
>>> /etc/sudoers.d/90-cloud-init-users: syntax error near line 8 <<<
sudo: parse error in /etc/sudoers.d/90-cloud-init-users near line 8
sudo: no valid sudoers sources found, quitting
sudo: unable to initialize policy plugin

(b) I still not able to mount a volume under
https://cloud.lab.fiware.org/#nova/volumes/
*Error:*Error creating volume volume1. Cause: 503 Error

Thanks again for your team to support us!

The email is : info@wei-medicine.com

The IP is 160.85.2.x ( every time I disassociate and re associate IP, x
changes, currently x = 73) .
I can not access the instance using ssh right now. It was fine for last
few weeks.

The problems started because I change the security rule yesterday to
open more ports, however, the addition of ports were not recognized by
the network ( as it should have been for the last few weeks). Due to
that, I started trouble-shooting and the instability (web in-responsive)
got worse.

I hope this feedback helps others.

KT

Hi KT,

Apologies for the problems you are having.

I looked up your email addr (kts@wei-medicine.com), but could not find an account registered under this email addr. Can you tell me what email addr you use to log in to the service so I can look into this further.

Also, can you tell us what IP addr has been allocated to your VM?

Thanks,
Seán.

Dear Seán,

For whatever reason, I am able to allocate IP to one remaining instance.
However, when I reboot the instance, there are many network error.
After these errors, when the login is ready, I am not able to use Putty SSH to log in

Thanks, this happens for the last two days, very often, the interface
just simply frozen for the last two days

> Dear Seán.
> My most urgent problem, I simply cannot launch an image.

We have seen the same problem on the web interface. Unfortunately, we are not responsible for this. We will check with others in the project to determine if this is a known problem.

BR,
Seán.

I have created a snapshort of a ubuntu14. I have tried both the
snapshort and a base Ubuntu, in both cases, I am not able to launch the
images into instance even I have the sufficient resources
Please check to see what happen.
I will follow with screen shorts
Thanks for your help
KT

> My account seems to be frozen.
> I no longer able to lunch an image even the allocated CPU, Memory > and
> instance are sufficient.
> Please urgently look into it. Thank you

We see some problems with the web interface right now.

I will raise this with the responsibles and let you know as soon as I hear further.

Apologies for this,
Seán.

Dear Seán.

My most urgent problem, I simply cannot launch an image.
I have created a snapshort of a ubuntu14. I have tried both the
snapshort and a base Ubuntu, in both cases, I am not able to launch the
images into instance even I have the sufficient resources

Please check to see what happen.

I will follow with screen shorts

Thanks for your help

KT

Dear KT,

Apologies for the delay in responding.

> (b) In my Networks (https://cloud.lab.fiware.org/#neutron/networks/)
> I have 3 networks. 2 given to me (federation-int-net-01
> <https://cloud.lab.fiware.org/#neutron/networks/96bf7d04-eda8-4970-9f14-eb97f2466ff3>),
> (node-int-net-01
> <https://cloud.lab.fiware.org/#neutron/networks/253856c2-acb8- 4b31-904f-0154b753a99d>),
> one I created myself ( 1-network)
> I created an instance (1-instance) choosing 1-network.
> I stop the 1-instance and restart it
> Now I cannot (at
> https://cloud.lab.fiware.org/#nova/access_and_security/)
> allocate IP to project to 1-network, only to

I'm not sure what you mean by project 1-network.

> (federation-int-net-01
> <https://cloud.lab.fiware.org/#neutron/networks/96bf7d04-eda8- 4970-9f14-eb97f2466ff3>),
> (node-int-net-01
> <https://cloud.lab.fiware.org/#neutron/networks/253856c2-acb8-4b31-904f-0154b753a99d>)
> (ii) associate IP to 1-instance, because the IP address
> assigned to 1-instance based on 1-network is not visible
> Please advice how to solve this problem
> (c) The 1-instance is linked to 1-network. Is it possible to change to
> either (federation-int-net-01
> <https://cloud.lab.fiware.org/#neutron/networks/96bf7d04-eda8-4970-9f14-eb97f2466ff3>),
> (node-int-net-01
> <https://cloud.lab.fiware.org/#neutron/networks/253856c2-acb8-4b31-904f-0154b753a99d>),
> after the instance has been created?
> (d) The. "1-network" has "1 subnet". However, the shared status is NO,
> how to make it Yes? The 1-network has shown to work before. After > I stop
> the 1-instance and restart the 1-instance, I am no longer able to
> allocate IP to 1-network and to associate 1-instance to 1-network IP
> PLease let me know if these questions are clear.

I'm afraid this is not clear to me.

Would you be able to include some screenshots to highlight what the problems are?

BR,
Seán.

My account seems to be frozen.
I no longer able to lunch an image even the allocated CPU, Memory and
instance are sufficient.
Please urgently look into it. Thank you

KT

(a) I still do not have the contact of the admin of Zurich

(b) In my Networks (https://cloud.lab.fiware.org/#neutron/networks/)
I have 3 networks. 2 given to me (federation-int-net-01
<https://cloud.lab.fiware.org/#neutron/networks/96bf7d04-eda8-4970-9f14-eb97f2466ff3>),
(node-int-net-01
<https://cloud.lab.fiware.org/#neutron/networks/253856c2-acb8-4b31-904f-0154b753a99d>),
one I created myself ( 1-network)
I created an instance (1-instance) choosing 1-network.
I stop the 1-instance and restart it
Now I cannot (at
https://cloud.lab.fiware.org/#nova/access_and_security/)
allocate IP to project to 1-network, only to
(federation-int-net-01
<https://cloud.lab.fiware.org/#neutron/networks/96bf7d04-eda8-4970-9f14-eb97f2466ff3>),
(node-int-net-01
<https://cloud.lab.fiware.org/#neutron/networks/253856c2-acb8-4b31-904f-0154b753a99d>)
(ii) associate IP to 1-instance, because the IP address
assigned to 1-instance based on 1-network is not visible

Please advice how to solve this problem

(c) The 1-instance is linked to 1-network. Is it possible to change to
either (federation-int-net-01
<https://cloud.lab.fiware.org/#neutron/networks/96bf7d04-eda8-4970-9f14-eb97f2466ff3>),
(node-int-net-01
<https://cloud.lab.fiware.org/#neutron/networks/253856c2-acb8-4b31-904f-0154b753a99d>),
after the instance has been created?

(d) The. "1-network" has "1 subnet". However, the shared status is NO,
how to make it Yes? The 1-network has shown to work before. After I stop
the 1-instance and restart the 1-instance, I am no longer able to
allocate IP to 1-network and to associate 1-instance to 1-network IP

PLease let me know if these questions are clear.

KT

Hello,
Can you describe the problems in a more detailed way? In the meanwhile I send your request to the Zurich support team.

Regards,
Giuseppe