[Bug 779812] Re: uec-publish-tarball ignores the x86_64 option

2011-10-24 Thread Razique Mahroua
** Changed in: openstack-manuals
 Assignee: Anne Gentle (annegentle) = Razique Mahroua (razique)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779812

Title:
  uec-publish-tarball ignores the x86_64 option

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-manuals/+bug/779812/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 779812] Re: uec-publish-tarball ignores the x86_64 option

2011-10-23 Thread Razique Mahroua
** Changed in: openstack-manuals
   Status: In Progress = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779812

Title:
  uec-publish-tarball ignores the x86_64 option

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-manuals/+bug/779812/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 669142] Re: if-up.d/if-down.d scripts restart iSCSI inappropriately

2011-07-08 Thread Razique Mahroua
I experienced the same issue.
I've modified the beginning of the script this way : 


PATH=/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/sbin/iscsid
ADM=/sbin/iscsiadm
PIDFILE=/var/run/iscsid.pid
NAMEFILE=/etc/iscsi/initiatorname.iscsi
ISCSI_INTERFACE=br1:0


[ -x $DAEMON ] || exit 0

# Support for ifupdown script.
# Don't bother to restart when lo is configured.
if [ $IFACE != $ISCSI_INTERFACE ]; then
exit 0
fi


So now, appart from the explicitely interface specified, the open-iscsi daemon 
doesn't restart :)
Pay attention if you use some aliased interfaces though, you coud physically 
loose the connectivity.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669142

Title:
  if-up.d/if-down.d scripts restart iSCSI inappropriately

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 669142] Re: if-up.d/if-down.d scripts restart iSCSI inappropriately

2011-07-08 Thread Razique Mahroua
Actually, I've slighly updated it :

# Support for ifupdown script.
# Don't bother to restart when lo is configured.
if [ $IFACE != $ISCSI_INTERFACE ]  [ -n $IFACE ]; then
echo Not restarting ISCSI daemon... (check the value of 
ISCSI_INTERFACE)
exit 0
fi

Which means that I restart iscsi when the explicitely interface is set,
but you are still able to restart the iscsi daemon while you invoke the
script.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669142

Title:
  if-up.d/if-down.d scripts restart iSCSI inappropriately

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 669142] Re: if-up.d/if-down.d scripts restart iSCSI inappropriately

2011-07-07 Thread Razique Mahroua
** Changed in: open-iscsi (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669142

Title:
  if-up.d/if-down.d scripts restart iSCSI inappropriately

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 778392] [NEW] [UEC 2.0+bzr1241-0ubuntu4.1] Unstable state for the iscsi daemon

2011-05-06 Thread Razique Mahroua
Public bug reported:

Description:Ubuntu 10.10
Release:10.10
UEC suite : 2.0+bzr1241-0ubuntu4.1 

Description : 
After doing tests of custom EMI's instancitation, the Node Controller went 
unstable. I was then unable to instanciate anymore instances. For the running 
instances with EBS attached, I was then unable to detach them, and for new 
instances, unable to attach a new EBS volume : 

Detaching :

[Wed May  4 11:01:23 2011][020884][EUCAERROR ] ERROR: DetachVolume returned an 
error
[Wed May  4 11:01:23 2011] ERROR: doDetachVolume() returned FAIL

Attaching : 
[Wed May  4 09:26:04 2011][013319][EUCAERROR ] libvirt: internal error 
'//,46.227.16.70,iqn.2009-06.com.eucalyptus.cluster1:store5,Itj/2Zbs1QNRlVzKROjF7k5nKBnck0NuFPlgm2hlf7F63sMKldO0W3vG4at6RE4PRe5gy6tKMPnkpZXAUQlymBOT+hAUmT4cBgvDYNdmAN98oLlUGXqkzZVI3SxBBfUeHwAi7v/tQHcZUg49ezVWpdXg4D55DUHT6BwsxLYmxXmbqRUH5RVeXw7r8Dhaplh1P5X5KWZHvdCrQDWbUF8zU37jxOsUANzzpTYUTfRl7VtHitvzQ2ebY06xRbABziBe6MY/p3r6qILyl8vDgot1MQ+OzWH3WizsDRu4g0uDWI3MVfKUh2UEz2mOA/IKSQF7Cfrv2zyIpUSGq+uDPhp/hg=='
 does not exist (code=1)

