Do we still need dhclient in our cloud images? I am looking at the candidate for F22 [1] and am having issues with my network coming up on boot in an openstack environment. I suspect the fact that dhclient isn't in the image is to blame. It is in the F21 image. Was it intentionally removed?
Dusty
[1] - http://koji.fedoraproject.org/koji/taskinfo?taskID=9029299
Do we still need dhclient in our cloud images? I am looking at the candidate for F22 [1] and am having issues with my network coming up on boot in an openstack environment. I suspect the fact that dhclient isn't in the image is to blame. It is in the F21 image. Was it intentionally removed?
No, it was renamed to dhcp-client, is that there?
On Wed, Feb 25, 2015 at 3:40 PM, Peter Robinson pbrobinson@gmail.com wrote:
Do we still need dhclient in our cloud images? I am looking at the candidate for F22 [1] and am having issues with my network coming up on boot in an openstack environment. I suspect the fact that dhclient isn't in the image is to blame. It is in the F21 image. Was it intentionally removed?
No, it was renamed to dhcp-client, is that there?
It wasn't when I tested the cloud-init update last weekend. I had to install it to make instances start getting network access.
-- Garrett Holmstrom
On Wed, Feb 25, 2015 at 04:43:51PM -0800, Garrett Holmstrom wrote:
On Wed, Feb 25, 2015 at 3:40 PM, Peter Robinson pbrobinson@gmail.com wrote:
Do we still need dhclient in our cloud images? I am looking at the candidate for F22 [1] and am having issues with my network coming up on boot in an openstack environment. I suspect the fact that dhclient isn't in the image is to blame. It is in the F21 image. Was it intentionally removed?
No, it was renamed to dhcp-client, is that there?
It wasn't when I tested the cloud-init update last weekend. I had to install it to make instances start getting network access.
Agree with Garrett. There isn't a dhcp-client rpm installed in the image.
Dusty
On Thu, Feb 26, 2015 at 6:27 AM, Dusty Mabe dusty@dustymabe.com wrote:
On Wed, Feb 25, 2015 at 04:43:51PM -0800, Garrett Holmstrom wrote:
On Wed, Feb 25, 2015 at 3:40 PM, Peter Robinson pbrobinson@gmail.com wrote:
Do we still need dhclient in our cloud images? I am looking at the candidate for F22 [1] and am having issues with my network coming up on boot in an openstack environment. I suspect the fact that dhclient isn't in the image is to blame. It is in the F21 image. Was it intentionally removed?
No, it was renamed to dhcp-client, is that there?
It wasn't when I tested the cloud-init update last weekend. I had to install it to make instances start getting network access.
Agree with Garrett. There isn't a dhcp-client rpm installed in the image.
I am trying to do a local build with the above mentioned package, but sadly all of my local builds are failing with the error mentioned below.
"No operating systems found on the disk"
I am looking into this.
Kushal
On Thu, Feb 26, 2015 at 12:43 AM, Garrett Holmstrom gholms@fedoraproject.org wrote:
On Wed, Feb 25, 2015 at 3:40 PM, Peter Robinson pbrobinson@gmail.com wrote:
Do we still need dhclient in our cloud images? I am looking at the candidate for F22 [1] and am having issues with my network coming up on boot in an openstack environment. I suspect the fact that dhclient isn't in the image is to blame. It is in the F21 image. Was it intentionally removed?
No, it was renamed to dhcp-client, is that there?
It wasn't when I tested the cloud-init update last weekend. I had to install it to make instances start getting network access.
Looks like someone didn't update comps when the name changed, I've now done this.
Peter
On Thu, Feb 26, 2015 at 09:38:14AM +0000, Peter Robinson wrote:
On Thu, Feb 26, 2015 at 12:43 AM, Garrett Holmstrom gholms@fedoraproject.org wrote:
On Wed, Feb 25, 2015 at 3:40 PM, Peter Robinson pbrobinson@gmail.com wrote:
Do we still need dhclient in our cloud images? I am looking at the candidate for F22 [1] and am having issues with my network coming up on boot in an openstack environment. I suspect the fact that dhclient isn't in the image is to blame. It is in the F21 image. Was it intentionally removed?
No, it was renamed to dhcp-client, is that there?
It wasn't when I tested the cloud-init update last weekend. I had to install it to make instances start getting network access.
Looks like someone didn't update comps when the name changed, I've now done this.
The latest TC at [1] now has dhcp-client in the image and networking seems to come up fine (at least on openstack).
Dusty
[1] - http://koji.fedoraproject.org/koji/taskinfo?taskID=9097429
-
Dusty Mabe -
Garrett Holmstrom -
Kushal Das -
Peter Robinson