date:20170418

[Bug 1677710] Re: ds-identify does not find maas datasource

2017-04-18 Thread Andreas Hasenack

For xenial:

With the current cloud-init, where the problem appears:
 *** 0.7.9-48-g1c795b9-0ubuntu1~16.04.1 500
500 http://br.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages

# remove generated files
root@15-89:/run/cloud-init# rm cloud.cfg ds-identify.log

# cloud-init configuration, set via dpkg-reconfigure cloud-init and unchecking 
all items:
root@15-89:/run/cloud-init# cat /etc/cloud/cloud.cfg.d/90_dpkg.cfg 
# to update this file, run dpkg-reconfigure cloud-init
datasource_list: [  ]

# maas datasource config file, written to by MAAS:
root@15-89:/run/cloud-init# cat /etc/cloud/cloud.cfg.d/90_dpkg_maas.cfg 
# written by cloud-init debian package per preseed entries
# cloud-init/{maas-metadata-url,/maas-metadata-credentials}
datasource:
  MAAS: {consumer_key: L8SxaFb29L3rzc3Vw8, metadata_url: 
'http://10.0.5.5:5240/MAAS/metadata/',
token_key: 92LGSD8NBTHbD7n7T8, token_secret: 
FAbznaWcx72ryaK6SrErnqeK2z9LH2Dj}

# let's call ds-identify:
root@15-89:/run/cloud-init# unset DS_MAIN
root@15-89:/run/cloud-init# /usr/lib/cloud-init/ds-identify

# and we have no MAAS in cloud.cfg (somehow it thinks ec2 could be a candidate):
root@15-89:/run/cloud-init# cat cloud.cfg 
di_report:
  datasource_list: [ Ec2, None ]
  datasource: {Ec2: {strict_id: "warn"}}

# the ds-identify log file has
root@15-89:/run/cloud-init# cat ds-identify.log
(...)
DSLIST=MAAS ConfigDrive NoCloud AltCloud Azure Bigstep CloudSigma CloudStack 
DigitalOcean Ec2 OpenNebula OpenStack OVF SmartOS
(...)
is_container=false
ec2 platform is 'Unknown'.
check for 'Ec2' returned maybe
1 datasources returned maybe: Ec2
[up 273.31s] returning 0


Now I install the package from proposed:
 *** 0.7.9-90-g61eb03fe-0ubuntu1~16.04.1 500
500 http://br.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages

90_dpkg.cfg still has an empty list:
root@15-89:/run/cloud-init# cat /etc/cloud/cloud.cfg.d/90_dpkg.cfg 
# to update this file, run dpkg-reconfigure cloud-init
datasource_list: [  ]

And repeat the steps. This time I get:
root@15-89:/run/cloud-init# cat cloud.cfg
di_report:
  datasource_list: [ MAAS, None ]

And the ds-identify log has:
(...)
DSLIST=MAAS ConfigDrive NoCloud AltCloud Azure Bigstep CloudSigma CloudStack 
DigitalOcean Ec2 GCE OpenNebula OpenStack OVF SmartOS
(...)
is_container=false
check for 'MAAS' returned found
ec2 platform is 'Unknown'.
check for 'Ec2' returned maybe
Found single datasource: MAAS
[up 401.41s] returning 0

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1677710

Title:
  ds-identify does not find maas datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1677710/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1677710] Re: ds-identify does not find maas datasource

2017-04-18 Thread Andreas Hasenack

It's hard to reproduce the same error condition, as this happened during
the development of a new feature (deploying ubuntu-core via MAAS). The
closest I could get to it after some help from Ryan Harper was to run
ds-identify on a normally deployed MAAS node with the current cloud-init
and the proposed one, and check the results in /run/cloud-
init/cloud.cfg.

Besides that, I also configured MAAS to enable the -proposed
pocket and the nodes deployed just fine, and with the new cloud-init
from proposed installed.

For Yakkety:


