jFed Feedback #2136: Bug/Problem Report: Resources disappear and cannot be accessed Utah testbed

[jfedbug...@ilabt.imec.be]

The jFed Experimenter GUI sent feedback for user Mol...@wall2.ilabt.iminds.be

Feedback:
Type: Bug Report
Related testbeds: urn:publicid:IDN+utah.cloudlab.us+authority+cm

Description:
After some time the resources reserved on the Utah testbed disappear from the jFed GUI and cannot be accessed anymore. This happened on two different slices that seem to be still running but I cannot access the nodes.

[Brecht Vermeulen]

Hi Molka,

can you give some more information about 'after some time'.

Is this a couple of hours, days, weeks ?

Were the machines idle ?

Did you receive any email from cloudlab about expiration or idling ?

thanks,

Brecht

--
You received this message because you are subscribed to the Google Groups "fed4fire-experimenters" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fed4fire-experime...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fed4fire-experimenters/814085870.12.1579798513448%40flsmonitor-api.atlantis.ugent.be.

[Brecht Vermeulen]

Hi Molka,

thanks, can you give me a slice name, then I can check.

thanks,

Brecht

On Thu, Jan 23, 2020 at 6:23 PM mgharbaoui <mghar...@cnit.it> wrote:

Hi Brecht,

The access to the nodes is interrupted after almost 24 hours of the 
creation of the slices even if I set the experiment to expire after 
two months. This happened for two different slices (one created two 
days ago and one created yesterday).

Practically, the terminal becomes inactive, the public IP addresses 
are not anymore reachable from the browser and when I update the 
status of the topology viewer in jFed or I recover the experiment 
after closing it the nodes disappear.

On the machines I am running openstack and OSM that few seconds before 
the interruption were perfectly responding so they were not idle.

I did not receive any email feom cloudlab.

Thank you!

Brecht Vermeulen <Brecht.V...@ugent.be> ha scritto:

> https://groups.google.com/d/msgid/fed4fire-experimenters/CAOLR0vyw4LPkJWJYMxBmGdebrJddX5vEzKibVeOxZ88qGE-w8g%40mail.gmail.com.

[Brecht Vermeulen]

Hi Molka,

are you sure that jFed did not give an error when you extended the slice till March ?

I get this:

so max 5 days.

(when it fails, it does not extend it, but jFed should show this:

thanks,

Brecht

On Thu, Jan 23, 2020 at 7:05 PM mgharbaoui <mghar...@cnit.it> wrote:

Hi Brecht,

The experiments are slice2 and costa1 (slice2 is the most recent one). 
Both belong to the project lash-5g.

Thank you.

[mgharbaoui]

Hi Brecht,

No. I did not get that error because at creation time I set the
expiration date to march so I had not to renew or extend it.

I don't fully get the meaning of Leigh Stoller's reply. What shall I
do? Create the experiment from the CloudLab portal and not use jFed?

[mgharbaoui]

Hi Brecht,

The experiments are slice2 and costa1 (slice2 is the most recent one).
Both belong to the project lash-5g.

Thank you.

[mgharbaoui]

Hi Brecht,

The access to the nodes is interrupted after almost 24 hours of the
creation of the slices even if I set the experiment to expire after
two months. This happened for two different slices (one created two
days ago and one created yesterday).

Practically, the terminal becomes inactive, the public IP addresses
are not anymore reachable from the browser and when I update the
status of the topology viewer in jFed or I recover the experiment
after closing it the nodes disappear.

On the machines I am running openstack and OSM that few seconds before
the interruption were perfectly responding so they were not idle.

I did not receive any email feom cloudlab.

Thank you!

Brecht Vermeulen <Brecht.V...@ugent.be> ha scritto:

> https://groups.google.com/d/msgid/fed4fire-experimenters/CAOLR0vyw4LPkJWJYMxBmGdebrJddX5vEzKibVeOxZ88qGE-w8g%40mail.gmail.com.

[Brecht Vermeulen]

Hi Molka,

I see, there is indeed somewhere a bug if you give a long end date when starting, you do not get a warning then.

We will check this out !

For now: start your experiment with duration of 2 hours, and then renew.

(you will be able to renew max for 5 days on cloudlab).

We'll let you know.

thanks,

Brecht

On Fri, Jan 24, 2020 at 9:38 AM mgharbaoui <mghar...@cnit.it> wrote:

Hi Brecht,

No. I did not get that error because at creation time I set the 
expiration date to march so I had not to renew or extend it.

I don't fully get the meaning of Leigh Stoller's reply. What shall I 
do? Create the experiment from the CloudLab portal and not use jFed?

[mgharbaoui]

Hi Brecht,

So if I understand correctly, currently the maximum duration of the
experiment is of 5 days. After that, I should restart everything from
scratch, right?

[Brecht Vermeulen]

Hi Molka,

you will be able to renew each time for max. 5 days.

But there seems to be another problem as well:

 Insecure VNC password on port 5902: 

I will contact you on private email.

best regards,

Brecht 

On Fri, Jan 24, 2020 at 9:49 AM mgharbaoui <mghar...@cnit.it> wrote:

Hi Brecht,

So if I understand correctly, currently the maximum duration of the 
experiment is of 5 days. After that, I should restart everything from 
scratch, right?

[brecht.vermeulen]

Hi,

as a follow up, there were three problems:

- jFed did not process correctly the limitation of 5 days on cloudlab when starting an experiment with an expiration date longer than 5 days (we work on that at jFed side)

- the installation of openstack opened up a vnc without password which was detected automatically by a scanner at cloudlab, after sending some emails, they close off the expeirment

- Molka did not receive those emails because of a problem in her account -> we worked around this with a new account.

Brecht

>> >> >> >> email to fed4fire-experimenters+unsub...@googlegroups.com.

>> >> >> >> To view this discussion on the web visit
>> >> >> >>
>> >> >>
>> >>
>> https://groups.google.com/d/msgid/fed4fire-experimenters/814085870.12.1579798513448%40flsmonitor-api.atlantis.ugent.be
>> >> >> >> .
>> >> >> >>
>> >> >> >
>> >> >> > --
>> >> >> > You received this message because you are subscribed to the Google
>> >> >> > Groups "fed4fire-experimenters" group.
>> >> >> > To unsubscribe from this group and stop receiving emails from it,
>> >> >> > send an email to

>> fed4fire-experimenters+unsub...@googlegroups.com.