rating discrepancy

[echofs]

As a buyer, I see that our seller rating here https://spotcloud.appspot.com/buyer/market?page=1 is 3 stars (for some reason?), but when you click > Go to reserve an instance it shows 5/5 stars. 

 

--Seller #1047

[adam boduch]

Hi,

I bet this is the content being cached for the market and not for the offer details page.  Let me know if this doesn't correct itself and I'll dig deeper on this.

Regards,

Adam

[echofs]

Ok, so that begs the question why our rating is changing so much. I am getting no response from spot...@enomaly.com. Is that address monitored?

[Adam Boduch]

Hi,

The best place to get a response to your questions is here.

About your rating, its updated several times throughout the day, to if
your available resources and API errors fluctuate, your rating will
change correspondingly.

Did you have specific concerns about why your rating is changing? If
so, I'm happy to take a look.

Regards,

Adam

[Lars-Erik Forsberg]

Posted on behalf of echofs.

-----------------------

Once again we received the spurious admonition that our instance was shut down because it did not receive a public IP address, and once again I have to point out that it is incorrect.

 

Three instances have been provisioned on our system in the last day, and all three of them were assigned public IPs and all three of them acknowledged the DHCP lease from the guest OS:

 

admin logs:

 

spotcloud ee2840f8-9141-11e0-9c18-002590267f9c 06/19/11 10:54:24+07 Unknown  100% Provisioning completed

dhcpd logs:

 

Jun 19 10:57:05 ecp dhcpd: DHCPDISCOVER from 00:16:73:97:08:e7 via virbr0

Jun 19 10:57:05 ecp dhcpd: DHCPOFFER on 67.209.225.125 to 00:16:73:97:08:e7 (ubuntuvm) via virbr0

Jun 19 10:57:06 ecp dhcpd: DHCPREQUEST for 67.209.225.125 (67.209.225.87) from 00:16:73:97:08:e7 (ubuntuvm) via virbr0

Jun 19 10:57:06 ecp dhcpd: DHCPACK on 67.209.225.125 to 00:16:73:97:08:e7 (ubuntuvm) via virbr0

admin logs:

 

spotcloud ee2840f8-9141-11e0-9c18-002590267f9c 06/19/11 17:00:01+07 spotcloud_SC_CHECK_3e9e2f5e-9ad0-11e0-a367-7b80b9378c76  100% Provisioning 

completed

 

dhcpd logs:

 

Jun 19 17:02:54 ecp dhcpd: DHCPDISCOVER from 00:16:a5:9e:2f:dc via virbr0

Jun 19 17:02:55 ecp dhcpd: DHCPOFFER on 67.209.225.112 to 00:16:a5:9e:2f:dc (ubuntuvm) via virbr0

Jun 19 17:02:55 ecp dhcpd: DHCPREQUEST for 67.209.225.112 (67.209.225.87) from 00:16:a5:9e:2f:dc (ubuntuvm) via virbr0

Jun 19 17:02:55 ecp dhcpd: DHCPACK on 67.209.225.112 to 00:16:a5:9e:2f:dc (ubuntuvm) via virbr0

spotcloud

ee2840f8-9141-11e0-9c18-002590267f9c

06/19/11 17:00:01+07

spotcloud_SC_CHECK_3e9e2f5e-9ad0-11e0-a367-7b80b9378c76

100%

Provisioning completed

admin logs:

 

spotcloud ee2840f8-9141-11e0-9c18-002590267f9c 06/20/11 06:52:40+07 Unknown  100% Provisioning completed

dhcpd logs:

 

spotcloud

ee2840f8-9141-11e0-9c18-002590267f9c

06/20/11 06:52:40+07

Unknown

100%

Provisioning completed

spotcloud

ee2840f8-9141-11e0-9c18-002590267f9c

06/20/11 06:52:40+07

Unknown

100%

Provisioning completed

spotcloud

ee2840f8-9141-11e0-9c18-002590267f9c

06/20/11 06:52:40+07

Unknown

100%

Provisioning completed

spotcloud

ee2840f8-9141-11e0-9c18-002590267f9c

06/20/11 06:52:40+07

Unknown

100%

Provisioning completed

spotcloud

ee2840f8-9141-11e0-9c18-002590267f9c

06/20/11 06:52:40+07

Unknown

100%

Provisioning completed

Jun 20 06:55:57 ecp dhcpd: DHCPDISCOVER from 00:16:a6:c0:b4:a5 via virbr0

Jun 20 06:55:58 ecp dhcpd: DHCPOFFER on 67.209.225.122 to 00:16:a6:c0:b4:a5 (ubuntuvm) via virbr0

Jun 20 06:55:58 ecp dhcpd: DHCPREQUEST for 67.209.225.122 (67.209.225.87) from 00:16:a6:c0:b4:a5 (ubuntuvm) via virbr0

Jun 20 06:55:58 ecp dhcpd: DHCPACK on 67.209.225.122 to 00:16:a6:c0:b4:a5 (ubuntuvm) via virbr0

Once again, I have also confirmed that if I provision one manually, I can acess the instnace from the internet without problem.

 

Please address this. Our rating is now 1 star as a result of it, and everything appears to be properly set up from our end.

[Derek Anderson]

The most likely cause for this kind of failure is actually not that the DHCP server never got an address for the VM, but that the VM completed provisioning too long after the initial request, so the Spotcloud monitor gave up waiting for a running machine/address before the job completed.

To diagnose, it would be helpful to get the logs that contained the original provisioning request for that VM so that we can see how much time had passed. It is likely the provision job took a long time (20+ minutes) and resulted in the VM starting and getting an address after spotcloud had already marked it as "no IP received by deadline". If not, then I'll need to get the original provision job timestamp, the progress, dhcp pcap messages from the manager to correlate with our logs and try and figure out why you are not getting addresses sent to our service. 

If you ECP had queued more VMs up for provisioning than you have hosts, this could also be part of the problem, as provisioning is done sequentially.

Finally, just to confirm, are you running 3.5.1 of ECP? There was a bug in 3.5 that we fixed that may be biting you if you are still on that version.

 - Derek