Home · About · Download · Documentation · Getting Help · Google+

Ticket #52 (closed defect: invalid)

Opened 6 years ago

Last modified 6 years ago

wwvnfs and vnfs names

Reported by: fernsler Owned by: gmk
Priority: minor Milestone:
Component: provision Version:
Keywords: Cc: fernsler

Description

I was only doing what wwmkchroot suggested:

TEMPLATE_NAME (select one of the following):

  • centos-5
  • centos-6
  • rhel-generic
  • sl-5
  • sl-6

My chroot is called "sl-6".

Moving on to create/import the vnfs:


[root@phoenix .ssh]# wwvnfs --chroot /var/chroots/sl-6
Using 'sl-6' as the VNFS name
WARNING: Hybridpath defined, but not configured in the VNFS /etc/fstab!
ERROR: Illegal characters in --hybridpath option: /mnt/warewulf/%{VNFS}/
[root@phoenix .ssh]#

Change History

comment:1 Changed 6 years ago by gmk

Hi,

Can you give me some more background? :)

Where did wwmkchroot tell you to do that?

What is in /etc/warewulf/vnfs.d/sl-6.conf?

What version of WW is this?

Do we need to fix and rebuild the tarballs for the 3.2 release?

Thanks!

comment:2 Changed 6 years ago by fernsler

  • Priority changed from blocker to minor
  • Component changed from general to provision

Ok, it doesn't actually suggest to put a dash in the directory name.

I ran "wwmkchroot sl-6 /var/chroots/sl-6"

--
/etc/warewulf/vnfs.d/sl-6.conf contains:

[root@phoenix fernsler]# cat /etc/warewulf/vnfs.d/sl-6.conf
# Configuration file for 'sl-6' automatically generated by command:
# /usr/bin/wwvnfs --chroot /var/chroots/sl-6/

# Any command line options will override these on a case by case basis.
# The location of the template chroot. This needs to be set here or via --chroot.
chroot = /var/chroots/sl-6/

# If this is defined, the VNFS will be written here instead of imported into
# Warewulf automatically
# output = /tmp/sl-6.vnfs

# If you use this option, you should make sure that the path defined is
# mounted via the VNFS's fstab
# hybridpath = /hybrid/sl-6

# Location of a single file that lists all files to be excluded from the VNFS
# excludefile = /etc/warewulf/shared-excludes

# The list of all excluded files and paths from the VNFS
# excludes = /exclude/path1
# excludes += /exclude/path2

--
I pulled this from  http://warewulf.lbl.gov/downloads/repo/rhel6 today. The rpms say 3.2.1.

Additional info: If I make a symlink /var/chroots/sl6 to /var/chroots/sl-6 and run wwvnfs on /var/chroots/sl6, it creates the vnfs and claims to import it (it probably does, I haven't tested that yet).

...it would seem it just doesn't like the "-" in my pathname. Should it? wwmkchroot created it.

[root@phoenix fernsler]# ls -ld /var/chroots/*

dr-xr-xr-x 21 root root 4096 Apr 10 10:31 /var/chroots/rhel-6.3.1.1
lrwxrwxrwx 1 root root 17 May 17 22:12 /var/chroots/sl6 -> /var/chroots/sl-6
dr-xr-xr-x 21 root root 4096 May 17 17:42 /var/chroots/sl-6

It's probably not a blocker, but wholly unexpected.

comment:3 Changed 6 years ago by gmk

I think I just fixed it just by removing that hybridpath out of the default vnfs.conf. That should fix it, right?

I don't follow the second point your bringing up about the symlinks. Why do you say it doesn't like the hyphen? Did it not create /var/chroots/sl-6 like you told it to?

comment:4 Changed 6 years ago by fernsler

The original error is from wwvnfs:

[root@phoenix .ssh]# wwvnfs --chroot /var/chroots/sl-6
Using 'sl-6' as the VNFS name
WARNING: Hybridpath defined, but not configured in the VNFS /etc/fstab!
ERROR: Illegal characters in --hybridpath option: /mnt/warewulf/%{VNFS}/
[root@phoenix .ssh]#

The bug is about wwvnfs, not wwmkchroot. Sorry that wasn't clear.

And yes, the error goes away if you comment out that hybrid path. We did that, but apparently failed to test on the original sl-6 path after making the symlink, just tested the symlink. My confusion. Sorry. It's been a loong. day.

Last edited 6 years ago by fernsler (previous) (diff)

comment:5 Changed 6 years ago by fernsler

  • Status changed from new to closed
  • Resolution set to invalid

was considered blocker, rolled back. this will be retested from scratch when we get there.

Note: See TracTickets for help on using tickets.