With the current cloud-init, where the problem appears:
 *** 0.7.9-48-g1c795b9-0ubuntu1~16.10.1 500
500 http://br.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages

# remove generated files
root@15-89:/run/cloud-init# rm cloud.cfg ds-identify.log 

# cloud-init configuration, set via dpkg-reconfigure cloud-init and unchecking 
all items:
root@15-89:/run/cloud-init# cat /etc/cloud/cloud.cfg.d/90_dpkg.cfg 
# to update this file, run dpkg-reconfigure cloud-init
datasource_list: [  ]


# maas datasource config file, written to by MAAS:
root@15-89:/run/cloud-init# cat /etc/cloud/cloud.cfg.d/90_dpkg_maas.cfg 
# written by cloud-init debian package per preseed entries
# cloud-init/{maas-metadata-url,/maas-metadata-credentials}
datasource:
  MAAS: {consumer_key: xCkt8HsCeFKXBgm5SD, metadata_url: 
'http://10.0.5.5:5240/MAAS/metadata/',
token_key: 9pjmU6kjNAfdhe3xsJ, token_secret: 
kARCFjDaswVYDRLTSCTg9rrvXMjB7cGb}

# let's call ds-identify:
root@15-89:/run/cloud-init# unset DS_MAIN
root@15-89:/run/cloud-init# /usr/lib/cloud-init/ds-identify 

# and we have no MAAS in cloud.cfg (somehow it thinks ec2 could be a candidate):
root@15-89:/run/cloud-init# cat cloud.cfg 
datasource_list: [ Ec2, None ]
datasource: {Ec2: {strict_id: "warn"}}


# the ds-identify log file has
root@15-89:/run/cloud-init# cat ds-identify.log 
(...)
DSLIST=MAAS ConfigDrive NoCloud AltCloud Azure Bigstep CloudSigma CloudStack 
DigitalOcean Ec2 OpenNebula OpenStack OVF SmartOS
(...)
is_container=false
ec2 platform is 'Unknown'.
check for 'Ec2' returned maybe
1 datasources returned maybe: Ec2
[up 10525.51s] returning 0



Now I install the package from proposed:
 *** 0.7.9-90-g61eb03fe-0ubuntu1~16.10.1 500
500 http://br.archive.ubuntu.com/ubuntu yakkety-proposed/main amd64 
Packages


And repeat the steps. This time I get:
root@15-89:/run/cloud-init# cat cloud.cfg
datasource_list: [ MAAS, None ]

And the ds-identify log has:
root@15-89:/run/cloud-init# cat ds-identify.log
(...)
DSLIST=MAAS ConfigDrive NoCloud AltCloud Azure Bigstep CloudSigma CloudStack 
DigitalOcean Ec2 GCE OpenNebula OpenStack OVF SmartOS
(...)
is_container=false
check for 'MAAS' returned found
ec2 platform is 'Unknown'.
check for 'Ec2' returned maybe
Found single datasource: MAAS
[up 10721.60s] returning 0


** Tags removed: dsid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1677710

Title:
  ds-identify does not find maas datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1677710/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1615694] Re: [860730] Host experiencing constant session termination and recreation while using jumbo frames

2017-04-18 Thread Nish Aravamudan

Hi Clayton, sorry for the long delay on my part!

I think at this point, we need to ask upstream open-iscsi
(https://github.com/open-iscsi/open-iscsi/issues) about possible bugs in
their code.

They probably will ask you be running directly from github's sources
(rather than the package) -- are you able to build from source locally?
If we can get a fix from upstream narrowed down, I can help you get it
backported for SRU.

Thanks,
Nish

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1615694

Title:
  [860730] Host experiencing constant session termination and recreation
  while using jumbo frames

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1615694/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1677710] Re: ds-identify does not find maas datasource

[Bug 1677710] Re: ds-identify does not find maas datasource

[Bug 1615694] Re: [860730] Host experiencing constant session termination and recreation while using jumbo frames

3 matches

Site Navigation

Mail list logo

Footer information