@=> 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..

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

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 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.

Closing ticket due inactivity.

BR,
Bruno.