In order to be able to instanciate, I manually restarted the iscsi part : 
$ service open-iscsi restart

which cleaned all the running sessions, but lead to : 
[Wed May  4 09:34:32 2011][013319][EUCAERROR ] libvirt: operation failed: disk 
sde not found (code=9)
when I was trying to dettach disks.

Even by restarting all the services (NC, NC-publication, SC, SC-
publication), UEC wouldn't clean the missing volumes. UEC kept in memory
iscsi sessions and attachments (on the node controller (/dev/sdX and
when euca2ools-describe-volumes invoked, the volumes were still
present))

Expected behaviour : 
- When all the components are restarted, the EBS sessions should be cleaned

What happened :
- Unable to get rid of Attaching... or Dettaching... status, due to missing 
iscsi volumes


Razique

** Affects: eucalyptus (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [UEC 2.0+bzr1241-0ubuntu4.1] Unstable state for the iscsi daemon

-- 
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 778392] [NEW] [UEC 2.0+bzr1241-0ubuntu4.1] Unstable state for the iscsi daemon

2011-05-06 Thread Razique Mahroua
Public bug reported:

Description:Ubuntu 10.10
Release:10.10
UEC suite : 2.0+bzr1241-0ubuntu4.1 

Description : 
After doing tests of custom EMI's instancitation, the Node Controller went 
unstable. I was then unable to instanciate anymore instances. For the running 
instances with EBS attached, I was then unable to detach them, and for new 
instances, unable to attach a new EBS volume : 

Detaching :

[Wed May  4 11:01:23 2011][020884][EUCAERROR ] ERROR: DetachVolume returned an 
error
[Wed May  4 11:01:23 2011] ERROR: doDetachVolume() returned FAIL

Attaching : 
[Wed May  4 09:26:04 2011][013319][EUCAERROR ] libvirt: internal error 
'//,46.227.16.70,iqn.2009-06.com.eucalyptus.cluster1:store5,Itj/2Zbs1QNRlVzKROjF7k5nKBnck0NuFPlgm2hlf7F63sMKldO0W3vG4at6RE4PRe5gy6tKMPnkpZXAUQlymBOT+hAUmT4cBgvDYNdmAN98oLlUGXqkzZVI3SxBBfUeHwAi7v/tQHcZUg49ezVWpdXg4D55DUHT6BwsxLYmxXmbqRUH5RVeXw7r8Dhaplh1P5X5KWZHvdCrQDWbUF8zU37jxOsUANzzpTYUTfRl7VtHitvzQ2ebY06xRbABziBe6MY/p3r6qILyl8vDgot1MQ+OzWH3WizsDRu4g0uDWI3MVfKUh2UEz2mOA/IKSQF7Cfrv2zyIpUSGq+uDPhp/hg=='
 does not exist (code=1)

In order to be able to instanciate, I manually restarted the iscsi part : 
$ service open-iscsi restart

which cleaned all the running sessions, but lead to : 
[Wed May  4 09:34:32 2011][013319][EUCAERROR ] libvirt: operation failed: disk 
sde not found (code=9)
when I was trying to dettach disks.

Even by restarting all the services (NC, NC-publication, SC, SC-
publication), UEC wouldn't clean the missing volumes. UEC kept in memory
iscsi sessions and attachments (on the node controller (/dev/sdX and
when euca2ools-describe-volumes invoked, the volumes were still
present))

Expected behaviour : 
- When all the components are restarted, the EBS sessions should be cleaned

What happened :
- Unable to get rid of Attaching... or Dettaching... status, due to missing 
iscsi volumes


Razique

** Affects: eucalyptus (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778392

Title:
  [UEC 2.0+bzr1241-0ubuntu4.1] Unstable state for the iscsi daemon

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs