[Bug] v21.09.x Ubuntu Server 20.04 IP changes after reboot causing failures about packer-examples-for-vsphere HOT 18 CLOSED

Thanks, waiting for the next release. :)

from packer-examples-for-vsphere.

While the intent for this project was adjacent to my work as an architect on the VMware Validated Designs and VMware Validated Solutions and use with vRealize Automation's integration with the content library, this enhancement was added and approved in #44.

You'd modify config/common.pkvars.hcl in the next release.

// Template and Content Library Settings
common_template_conversion     = false
common_content_library_name    = "sfo-w01-lib01"
common_content_library_ovf     = false
common_content_library_destroy = false

You can always discuss in the GitHub Discussions.

Ryan

from packer-examples-for-vsphere.

v21.09 release or a clone of today's main?

Ryan

from packer-examples-for-vsphere.

If you're not a clone, can you test with main? Pushed a recent change to address the locks.

Ryan

from packer-examples-for-vsphere.

Hi there,

The lock issue I had was with version 21.08. It was weird that it worked fine for while and suddenly breaks.

The IP change issue I had was with the latest version 21.09.1 main

from packer-examples-for-vsphere.

Thanks for the update. It seems that these would be two separate issues and should be tracked separately.

With regards to "v21.09.1 main" did you download the v21.09.1 release package or git clone a copy of main? As the latter would be "top of tree" and be included in the next release.

Apologies, I'm trying to determine where on the commit timeline to investigate when time permits.

Ryan

from packer-examples-for-vsphere.

Also, there's a recent commit (#53) in main that aims to address the locking issue. Essentially the updates were running twice and locking / colliding at times.

Ryan

from packer-examples-for-vsphere.

I did git-clone a copy of v21.09.1 main .

I couldn't verify the locking issue still exists in ver21.09.1 because IP changes after reboot

from packer-examples-for-vsphere.

If you perform a git clone it will be pre-release as there are commits to main post-release.

Could you please download v21.09.01 from Releases and let me know if you experience the same issue.

Ryan

from packer-examples-for-vsphere.

I can confirm that I'm seeing a similar issue in main and retesting with v21.08 the issue does not seem to occur.

In v21.09.x it seems to have an issue after installing the desired packages.

Ryan

from packer-examples-for-vsphere.

FYI, one thing I was thinking while troubleshooting:

At the beginning , I thought it was my DHCP issue, because I setup DHCP IP expires in 30 mins, for testing purpose I only have a range of 20 IPs for DHCP.

So I changed the expire setting to 3 days and the issue still the same.

from packer-examples-for-vsphere.

Addressed in #61 for main.

You can patch v21.09.x with the following in user-data.pkrtpl.hcl for Ubuntu 20.04 LTS.

The locking issue should also be resolved with this change.

#cloud-config
autoinstall:
  version: 1
  early-commands:
    # Ensures that Packer does not connect too soon.
    - sudo systemctl stop ssh
  locale: ${vm_guest_os_language}
  keyboard:
    layout: ${vm_guest_os_keyboard}
  storage:
    layout:
      name: lvm
  identity:
    hostname: ubuntu-server
    username: ${build_username}
    password: ${build_password_encrypted}
  network:
    network:
      version: 2
      ethernets:
        ens33:
          dhcp4: true
  ssh:
    install-server: true
    allow-pw: true
  packages:
    - openssh-server
    - open-vm-tools
  user-data:
    disable_root: false
  late-commands:
    - 'sed -i "s/dhcp4: true/&\n      dhcp-identifier: mac/" /target/etc/netplan/00-installer-config.yaml'
    - echo '${build_username} ALL=(ALL) NOPASSWD:ALL' > /target/etc/sudoers.d/${build_username}
    - curtin in-target --target=/target -- chmod 440 /etc/sudoers.d/${build_username}
  timezone: ${vm_guest_os_timezone}

Ryan

from packer-examples-for-vsphere.

Thanks, I see the only change is ens192 to ens33

from packer-examples-for-vsphere.

Yes, but there are additional changes in #93 and #96 in 'main' that will be in the next release. Addresses theses two issues and others.

Ryan

from packer-examples-for-vsphere.

Just off the topic, can we have an option to choose where the templates stay? currently it goes to "content lib" , can it just stay in the "template" folder? Thx

from packer-examples-for-vsphere.

OK, confirmed, all working fine. Nice work!!

`==> Wait completed after 8 minutes 7 seconds

==> Builds finished. The artifacts of successful builds are:
--> vsphere-iso.linux-ubuntu-server: linux-ubuntu-server-20-04-lts
--> vsphere-iso.linux-ubuntu-server: linux-ubuntu-server-20-04-lts
Done.
Press Enter to continue.
`

from packer-examples-for-vsphere.

Excellent! Thanks for testing!

from packer-examples-for-vsphere.

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

from packer-examples-for-vsphere.